Skip to main content

Ad Hoc Data Request Document - Data migration Service

Modified on Wed, 25 Feb at 4:19 PM

To proceed with additional ad hoc data entry, please complete the Ad Hoc Data Entry Request Form

This form outlines the inclusions, exclusions, and pricing associated with the service.

Once the form has been submitted, our team will review the request and contact you to confirm details and next steps.

Attachments (1)

Rex Cirrus8 Data Migration.pdf
891 KB

Rex Cirrus8 Knowledge Base 1800 431 625

Name	Host	Duration	Description
_fw_crm_v	cirrus8support.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	cirrus8support.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	cirrus8support.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	cirrus8support.freshdesk.com	Session	Your secret key for verifying cookie session data integrity. If you change this key, all old sessions will become invalid!
helpdesk_node_session	cirrus8support.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	cirrus8support.freshdesk.com	2 months	Used for user authentication.
wf_order	cirrus8support.freshdesk.com	Session	Used to check in which the order the tickets are filtered for custom ticket filters eg: due_by, agent_responded_at, requester_responded_at, etc.
wf_order_type	cirrus8support.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	cirrus8support.freshdesk.com	Session	Denotes which filter is applied for the tickets list.

Was this article helpful?