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 containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | Field change |
| Field changed - Field essential phase name | Contains the phase names for which the field is essential | Any of the phase names |
| Field changed - Field essential phase type | ??? | |
| Field changed - Field internal name | Internal name of the changed field | |
| Field changed - Field is language dependent | contains yes of field is language dependent, no if not | |
| Field changed - Field name | Name of the changed field | |
| Field changed - Field type | type of the changed field |
|
| Field changed - Language | The name of the field language | any of the active language names, for example English |
| Field changed - Language id | The id of the field language |
Other numbers should be checked in the language table |
| Field changed - New value | Contains the value after the edit | |
| Field changed - Old value | Contains the value before the edit | |
Quality Note Saved - Action
Values: Added
Field: Trigger action Values: Service published
Lost child
This trigger occurs when a child relation is disconnected
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | Lost child |
| Related service guid | UniqueId of the unrelated service | |
| Related service id | Id of the unrelated service | |
| Related service name | Name of the unrelated service | |
Lost parent
This trigger occurs when a parent relation is disconnected
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | Lost parent |
| Related service guid | UniqueId of the unrelated service | |
| Related service id | Id of the unrelated service | |
| Related service name | Name of the unrelated service | |
New child
This trigger occurs when a new child relation is set
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | New child |
| Related service guid | UniqueId of the related service | |
| Related service id | Id of the related service | |
| Related service name | Name of the related service | |
New parent
This trigger occurs when a new parent relation is set
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | New parent |
| Related service guid | UniqueId of the related service | |
| Related service id | Id of the related service | |
| Related service name | Name of the related service | |
Phase change
This trigger occurs when a the phase of a service is changed
Publication request
This trigger occurs when the service is published
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | Publication request |
| Publication requested - Guid | Guid of the published service | |
| Publication requested - HashCheck | This hash is required to submit a vote on this publication request through the webservice | |
| Publication requested - Request comments | Comments provided when this publication was started | |
| Publication requested - Request option | In case an optional datastore is active for the publication action, the value selected in the dropdown list is in this field |
|
| Publication requested - Type | Type of the publication that will steer what happens when publication is approved |
|
Quality note change
This trigger occurs when a new quality note is added or an existing note is updated
| Fields containing specific values for this trigger | ||
|---|---|---|
| Field | Field explained | Possible content |
| Trigger action | The trigger causing the flow to start | Quality note change |
| Quality note saved - Action | The action performed on the quality note |
|
| Quality note saved - Closed by person | Id of the related service | |
| Quality note saved - Created by person | Name of the related service | |
| Created date | Creation date of the quality note | |
| Id | Unique Id of the quality note | |
| Is closed | Indicator if note is closed |
|
| Note | Content of the quality note | |
| Solution | Solution provided with the quality note | |
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