Declare Expression errors when calling Decision Table that has missing properties. V8 behaviour is different from v7.
Hi All,
We're currently upgrading from v7.3.1 to v8.6, and have hit a problem where a declare expression fires, but then errors because it calls a decision table which has missing properties: 'Goal seek requires missing input property'.
I thought a good workaround would be to update the DE to set 'Value of' = @ObtainValue so that I could set the AllowMissingProperties parameter myself, but then found that the DE doesn't fire because it doesn't sense any properties have changed.
The temporary workaround has been to set Param.AllowMissingProperties = true immediately before the DE fires, but this isn't ideal as I'll have to identify each place this might happen.
Root cause is that ObtainValue has been changed. Does anyone know why?
thanks Chris
***Edited by Moderator Marije to add Capability tags***
Updated: 10 May 2022 10:56 EDT
Pegasystems Inc.
GB
@ChrisWang I'm assuming that you are using the steps outlined in this post?
I found that there was a backward compatibility issue which has been fixed in Pega 8.6.1 (BUG-639912)
In your current version, any null values as inputs in the decision tables are being skipped if "Allow Missing properties" is not checked. This behavior is different from previous versions.
In Pega 8.6.1 the Decision table null input handling has been updated for backward compatibility. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
Your options are to either:
1. continue using your workaround :
To handle missing property value error for decision table columns, AllowMissingProperties parameter has to be set to true. This parameter is now handled for ObtainValue function in 8.5.x and the similar fix has to be handled for pxEvaluateDecisionTable function. Set the AllowMissingProperties in each activity call by selecting the checkbox (Utility function available in local which fetches the activities where the checkbox was not selected). Set a parameter to the DT - pxEvaluateDecisionTable , which can consume property AllowMissingProperties
@ChrisWang I'm assuming that you are using the steps outlined in this post?
I found that there was a backward compatibility issue which has been fixed in Pega 8.6.1 (BUG-639912)
In your current version, any null values as inputs in the decision tables are being skipped if "Allow Missing properties" is not checked. This behavior is different from previous versions.
In Pega 8.6.1 the Decision table null input handling has been updated for backward compatibility. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
Your options are to either:
1. continue using your workaround :
To handle missing property value error for decision table columns, AllowMissingProperties parameter has to be set to true. This parameter is now handled for ObtainValue function in 8.5.x and the similar fix has to be handled for pxEvaluateDecisionTable function. Set the AllowMissingProperties in each activity call by selecting the checkbox (Utility function available in local which fetches the activities where the checkbox was not selected). Set a parameter to the DT - pxEvaluateDecisionTable , which can consume property AllowMissingProperties
2. Best would be to update your environment to 8.6.1:
Please find below article pointing INC-164002 for reference. https://docs-previous.pega.com/pega-861-patch-resolved-issues-0
CMC Markets
GB
@MarijeSchillern Hi Marije, thanks for your reply. We are on 8.6.0 so I'm hopeful that the patch you mentioned might help. We will upgrade to 8.6.1 or higher shortly.
My scenario was different from the post you referenced. I have a declare expression which sets a property value using 'Result of Decision Table'. The decision table errors with 'Goal seek requires missing input property'. I am not using ObtainValue directly myself, but noticed that this function had been modified between v7 and v8. The sequence of rules/functions seems to be Declare Expression -> evaluateDecisionTable -> ObtainValue -> Decision Table where the error is happening.
Chris
Pegasystems Inc.
GB
@ChrisWang hopefully the issue will be resolved with the update.
If you could confirm the outcome in this post that would be great.