techSHIP WMS - Onboarding Requirements [Information]

Modified on Thu, 13 Aug at 1:43 PM

This article explains the configuration fields required to set up the TechShipWms plugin.

When onboarding/adding a new TechShip WMS location the following information needs to be provided and verified:

TABLE OF CONTENTS

To Be Provided

TechShip region: Selects the specific techSHIP environment for your WMS imports (e.g., USA, Canada, Europe). You must choose the region that matches your issued API credentials.
TechShip API key: Authenticates requests to techSHIP.
TechShip Secret API key: Authenticates requests to techSHIP.

Wms trace: Records detailed troubleshooting information for imports. You should enable this only while investigating an issue.


	Any missing or non-validated, incorrect setup or information will delay the setup process.

Name	Host	Duration	Description
_fw_crm_v	techdinamics.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	techdinamics.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	techdinamics.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	techdinamics.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	techdinamics.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	techdinamics.freshdesk.com	2 months	Used for user authentication.
wf_order	techdinamics.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	techdinamics.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	techdinamics.freshdesk.com	Session	Denotes which filter is applied for the tickets list.