Changes Of BUSINESS PARAMETERS Are Not Reflected When The Application Is Re-deployed
Last updated on OCTOBER 23, 2017
Applies to:Oracle Process Cloud Service - Version N/A to N/A
Information in this document applies to any platform.
Changes of BUSINESS PARAMETERS are not reflected when the application is re-deployed
When a BUSINESS PARAMETER is changed to a new value, this new value is ignored when the PCS application is re-deployed. It still reflects the previous (first ever set) value. An exported application shows that the organization.xml (where the BUSINESS PARAMETERS are defined) is indeed updated. But the BPMN engine still uses the old value.
Changes of BUSINESS PARAMETERS to reflected when the application is re-deployed
The issue can be reproduced at will with the following steps:
1/ Deploy a PCS application which contains a BUSINESS PARAMETER with an initial value
2/ Run the application and confirm that the form displays "initial value" as the content of the business parameter "MY_BUSINESS_PARAMETER".
3/ Change to the PCS editor and change "MY_BUSINESS_PARAMETER" to "something new" for example.
4/ Save changes and re-deploy (or undeploy and deploy) the application using the same revision id.
5/ Start the application again. It will be observed that the form still displays "initial value". -> This is NOT the expected behavior
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms