Viewing Logs for Actions Performed Using SuiteFlow
This page lists common examples of how actions triggered by SuiteFlow are recorded into the PI access log. For general information about the SuiteFlow feature, see SuiteFlow Overview.
When you perform actions on records that contain customer related sensitive information using the SuiteFlow feature, such actions are logged into the PI access log.
The access log doesn’t track the exact actions the workflow performs. To see what actions were performed during a workflow, use the link in the Source Details column to see the workflow definition.
Scheduled Workflows
For scheduled workflows, the action is logged with SuiteFlow in the Interface column and Workflow Execution in the Action column. In the following example, the workflow runs every 30 minutes to process new customers.
Event Based Workflows
For workflows initiated on an event, the log shows UI in the Interface Type column, and the action you performed, such as Create, View, Edit, or Delete, in the Action column. In the following example, Bradley updated an invoice in Madalyn's name, which triggered a workflow that sent an email to Madalyn notifying about the update on her transaction.
In both cases, you’ll see the type of record in the Source column, and you can use the link in the Source Details column to see the workflow that triggered the action.
Workflows Initiated by SuiteScript
You can also use scripts to initiate workflows. For general information about SuiteScript, see SuiteScript Overview.
In the following example, Bradley updated Madalyn's invoice, which triggered a script that initiated a workflow that added a comment to Madalyn's record about the recently updated invoice. Since this workflow was initiated using an asynchronous method task.create(options), the workflow execution is logged as a separate row in your access logs.
When you use synchronous methods such as workflow.initiate(options), only the Source Details column shows that the action was performed using SuiteFlow.
When you run scripts with the Script Debugger, such actions are logged as script executions and the access log may show the following:
