Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Suggested Answer
Replies
8 replies
Answers
1 answer
Subscribers
8 subscribers
Views
7107 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Is there any way to keep a Constant the same value in a particular environment?
lisak
over 8 years ago
Is there any way to keep a Constant the same value in a particular environment? For example, my Development environment has a constant with the value "X" and my QA environment has the same constant with the value "Y". When I export/import the application from Development to QA, the constant in QA gets overwritten from "Y" to "X" and needs to be manually changed back.
Is there any way to confirm that the QA's constant retains its value of "Y"?
OriginalPostID-219498
OriginalPostID-219498
Discussion posts and replies are publicly visible
0
Tyler Criste
Appian Employee
over 8 years ago
Check out this page:
forum.appian.com/.../Environment_Specific_Properties.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
lisak
over 8 years ago
Thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
phanibabuk
over 8 years ago
If the constant is already deployed to QA the first time, what is the need to redeploy it again?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mohammedz
Certified Senior Developer
over 8 years ago
@lisak
When you move any existing component the content will get override. For example if u declare constant value of type process model I'd or some other unique keys all environments will have thier unique id defined.
In such case if we try moving a package let's say constant has process model I'd 501 SIT ... after moving it will override in QA .. Anyhow we need to keep a track on post deployment steps like Constant needs to be updated
Thanks ..!!!!!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Karthik
over 8 years ago
Create constants per environment and access the constants using a rule. The rule that you are calling to get a value should be able to figureout the environment that is being executed and return the value of a specific constant.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
lisak
over 8 years ago
Thanks, @Kathikeyans75 . That's actually what I'm trying to figure out right now - our environment specific constants were improperly set up so I'm trying to fix it so they don't get overwritten with each migration.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
erickp
over 6 years ago
in reply to
Tyler Criste
Hello Tyler, this URL is not working anymore. Do you have the latest one?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Carlos Santander
A Score Level 2
over 6 years ago
in reply to
erickp
The way to do this these days is by using environment specific constants:
docs.appian.com/.../Application_Deployment_Guidelines.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Reject Answer
Cancel