Create or update instances
- Create an Automation and choose an adapted trigger.
- Select the Generate data action.
- Select Create or Update:
- To update an instance, Update should be selected, with the path to the instance that needs to be updated.
Updates the Triggering instance
- To create an instance, Create should be selected:
- Without linking to an existing instance, the path should be completed with the Concept of the instance that needs to be created.
Creates a Use case
- By linking to an existing instance, the path should be completed with the path to the linking field.
Creates a Milestone in the Milestone list of the Triggering instance
- Without linking to an existing instance, the path should be completed with the Concept of the instance that needs to be created.
- To update an instance, Update should be selected, with the path to the instance that needs to be updated.
- Add one or more operations, each operation will be played in the displayed order.
Configure operations
For each operation, select the field that needs to be updated.
Select the needed operation. Depending on the type of the field updated, a variety of operations are available:
For fields Text, Association, Number, Date, the available operations are the following:
| Operation | Field types | Effect |
|---|---|---|
| Initialize | Text, Association, Number, Date | Will only update the field if the updated instance has no value for this field. |
| Replace | Text, Association, Number, Date | Will always replace the previous value with the new one. |
| Add | Only for Association (n-n) and Association (1-n) | Will add the value to the existing values. |
| Remove | Only for Association (n-n) and Association (1-n) | Will remove the value from the list. |
| Clear | Text, Association, Number, Date | Will delete all values from the field. |
| Increment | Only for Number | Will increment the number by the value given, which can be positive or negative. If the Number field for the updated instance has no value, it will start at 0. |
Choose values for operations
If the selected operation needs a value (i.e. all operations except Clear), this value can be:
- A fixed value (With a value):
Add Australia to the Concerned site field
- A dynamic value (With a path)
Add all the Sites to the Concerned site field
Dedicated interfaces are available for Date Range, Workflow and Stakeholders fields.
Review the run history
The run history of an automation shows when the automation was triggered and when it produced data.
What does an empty run history mean?
If no entry appears in the run history, it means that the automation has not been triggered.
What does a successful run with no generated data mean?
If a run is marked as Ran successfully but it is marked as No data generated, it means that the automation was triggered successfully, but based on what has been configured, no data was generated. If this is not the intended outcome, it’s possible that the configuration is incorrect (ex: Only if misconfigured).
What does an event ID indicate?
If an Event id is listed for a run marked as Ran successfully, it confirms that data has been generated. If further clarification is required regarding the generated data, please contact the support team.
Why can large automations be delayed?
For large automations that generate a high volume of updates, a significant delay may occur between the Ran successfully status and the moment when data becomes visible to users. In such cases, it's recommended to wait a little while before expecting to see the results.