Skip to main content
System StatusContact Support
VersionOne Community

Global Registry

Overview

Learn how to configure and manage the Continuum Flow Global Registry.

There are several different modules in Continuum that work together to form a complete orchestration and automation capability. As a logic designer, there's often a need to share information across the different modules, (Flow Pipelines, Automate Tasks, etc), or to persist information for use and reuse.

Pipelines and Tasks both have internal Workspace while processing, but for fully customizable persistence and data sharing, make use of the Global Registry.

The Global Registry is a persistent collection of named registry documents that can be read and written by both the UI as well as any automation in Continuum.

Managing the Global Registry in the UI

The Global Registry can be managed from the administration menu, under Flow - Manage Global Registry.

The interface is simple, and consistent with other similar 'globals', such as on a Pipeline Definition or a Project.

Accessing the Global Registry from a Pipeline

There are two commands available in a Pipelines to work with the Global Registry. In the Utility plugin, Get Registry and Set Registry.

Get Registry

The Get Registry command will load a specific registry document in it's entirety into the Pipelines workspace under the specified key.

  • Name - (required) the name of the registry document
  • Key - (required) a target Workspace key to receive the document
  • Required - (true/false) if true and the registry document is not found, the pipeline will fail. If false, a missing document will not stop pipeline execution

Registry documents cannot be partially loaded, therefore it's a good practice to have many documents with more targeted content than one giant document.

Set Registry

The Set Registry command will load a specific registry document in it's entirety into the Pipelines workspace under the specified key.

  • Name - (required) the name of the registry document
  • Path - (required) path to a key in the document to set. (Dotted notation and index specification are allowed.)
  • Value - (optional) value to set at the specified key path. If left empty, the specified key path will still be set, but set to an empty value.
  • Create - (true/false) if the specified registry document does not exist, it will be created according to this setting
  • Action - (required) There are several different methods of updating a document value:

    • set - set the specified key path to the provided value. If the value is empty, the specified key path will set to a zero-length string value.
    • unset - remove the specified key path from the document completely
    • add_to_set - if the specified key path is an array, the value will be added to that array only if it does not already exist in the array.
    • push - if the specified key path is an array, the value will be added to that array regardless of if it already exists in the array.
    • pull -if the specified key path is an array, all instances of the value will be removed from the array.

Accessing the Global Registry from a Task

In an Automate Task, there are similarly two functions for working with the Registry. In the Variable category in the Commands toolbox, Get Registry and Set Registry. The arguments are the same as described above.

  • Was this article helpful?