1
Download AGILOFT REFERENCE MANUAL
Transcript
Administrator Guide All this is a lot easier in practice, using the GUI, than it seems on paper. Agiloft provides a graphical interface that makes it easy for the administrator to see and edit the workflows that apply to a particular type of record. Tables inherit the workflows from their parents. Consider the following hierarchy: Contact + Lead + Customer If you create a workflow for Contact, then select Lead and look at its workflow, you will see the Contact workflow that you just created has been applied to it as well. However, workflows do not have to be the same between parent and child tables. For example, you can augment the workflow for Lead by adding additional states, state-transitions or guards. This will not alter the workflow for Contact, nor will it break the linkage to the workflow for Contacts – if you add additional states/transitions/actions to Contacts, they will automatically show up in Leads. In brief, sub-table workflows don't contain a copy of the parent workflow, they contain the parent workflow plus their own additions to it. If you are in a sub-table (Lead in the example above) and try to delete one of the state transitions or edit one of the actions that was inherited from the parent, the system will warn you that this change will affect the parent workflow. See Also: Business Example Actions Rule Record Object Flash Tutorials 229
