Question

Constant value not getting deployed

Forum|Forum|2 years ago
June 5, 2024
16 replies
0 views

Hi All,
We have a constant containing a process model. Yesterday we moved that constant and process model from test to UAT. All values were present in test. After deployment, while doing sanity we found that the value of the constant was empty. All objects got imported even the constant and process model except the constant's value. We tried redeploying the constant but it said no change while inspecting. So we directly edited in model and saved the value in the constant. The deployment was done by devops person and he is a system admin. Any insights on this issue?

jayaprakashr0001

Is the constant environment specific

sarathkumr268295Author

No, its not environment specific

shubhama926776

[mention:b08a9915dde2428e9c6dfef8cba0cdd6:e9ed411860ed4f2ba0265705b8793d05]
Marking a constant as environment-specific just creates a placeholder. It needs a customization file to actually work in different environments. Without that file, the constant will be empty or have a default value.

If your constant is environment specific you have to import customization file.

sarathkumr268295Author

No, its not environment specific

stefanhelzle0001

Did you check the export and import logs?

sarathkumr268295Author

yeah we did. We had to import twice since multiple objects are being used across different applications and we were deploying multiple applications. While importing first time, the process model didnt get imported due to dependencies. When we imported 2nd time, process model got imported but constant didnt get updated and its showing no change in the log

shubhama926776

Now you gave proper insight.
1st import skipped process model due to dependencies. 2nd import brought the model but didn't update the constant's reference (like an outdated address).
AFAIK constants store metadata, which is a reference to the process model, not the actual process model itself. So, the second import brought in the process model as a separate object, but the existing constant definition (pointing to the old location in the test environment) remained unchanged.
I would recommend to edit constant value directly in UAT(Update Constant with Process Model).

S

silasf799172

Today I just faced the same issue with a Process Model constant. Apparently it seems to be a non solved issue/bug yet.

Any updates on this?

Sign up

Login with SSO

Login to the community

Login with SSO