For BSS Contact entities we support both push and pull methods. Below table presents property mapping between BSS Contact entity and Zendesk end-user entity | Contact (BSS entity) | End-User (Zendesk entity) |
|---|
| Email | Email | | FirstName+LastName | Name | | MobilePhone | Phone | ServerVariable
Role | Role | | "True" | Verified |
For BSS Case entities we support both push and pull methods. Below table presents property mapping between BSS Case entity and Zendesk ticket entity | Case (BSS entity) | Ticket (Zendesk entity) |
|---|
| Contact.IntegrationId * | Requester_Id | | Contact.IntegrationId * | Submitter_Id | | Type.IntegrationId | Type | | Name | Subject | | Name | Raw_Subject | | Description | Description | | Priority.IntegrationId | Priority | | Status.IntegrationId | Status | | DueDate | Due_At | | Description * | Comment |
| Rw ui textbox macro |
|---|
| Requester_Id , Submitter_id
In case no contact is present for a ticket, the static value of ServerVariable Submitter_ID is used in order to define the Requester_Id and Submitter_Id of the ticket. |
| Rw ui textbox macro |
|---|
| Comment
If Account or Product exists on a BSS Case, comment will include the Account name/Id and Product name/id respectively. |
|