| Table of Contents | ||||
|---|---|---|---|---|
|
...
In section Field Definition you find a collection of all JSON keys that are used by the interface. As specified in the Jira configuration section for this template some of these are purpose bound and can therefore not be mapped freely.
Currently it is not possible to send data with JSON keys deviating from this list:
JSON field | Note |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| only available SAP inbound |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
...
If you want to create a ticket based on a template, e.g. Change Request Template, this can be realized by mapping the JSON key IVPREDECESSORID to the object DOC_FLOW with the logical key E.
Otherwise, if a predecessor is mapped, no custimizing for the predecessor Id is required.
...
| Info |
|---|
Template In this context Template means transaction templates. A ticket created by the interface can be linked to a transaction template. Data can be taken over using the copy control mechanism. In comparison to the predecessor transaction the linkage will be removed on first save. The template can be either a real template transaction (e.g. incident template, change request template) or just another ticket of the same process type as the ticket which is getting created. |
Example - Multilevel Category
...