Change a Constant to Environment Specific

when u try to create a constant of type Document the selection of Environment specific gets Disabled so i just learnt it is NOT POSSIBLE for Document Type Constant

Yes, even I found this now..

That sounds about right actually. A document pointed to by a constant will import to other environments and maintain its relationship with the constant pointing to it, even if the document ID changes in the new environment. So in a general use case there would be no need to have environment-specific document-type constants.

Hi Rohan,
Currently, Appian only allows for primative and email constants to be configured as environment specific. For those types, the configuration can be switched at any time docs.appian.com/.../Constants.html.

If environmental specific documents are needed, an expression rule can be created to interrogate the site url and select a document based on it.

Also in the off chance that there's a valid use case requiring different Documents be referred to by some constant on an environment-by-environment basis, all this would require is to make an Integer type constant, set it to environment-specific, and point it at the Doc ID in question. Just note that if this document is being deployed from one environment to another, the value of the constant would need to be set after the deployment of the document to the new environment to ensure its ID is captured correctly.

Hi Rohan,

I don't think Appian has provided an option to make the document type constants as environment specific.

Hi Rohan,

We can enable the environment specific property for constants , but Only constants that are of a primitive type or the Email Address type can be set to environment specific.

This is not possible with document type constant i guess.
Regards,
Neha Dangi