Use filter conditions to set conditions for when to trigger flows. You can set additional properties to define more granularly when the flow runs and the user profile under which it runs. The Scope list indicates those rows should be monitored to determine if the flow should be run.Īctions are taken on rows owned by anyone in your business unit.Īctions are taken by anyone within the environment.Īctions are taken on rows that are owned by anyone in your business unit or a child business unit. The When a row is added, modified or deleted trigger doesn't support starting flows on relationships of type 1:N or N:N. The When a row is added, modified or deleted trigger doesn't support virtual tables. The Table name list filters the rows to indicate precisely which kind of rows should change before the flow triggers. When the flow is triggered by the creation, update, or deletion of a row, the value of triggerOutputs() will be Create, Update, or Delete, respectively. The trigger condition, Change type, precisely defines which combination of changes to a row would run the flow. The following information is required to use the When a row is added, modified or deleted trigger. To create a flow that triggers when you create, modify, or delete a row, you must have user-level permissions for create, read, write, and delete on the Callback Registration table.Īdditionally, depending on the scopes defined in the flow, you might need at least that level of read on the same table. You can get more information about Environment security. The When a row is added, modified or deleted trigger runs a flow whenever a row of a selected table and scope changes or is created.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |