Testing Actions and Transitions

When you test a workflow, review the workflow execution log to see which actions and transitions did or did not process during the run of your workflow. Based on log details, you can make changes to the workflow to resolve issues with actions or transitions. For more information about the workflow execution log, see Workflow Execution Log.

Actions and transitions can have one the following statuses:

• Executed

• Failed

• Skipped

• Considered

In addition, an event or transition may not appear in the log because they did not run. SuiteFlow will only attempt to process actions of the appropriate trigger type. Make sure that you understand triggers and the Suiteflow triggering model. For more information, see Workflow Triggers.

Tip

To test the execution of one specific action within a state, set all other actions in the state to Inactive. For each action, select the Inactive box on the action definition page and save the action. After you test, you can re-activate the actions. You can also change the trigger type for the action to make sure the action trigger type did not cause the failure.

Skipped Actions

When SuiteFlow skips an action, the action may not be supported for the server trigger on which the workflow entered the state.

The following screenshot shows a record that entered a state on a Before Record Load trigger and consequently, the Send Email action was skipped:

You can view the options for the Send Email trigger on the Send Email action definition page in the Trigger On dropdown list:

This action can be executed on any of the four triggers listed, depending on the server trigger on which the record enters the state. Since Before Record Load is not an option for the action, the workflow skips the action when running ONENTRY trigger under BEFORELOAD.

General Notices