Page History
...
Note |
---|
NOTE that as opposed to references that can reference the result of an Action, which has already run, across RunTypesRuntypes, dependencies require the Action being dependent on to run in the same RunType, too. |
...
Good Example 1:
Action A and B both run after login, A depends on B (that is, the alias for Action B is entered into the dependencies field of Action A)
If B has already run, A will run.
If B has not run yet, A will attempt to run B. As soon as B has finished, A runs.
Bad Example 1:
Action A runs after login, B before login. A depends on B.
Irregardless of whether B has already run by the time A wants to run, A will fail to execute as B is not configured for the same RunTypeRuntypes.
Bad Example 2:
Action A runs after login, B at shutdown. A depends on B.
Since B has not yet run by the time A is set to execute, and B is configured for a later Runtype, execution of A fails.
...
Note |
---|
NOTE that you can have nested dependencies, e.g. A depends on B depends on C depends on D. |
...