Omni Automation is a powerful tool for automating the use of the suite of Omni productivity applications. Nearly all the abilities of these great applications can be accessed and automated in order to interact with Omni applications, documents, and the data they contain.
With so much control and access to data available to scripts, it is important to ensure that “external scripts” (those from 3rd-party apps and webpages) are executed with your direct review and approval. And it is also crucial that once you’ve indicated that an external script is approved, that any security interface get out of the way and not interfere with your automated processes.
The Omni Automation security protocols are designed to meet those expectations and provide a secure environment for your automation tools.
Configuring the Execution of External Scripts
By default, the execution of external Omni Automation scripts is disabled. (Note: this restriction is for external scripts only and does not apply to Omni Automation plug-ins you’ve installed yourself.)
On iOS and iPadOS the following dialog is displayed if an external script attempts to execute:
On macOS the following dialog is displayed if an external script attempts to execute:
Clicking the “Configure…” button will summon the Automation Settings dialog (shown below).
Automation Configuration Settings on macOS
The panel containing the controls for external scripts can be summoned by either clicking the “Configure…” button displayed in the script security alert dialog (shown above) or by selecting the “Configure…” menu item from the application’s Automation menu.
Here is the Automation Configuration panel on macOS:
Automation Configuration Settings on iOS/iPadOS
On iOS and iPadOS the panel containing the controls for external scripts can be summoned from the Settings menu > Configure Plug-Ins > Security:
Individual Script Approval
The design of the Omni Automation security for the execution of external scripts requires you to review each external script at least once. If a script is approved and executed, you won’t be prompted to review it again.
On all platforms (iOS, iPadOS, macOS) the displayed script must be viewed in its entirety prior to the execution control being enabled.
IMPORTANT: once a script/sending application pair has been approved, no security interaction will occur during subsequent executions of the script by its hosting application.
The following video demonstrates how an external script can approve and executed, and run again without re-approval.
The example embedded webpage script demonstrated in the video is detailed in the next page.