External App Fields: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
When publishing a service, the external app Services contains a large number of fields. Some of these fields contains codes. In this page an overview is provided of the values that can be expected in these codes: | When publishing a service, the external app Services contains a large number of fields. Some of these fields contains codes. In this page an overview is provided of the values that can be expected in these codes: | ||
== | = Template Triggers = | ||
==Create version request== | |||
==Custom request== | |||
==Field change== | |||
Field: Quality Note Saved - Action | Field: Quality Note Saved - Action | ||
Values: Added | Values: Added | ||
| Line 6: | Line 9: | ||
Field: Trigger action | Field: Trigger action | ||
Values: Service published | Values: Service published | ||
==Lost child== | |||
==Lost parent== | |||
==New child== | |||
==New parent== | |||
==Phase change== | |||
==Publication request== | |||
==Quality note change== | |||
==Service creation== | |||
==Service expired== | |||
==Unpublish request== | |||
Revision as of 16:46, 8 February 2022
When publishing a service, the external app Services contains a large number of fields. Some of these fields contains codes. In this page an overview is provided of the values that can be expected in these codes:
Template Triggers
Create version request
Custom request
Field change
Field: Quality Note Saved - Action Values: Added
Trigger action
Field: Trigger action Values: Service published