pxUrgencyWork is empty for cases created using a dataflow
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.
Steps to Reproduce
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.
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.
0% found this useful