PH45827: A STEP USING A PRECONDITION WILL ATTEMPT TO RESOLVE VALUES OF PROPERTIES NOT USED IN THE PROCESS EXECUTION

APAR status

• Closed as program error.

Error description

• Steps to reproduce:
  
  1) Create a Component Process:
   Operational No Version
   Single 'Shell Step' doing an 'echo hello
   Precondition:
   properties.get("environment.name") !== undefined &&
   properties.get("environment.name") !== null &&
   properties.get("environment.name") !== ""
  
  2) Create an Environment on an Application with an 'Environment
  Property' called 'someproperty ', with the value
  '${p:unresolvable.property}'
  3) Run a deployment against the Environment
  
  Expected Result:
  The Process Execution and Step should end in 'Success'.
  
  Actual Result:
  The Process Execution ends in Success, but the Step shows
  'Precondition Failed', and the Success indicator will be grey.
  
  In the server logs you will see the following message:
  Caused by:
  com.urbancode.ds.subsys.process.property_context.UnresolvedPrope
  rtyException: The following properties were left unresolved:
  ${p:unresolvable.property}, ${p:unresolvable.property},
  ${p:unresolvable.property}. Please ensure their values have been
  given and that the property names are spelled correctly
  
  
  
  Problem:
  The Precondition should not try to resolve Values of Properties
  that are not being used in the Process Execution / that have not
  been defined on the Step, Precondition, or other scope called
  during the Process Execution.
  

Local fix

• Use ${p?:propName} which will resolve this issue.
  Documentation reference:
  https://www.ibm.com/docs/en/urbancode-deploy/7.1.2?topic=propert
  ies-referring
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Deploy Server Web UI Users                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A Step using a Precondition will attempt to resolve Values   *
  * of Properties not used in the Process Execution.             *
  * For example:                                                 *
  * If Properties have been defined on the Environment scope,    *
  * with a Value like '${p:unresolvable.property}', and you have *
  * a Precondition script that attempts to get the               *
  * environment.name, the Step will fail because it cannot       *
  * resolve  '${p:unresolvable.property}'.  Even if you have not *
  * attempted to use / resolve the Property that has '           *
  * '${p:unresolvable.property}',' as it's value.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fix is provided in IBM UrbanCode Deploy 7.3.0.0              *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.3.0.0
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels