---
schema_version: "1"
id: fe36a318f46ae1c0774d178c66dfa3b5ce5bdf1459f443cc9e64f71b22f103ef
title: Configure Save Options (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_configure_save_options.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_configure_save_options.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3de31d11d5e97438f0b1a4e284b5308393dfdf9ea42f27f34fc7c75dc4e70793
description: For the managed package runtime, enable your users to save and resume Omniscripts by configuring the save for later functionality.
products:
  - Omnistudio
release: "264"
---
# Configure Save Options (Managed Package)

For the managed package runtime, enable your users to save and resume Omniscripts by configuring the save for later functionality.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

1. From the Omniscript's script configuration, expand the Save Options section.
    
    ![image](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/owc_save_options.png)
2. Click **Allow save for later** to enable save for later.
3. If needed, to save the Omniscript automatically when a user clicks **Next** in a step, select **Auto save on step next**.
4. In the **Save Name Template** field, enter a name for the Omniscript.
    
    This field supports merge fields. For example, `%LastName%, %FirstName% - Application`. If the field is blank, the default is `Saved-Omniscript Name-RowId`.
5. In the **Save Expire In Days** field, enter the number of days for which the Omniscript is to remain usable before it expires.
    
    If a user attempts to resume the script after it expires, the Omniscript restarts.
6. For Angular Omniscripts only, set the **Save For Later Redirect Page Name** to the name of a redirect page.
    
    Upon success, the script navigates to this page.
7. For Angular Omniscripts only, set the **Save For Later Redirect Template Url**, the HTML template of the redirect page.
    
    The provided template is vlcSaveForLaterAcknowledge.html.
8. Set the **Save Object ID** field to attach the saved Omniscript to a record.
    
    This field supports merge fields. The default value is %ContextId%. For more information, see [Access Omniscript Data JSON with Merge Fields (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_access_omniscript_data_json_with_merge_fields.htm&release=264.0.0&type=5 "For the managed package runtime, enable Omniscript elements and element properties to access data JSON using merge fields. A merge field is a variable that references the value of a JSON node. For example, if a JSON node is \"FirstName\": \"John\", then the merge field %FirstName% returns John.").
9. If needed, enable users to merge data into an updated Omniscript by selecting **Merge Saved Data JSON into updated Omniscript**.
    
    If **Merge Saved Data JSON into updated Omniscript** is selected, the Omniscript merges the data from the saved instance into the updated Omniscript when a saved instance launches. However, if you used the Set Value action in a step of your Omniscript, that step takes precedence over the saved value, and Omnistudio doesn’t retain any previously saved value.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)
    
    Note
    
    If an Omniscript is deactivated or activated, a new instance of the Omniscript is always created. Multiple instances of forms are created, and saved instances are no longer available. Selecting **Merge Saved Data JSON into updated Omniscript** prefills a form of the new instance of the Omniscript with saved data.
    
    To use saved fields in the new version of the Omniscript, first select either **Merge Saved Data JSON into updated Omniscript** or set the **ContextId** field. Then ensure that the value of the **Save Object Id** field is the same in both Omniscripts. These steps map JSON data from the saved version of the Omniscript into the new version of the Omniscript that is created.
10. To use Base64 encoding for the saved Omniscript file, click **Save Content Encoded**.
    
    Select this option to obfuscate the data.
11. In the Save URL Patterns section, map the Omniscript URL to a custom field of an object. See [Map Saved Instance URLs to Custom Fields (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_map_saved_instance_urls_to_custom_fields.htm&release=264.0.0&type=5 "For the managed package runtime, configure where a saved Omniscript instance launches in Salesforce by mapping URLs to custom fields on the Saved Omniscript object.").
12. To enable save for later on a per-step basis, expand the Save Options section and select **Allow Save For Later**.

What’s next: [Map Saved Instance URLs to Custom Fields (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_map_saved_instance_urls_to_custom_fields.htm&release=264.0.0&type=5 "For the managed package runtime, configure where a saved Omniscript instance launches in Salesforce by mapping URLs to custom fields on the Saved Omniscript object.").