Viewing Logs for Actions Performed Using SuiteFlow

This topic provides examples of how actions triggered by SuiteFlow are recorded in the PI access log. For general information about the SuiteFlow feature, see SuiteFlow Overview.

When you use SuiteFlow to perform actions on records containing sensitive customer information, those actions are recorded in the PI access log.

Note:

For workflow execution entries, the PI access log doesn't track the exact action performed by the workflow. Use the link in the Source Details column to view 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.

A log of actions triggered by a scheduled workflow.

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.

An action triggered by an event based workflow.

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.

An example of a log where the workflow was triggered by a script.

When you use synchronous methods such as workflow.initiate(options), only the Source Details column shows that the action was performed using SuiteFlow.

An example of a log where the workflow was triggered by a script that uses workflow.initiiate.

When you run scripts with the Script Debugger, such actions are logged as script executions and the access log may show the following:

An example of a log where the script was run using Script Debugger.

Record Lookups During Workflow Creation with Ask Oracle

When preparing a workflow from your request, Ask Oracle can look up records to determine which field values to use. Qualifying record access during these lookups is recorded in the Personal Information Access Logs workbook.

This access occurs before the workflow is created. A log entry does not confirm that a workflow was created.

For information about viewing access entries, see Personal Information Access Logs Dataset and Workbook.

Related Topics

General Notices