Workflow Actions
You can create workflow actions before setting up workflow triggers (or custom buttons) and associate such actions with them or you can create workflow actions directly in a certain workflow trigger (or a custom button):
Click the Setup link in the top right corner of the window.
Choose a necessary table and click a corresponding tab at the top of the window.
From the menu in the main frame select Rules > Workflow Triggers in case of a trigger creation or Rules > Custom Buttons in case of a custom button creation.
Choose a trigger/custom button from the list and click either its name or the Edit button next to it. There is the Actions section displayed below, where the actions can be added.
Click on the New button to add actions created beforehand or create a new action.
Workflow actions created beforehand:
Also you can create actions in advance and associate them with corresponding triggers or custom buttons later.
To create a new workflow action:
Click the Setup link in the top right corner of the window.
Choose a table and click a corresponding tab at the top of the window.
From the menu in the main frame select Rules > Workflow Actions. Click New at the top of the actions list.
Select a necessary action type:
Fill out the Action form in accordance with the selected type (see details below):
Workflow actions may be created in the process of trigger/button creation or prior to adding triggers/buttons (in the latter case, during the process of trigger/button creation, you select previously created actions from the list).
Please notice, that Table Records Access and Columns Access do not affect Workflow Actions. Only the access to a button or a trigger comprising the action is taken into account by the system.
TeamDesk allows cascading execution of record change triggers. By default the cascading execution is switched off. It is controlled via the
Execute Triggersoption available in Create Record, Update Record, Delete Record and Call-URL actions.There is the limit on the number of executed workflow actions. It depends on the number of users.