Skip to main content

Update Variables

This guide explains how to update existing variables in Authorium and the impact of these changes depending on where the variable is defined. Updating a variable ensures that your content stays accurate, consistent, and aligned with project needs.

Where You Can Update Variables​

Variables can be updated from the same sections where they are created.

To Update Template-Level Variables​

These variables are defined within a specific project template and reused across forms and documents.

  1. Go to Configuration from the sidebar.
  2. Select a Project Template and click View Template.
  3. Go to the Variables tab.
  4. Click the Kebab menu next to the variable and select Change Variable.
  5. Update the Name, Key, and any relevant fields:

    You cannot switch the variable type (for example, from Custom to Mapped to Existing Data).
    You can only modify fields relevant to the original type.

    • If it was created as Custom, you can change the data type.
    • If it was created as Mapped to Existing Data, you can change the data source.
  6. Click Save Changes.
  7. To apply changes to future projects, click the Kebab menu at the top and select Publish.

To Update Project-Level Variables​

These updates apply only within the selected project and take effect immediately.

  1. Open a project from the Projects section.
  2. Go to the Variables tab.
  3. Locate the variable and click Change Variable.
  4. Edit the Name, Key, or any value as needed.
  5. Click Save Changes.

When you update a variable in a project, the changes automatically reflect across the project — including in forms, business rules, and completed documents.

Impact of Updates​

LevelAffectsRequires PublishingNotes
TemplateProjects created after publishingYesMust republish the template.
ProjectThe current project onlyNoTakes effect immediately.

Changing a variable's key may break existing mappings. Be sure to re-map the variable in forms or templates if needed.

Publishing and Saving​

  • Template-level changes must be saved manually.
  • Template-level changes also require publishing to take effect in new projects.
  • Project-level changes are saved automatically after clicking Save Changes.

Use naming versioning (e.g., contractStatus_v2) when changing variables with broad usage.

See Also​

To complement your knowledge of this process, check the following pages: