I am trying to find the Best Practice for code promotion for this scenario - we

senthilar over 10 years ago

I am trying to find the Best Practice for code promotion for this scenario - we have live instances in higher environment. Now, for an enhancement, we have made CDT changes - added couple of elements. These new elements are mapped to existing UI for the user to enter values.

Now, when we promote this build, the existing instances won't have the newer instance of the CDT - so they won't have these 2 elements. But they will still call the latest version of the UI Rule which refers to the newly added elements. So they would fail.

How do we take care of this scenario. The Process Upgrade utility would not be of help here.

Discussion posts and replies are publicly visible

0 Conor Cahill
Certified Lead Developer
over 10 years ago

Depending on the necessity of the new fields, you can configure your UI Rule to account for older versions (e.g. not showing certain input fields or grid columns if the corresponding CDT field does not exist).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 senthilar over 10 years ago

@conorc - apart from handling this in logic, thought of checking what the Best Practices are for this scenario. Couldn't find anything in documentation for handling CDT changes
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel