For the managed package runtime, restrictions and limitations exist for saving and resuming Omniscripts. Some configurations do not support save and resume. Some users are not allowed to perform save and resume, and some users require certain permissions to use the feature.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
The save for later feature isn't supported in these cases:
-
Embedded OmniScripts. When an Omniscript is included in a custom Lightning web component, the outer Omniscript does not save the inner Omniscript.
-
Child (reusable) Omniscripts. When a child Omniscript is included in a parent Omniscript, only the steps and actions from the child Omniscript are copied to the parent Omniscript. All configurations, such as save for later and custom styles, are based on the parent Omniscript. They are not copied from the child Omniscript to the parent Omniscript.
-
Set error. Because set error is not saved in the JSON data, it is not saved in the Saved Session (OmniScriptInstance__c) object.
-
Guest users and Experience Cloud guest users. Such users can't use Omniscript Saved Sessions because security policies prevent them from retaining ownership of records they create.
The save for later feature requires specific permissions in these cases:
-
If a user updates an Omniscript and saves it for later, another user can’t access the saved Omniscript unless that user is granted the necessary permission.
-
Users must have access to the File Based Omniscript Name field of an Omniscript Saved Session object to use save for later. Without this access, they can't save an Omniscript for later or resume an Omniscript that was previously saved for later.