User Guide Cancel

Acrobat Sign Sandbox asset types

 

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Send, Sign, and Manage Agreements

Advanced Agreement Capabilities and Workflows

Integrate with other products

Acrobat Sign Developer

Support and Troubleshooting

Asset types that can be copied between environments

Several assets can be copied from the Production environment to the Sandbox or from the Sandbox to Production. This is designed to allow testing of existing objects in the Sandbox and then promoting them to production use when testing is satisfactorily completed. 

Templates

The column data provided in the Templates section is as follows:

  • Title - Provides the literal name for the library template.
    • Templates created in (or copied to) the Sandbox environment will have the string [DEMO USE ONLY] prepended to the template name in the Manage view
  • Status - The status of the template can be:
    • Active - Active templates are available to send to recipients or attach to workflows.
    • Authoring - This is a Draft template that hasn't been completed to the point it can be sent for signature.
  • Sharing Mode - This value asserts the scope of the template. A template may only have one sharing mode:
    • Account - Account sharing indicates that all users in the account can use the template for agreements or workflows.
    • Group - Group sharing indicates that anyone in the group the template is associated with will be allowed to use it for creating agreements or workflows.
    • User - User sharing mode indicates that only the creating user can access the asset. These can only be copied if you're the owner of the template.
      • If you attempt to copy a template with a User share mode, and the owner of that template isn't you, an error message will trigger (Error executing request!)
  • Template Types - Templates have two types. One or both can be referenced:
    • Document - A file containing viewable content with a form field layer applied. The document type is used for static documents with defined field placement.
    • Form Field Layer - A form field layer without the underlying document containing the viewable content. Used when the document's content is variable, but the field requirements are constant.

Actions that can be taken with library templates are:

  • Copy - This action copies a template version to the local environment with the same name value.
  • Copy As - This action allows the admin to change the asset's name when copied to the local environment.
Library template options

User Group

The column data provided in the Groups section is as follows:

  • Name - Provides the literal name for the group.
  • Is Default - Identifies if the group is the default group for the account.
    • True - This value identifies the account's default group.
      • There must be one, and only one, default group.
    • False - All groups that are not the default group.

 

The only action that can be taken with a Group is Copy.

When a group is copied to the other environment, a new group is created with the same Name value as the copied group.

  • No settings or users are imported when the group is copied. The group will be empty and configured to inherit all settings from the account level, just as any new group would be.
  • Copying groups is in place to support other objects that reference groups (e.g., Workflows).
Group options

Web forms

The column data provided in the Web Form section is as follows:

  • Title - Provides the literal name for the web form
    • Web forms created in (or copied to) the Sandbox environment will have the string [DEMO USE ONLY] prepended to the name in the Manage view
  • Status - What is the current status of the web form:
    • Active - The web form URL is available to the public and can be signed by a recipient
    • Disabled - The web form is disabled. The URL will either redirect recipients or provide a terminal message depending on how the web form was configured at the time it was disabled

  Actions that can be taken are:

  • Copy - This action copies a version of the web form to the local environment with the same name value
  • Copy As - This action allows the admin to change the name of the web form when it's copied to the local environment
Web form options

Custom Workflows

The column data provided in the Workflows section is as follows:

  • Name - Provides the literal name for the workflow.
  • Scope - Defines the workflow's scope in terms of account access.
    • Group - The workflow is currently configured to be accessible to only one group.
    • Account - The workflow is currently configured to be accessible to the whole account.
  • Status - The current availability status of the workflow.
    • Active - Workflows that are available to users in the account.
    • Draft - The Draft status is used when the workflow hasn't been set to Active.
      • Workflows that have been deactivated will reflect a Draft status.  

 

Actions that can be taken are:

  • Copy - Copies the workflow from the remote environment to the local environment.
    • Automatically updates the workflow if the local environment has the same workflow already.
  • Copy As - Copies the workflow from the remote environment and allows the admin to rename it.
Workflow options

API Applications

The column data provided in the API Applications section is as follows:

  • Display Name - Provides the literal name displayed for the application.
  • Domain - Defines the application's scope in terms of account access.
    • CUSTOMER - The application is only configured to access data within your Acrobat Sign account.
    • PARTNER - The application is configured to access any authorized Acrobat Sign account.
  • Status - The current availability status of the application.
    • Active - Applications that are currently available to users in the account.
      • Applications are created in Active status.
    • Disabled - Applications that are no longer available.

 

Actions that can be taken are:

  • Copy - Copies the application from the remote environment to the local environment.
  • Copy As - Copies the application from the remote environment and allows the admin to rename it.
API Applications options

Searching for assets

By default, the list of assets is sorted by the Name/Title value of the asset.

To help find the asset you are looking for, each section has a Search field that limits the data set exposed based on the Name/Title field of the asset type being viewed:

Search assets

Only assets that match the string will be returned.

  • The search string is not case sensitive
  • The search string can be anywhere in the name/title as long as the string is unbroken

Local vs Remote assets

When a Sandbox is connected to your Production environment, the Sandbox interface defines the two independent environments as either Local or Remote.  

  • The Local section contains the assets that are available in the environment you authenticated to
  • The Remote section lists the assets in the environment you connected to

In the image below, we have authenticated to the Sandbox (note the banner at the top of the page), and connected to the Stage environment (Stage Sync). In this case, the Sandbox is local, and you can copy assets from the remote Stage environment.

Local vs Remote

Note:

Currently, the Sandbox only allows copying an asset to the local environment from the remote environment.

Admins can authenticate to both environments, permitting back-and-forth Copy actions.  

Get help faster and easier

New user?