Support Article
pxUrgencyWork is empty for cases created using a dataflow
KCP-547
Summary
The value of pxUrgencyWork property is empty for cases that are created using a dataflow. However, the value of pxUrgencyWork is set for cases that are manually created.
Error Messages
Not Applicable
Steps to Reproduce
Unknown
Root Cause
An issue in the client application code or rules.
When the value of pxUrgencyWork is set, the value of Urgency is displayed on the UI. However, the value of pxUrgencyWork property is set if the Work-.pxUrgencyWork declare expression is triggered. If a dataflow is used to create a case, the declare expression is not triggered because no forward chaining occurs in the dataflow. Hence, the value of pxUrgencyWork property is empty. However, if a case is manually created, the value of pxUrgencyWorkClass is updated. Therefore, when a service-level agreement (SLA) is triggered again, the Work-.pxUrgencyWork declare expression is invoked because the value of pxUrgencyWorkClass is considered than that of pxUrgencyWork property.
Resolution
Here's the explanation for the reported behaviour:
Dataflows do not support declare expressions. Running an activity in a dataflow context disables the inference engine that is responsible for triggering declare expressions.
Tags:
Published December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.