Skip to content


A Project is the most common Clarive security Scope.

A Clarive Project is a collection of Topics, and is defined according to your organization's requirements. For example, a Clarive Project could be:

  • A software development project.
  • A system.
  • A group of software components.
  • (More commonly) an application.

Topics can belong to zero, one or more Projects, but that is not a requirement. For example, Changeset Topics must belong to one (and only one) Project.

Releases, on the other hand, may be multi-project or have no Projects.

Project Variables

Every Project can have a set of variables with values set specifically for that Project. Moreover, for every Environment, different values can be set.

Project variables can be of 2 types:

  • Administrator-defined variables
  • Custom (user-defined) variables

Custom Project Variables

These are variables defined inside the project Deploy > Variables area, under Custom Vars.

The intention of these variables are that they be set by project users with variable edit permissions, with action action.variables.admin.

Custom project variables do not overwrite project variables. They can be accessed under the CUSTOM_VARS prefix namespace in a rule, such as ${CUSTOM_VARS.myvar} in rules, or without the prefix in rulebooks: ${myvar}.

In rules that run under a given environment, such as pipeline rules, the environment-assigned variable will have precedence over other definitions of the variable.

If no environment-specific variable exists, Clarive will use the common environment (*) variable instead. This is the case also when custom project variables are used in rules that do not have an environment, such as webservice, form, event, etc. rules.

Custom project variables are intended for end-users, with permissions, to modify at will and are not as secure and versioned as project variables are.

Administrator Project Variables

Variables may be configured in an Project Templateaccording to the Environment(s) in which they are available or are assigned a given value. These variables are referenced in Projects in a similar way to when referencing simple variables, with the difference that their values are then imported by selecting from the Import Configuration combo the Environment Template in which these were configured.

In this combo, there are two options available.

  • Overwrite - Overwrites the values of variables that are already defined in the project with the values of the template. Do not import not defined variables in the project.

  • Reset with template - Remove variables and their values and replaces them with variables included in the template.

In addition, two checkboxes are available:

  • Skip if already set - Skip all values of variables that have been modified in the project.

  • All Environments - Imports all variables in all environments of the template. If it is not active, it will only import the variables that are in the current environment.

Copying variables between Environments

Setting variables can be a cumbersome process, and it is very common for different Environments to have the same variables, albeit with different values. That is where copying vars to another environment can be a real help. If the variable has a Copy flag it is copied with the current value.

Nature variables

Nature variables are built from selected natures and their blueprints.