Endpoint details
In this document, you will find detailed info about Remedyforce Endpoint Type. This Endpoint Type is a self-service type, so users can add them without a need to reach out to ONEiO Support.
General | |
---|---|
Status | Sets the status of the endpoint. Active / Suspended |
Remedyforce root URL | The base address of your Remedyforce. You can test the HTTP connection by clicking the Test Connection button. Note that this function does not test the authentication, only if ONEiO can reach the endpoint. |
Name | Name of the endpoint. It is recommended to use short names since this name is used in displays throughout ONEiO. |
Timezone | The timezone used in the Remedyforce application |
Datetime pattern | Date time pattern ONEiO uses to read DateTime fields and how ONEiO sends out DateTime fields. Shown only for reference. |
ONEiO ->[Your Remedyforce] | |
---|---|
Remedyforce user | The user that is used in all calls to [Salesforce/Remedyforce] API. These include updates and lookups. |
Remedyforce User ID |
Unique identifier of integration user. On Lighting version of Remedyforce ; 1- Click on profile avatar, 2- After the profile menu opened, click profile avatar one more time, 3- Check URL and take "user id", which is in ".../User/{user id}/..." |
Password | The password of the integration user. |
Security Token | The token can be taken by clicking Profile avatar then Settings → My Personal Information → Reset My Security Token. |
Client ID | Consumer Key. It must be taken from the related Connected App which is created with the integration user. |
Client Secret | Consumer Secret. It must be taken from the related Connected App which is created with the integration user. |
Unrecoverable HTTP error codes | List of numeric HTTP response codes that are to be handled as non-recoverable when sending messages to Salesforce/Remedyforce API. If ONEiO receives an error code that is not on the list, it will retry the message automatically. If ONEiO receives an error code that IS on this list, the message will result in an error. |
Comments
Please sign in to leave a comment.