External App Fields: Difference between revisions

From SMTX Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:
This trigger occurs when the user clicks the button to create a new version
This trigger occurs when the user clicks the button to create a new version
==Custom request==
==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==
==Field change==
This trigger occurs when a value in a field is changed.
  Field: Quality Note Saved - Action
  Field: Quality Note Saved - Action
  Values: Added
  Values: Added
==Trigger action==
 
  Field: Trigger action
  Field: Trigger action
  Values: Service published
  Values: Service published
==Lost child==
==Lost child==
This trigger occurs when a child relation is disconnected
==Lost parent==
==Lost parent==
This trigger occurs when a parent relation is disconnected
==New child==
==New child==
This trigger occurs when a new child relation is set
==New parent==
==New parent==
This trigger occurs when a new parent relation is set
==Phase change==
==Phase change==
This trigger occurs when a the phase of a service is changed
==Publication request==
==Publication request==
This trigger occurs when the service is published
==Quality note change==
==Quality note change==
This trigger occurs when a new quality note is added or an existing note is updated
==Service creation==
==Service creation==
This trigger occurs when a new service is created
==Service expired==
==Service expired==
This trigger is not active yet
==Unpublish request==
==Unpublish request==
This trigger occurs when the users clicks the unpublish button

Revision as of 16:52, 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

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.

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