Skip to main content
Question

You created a new Boolean constant named AV_BOOLEAN_ENABLE_DELETE_TEM_DOCUMENTS in the Development environment and marked it as Environment Specific.

When deploying the application package to the QC environment, the deployment fails with the following error:

The constant [uuid=...] was not created because a value for the constant must be provided in an
import customization file when it is environment specific.

What causes this error, and how would you resolve it?

A
Anonymous
July 29, 2026

Answer

The constant is marked as environment specific, but the import customization file has no value for it. The first time an environment-specific constant goes to a target environment, Appian needs an initial value. Regular constants take their value from the source environment, but environment-specific ones don’t.


Error:

1785337016585-d3wh9msvd2q.jpeg


The deployment is failing due to environment constant ,As suggesting in error we need to imported customize file importing the package in QC environment


1. Download the customization file

Download the generated import customization file from the deployment package in Appian.

1785337016588-b4fyo8rties.jpeg


2. Find the constant

Open the file in a text editor and search for the constant name:

## Constant: AV_BOOLEAN_ENABLE_DELETE_TEM_DOCUMENTS
## Type: Boolean
##
## Boolean values must be TRUE or FALSE.

#content._a-0000f01d-a8fd-8000-9ccf-011c48011c48_7099241.VALUE=TRUE


3. Uncomment the property and set a value

Remove the single # at the start of the property line:

## Constant: AV_BOOLEAN_ENABLE_DELETE_TEM_DOCUMENTS
## Type: Boolean

content._a-0000f01d-a8fd-8000-9ccf-011c48011c48_7099241.VALUE=TRUE

TRUE is only an example. Set TRUE or FALSE to match what QC needs.

When you edit the file:

  1. Leave the generated constant UUID as it is.
  2. Keep the ## on the instruction and heading lines.
  3. Don’t leave the value empty.
  4. Make sure the property line doesn’t start with #.


4. Deploy to QC

  1. Save the .properties file.
  2. Upload it with the application package when you deploy to QC.

1785337016589-bjbqubp5pcu.png

Run the deployment again and check that the constant was created with the right value.


What happens on later deployments

For constants marked as environment specific in the deployment package:

Scenario

Appian behavior

Constant is new in QC and no value is provided

Deployment fails

Constant is new in QC and a value is provided

Constant is created

Constant already exists in QC and no value is provided

Existing value is kept

Constant already exists in QC and a new value is provided

Existing value is updated

So once the constant exists in QC, you only need to include a value when you want to change it.


Interview tip

Mark a constant as environment specific when its value has to differ between environments. For example:

  1. DEV: AV_ENABLE_EMAIL_NOTIFICATION = FALSE
  2. QC: AV_ENABLE_EMAIL_NOTIFICATION = FALSE
  3. PROD: AV_ENABLE_EMAIL_NOTIFICATION = TRUE

Email notifications stay off in the test environments and on in Production.

Check yourself

Question 1 of 3, on what the answer above covers.

  1. 1.
    Question: You created a new environment-specific constant CONS_ENABLE_EMAIL in DEV. While deploying it to QC for the first time, Appian throws an error stating that a value must be provided.
    What should you do to resolve this error?
JuniorConstant#secenrio_based