You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: flashduty/en/1. On-call/8. Integrations/8.5 Webhooks/8.5.6 ServiceDesk Plus sync.md
+6-25Lines changed: 6 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,30 +70,19 @@ Please select the corresponding API Endpoint and Accounts Server URL according t
70
70
- Manual Trigger: Requires manual triggering of ServiceDesk Plus sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
71
71
72
72
5.**Channel:** Select the channel where this integration takes effect.
73
-
6.**Request Template:** Select the template to use when creating requests.
74
-
7.**Severity Mapping:**The mapping relationship between Flashduty severity and ServiceDesk Plus priority. For default mapping relationship, please refer to [Priority Mapping](#priority-mapping).
73
+
6.**Request Template:** Select the template to use when creating requests. If empty, the default template will be used to create the request.
74
+
7.**Severity Mapping:**You can choose to map the values of severity, incident labels, or custom fields to the Priority field in ServiceDesk Plus. If empty, this field will not be passed when creating requests.
75
75
8.**Custom Field Mapping:** You can map labels or custom fields in incidents to corresponding text fields in ServiceDesk Plus tickets to achieve automatic information filling. This feature supports syncing common context information (such as service name, instance address, metric name, etc.) to ServiceDesk Plus for subsequent troubleshooting and tracking.
76
76
- Only supports target fields of single-line text or multi-line text type.
77
77
- Supports extracting values from incident labels (such as service, instance) or custom attributes.
78
78
- If the source field is empty, the target field will also remain empty and will not overwrite existing content.
79
-
- Mapping configuration is managed uniformly in integration settings without manual filling each time.
80
79
81
80
9.**Assignee Mapping:** When Flashduty incidents are synced to ServiceDesk Plus and need to be automatically assigned to Technician or Group, you can get the value of Flashduty incident labels as the assignee (if the corresponding assignee does not exist, it will cause sync failure, please choose carefully).
82
-
83
-
10. Click `Save` to complete the configuration.
81
+
10.**Requester:** The requester to be specified when creating a request. This needs to be configured if the field is mandatory when creating requests.
82
+
11. Click `Save` to complete the configuration.
84
83
85
84
### In ServiceDesk Plus
86
-
#### Step 2 Create Requester
87
-
When Flashduty incidents are synced to ServiceDesk Plus, the Requester automatically set by the system
88
-
89
-
1. Log in to the ServiceDesk Plus console and find the `Setup` configuration page.
90
-
2. Select `Users & Permissions`, then enter the `Users` creation page and select `New Requester`.
91
-
3. Fill in **flashduty** for `Name (Display Name)` and `First Name`, fill in **flashduty-sync@flashcat.cloud** for `Email`.
92
-
4. Other settings can be configured as needed, click `Save` to save the configuration.
To achieve synchronization of ServiceDesk Plus requests to Flashduty, please refer to this configuration item. **Note:** Different versions may have slightly different paths, but the configuration method is the same.
98
87
##### Create Webhook
99
88
1. Log in to the ServiceDesk Plus console and find the `Setup` configuration page.
@@ -132,7 +121,7 @@ To achieve synchronization of ServiceDesk Plus requests to Flashduty, please ref
0 commit comments