External App Fields

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

This trigger occurs when the user clicks the button to create a new version

Custom request

This trigger occurs when a (publication) request is started through the API. Custom requests can be used to lock a service while actions in the background are pending to be completed.

Delete request

This trigger occurs when the user clicks the button to delete a service

Field change

This trigger occurs when a value in a field is changed.

Fields the contain a value: 

colspan="2" Fields containing specific values for this trigger
Field changed - Field essential phase name	Contains the phase names for which the field is essential
Field changed - Field essential phase type	???
Field changed - Field internal name	Internal name of the changed field

Quality Note Saved - Action

Values: Added

Field: Trigger action
Values: Service published

Lost child

This trigger occurs when a child relation is disconnected

Lost parent

This trigger occurs when a parent relation is disconnected

New child

This trigger occurs when a new child relation is set

New parent

This trigger occurs when a new parent relation is set

Phase change

This trigger occurs when a the phase of a service is changed

Publication request

This trigger occurs when the service is published

Quality note change

This trigger occurs when a new quality note is added or an existing note is updated

Service creation

This trigger occurs when a new service is created

Service expired

This trigger is not active yet

Unpublish request

This trigger occurs when the users clicks the unpublish button