Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

pySLAGoal and pySLADeadLine values are setting null



The user has upgraded their application from 6.3 to 7.2.

In 7.2 version, pySLAGoal and pySLADeadLine values are setting null in step 5 of Resolve activity. So, those values are getting blank in the case id after resolution.

And, this is not there in 6.3 version.

Error Messages

Not Applicable 

Steps to Reproduce

  1. Create any work case.
  2. Resolve the case.
  3. Check for Goal and Deadline values in the harness.

Root Cause

In Work-.Resolve Activity,Step-5 was added because there is no SLA event scheduled to take place anymore, since the work object has been resolved.


Below is the Local Change:
  1. Do a save as of the ‘UpdateStatus’ activity into your own RuleSet and workpool, you can delete all the steps present in the newly saved activity.
  2. Add a step ‘property-set’ method , set the pySLAGoal and pySLADeadine values into local variables.
  3. Call ‘Work-.UpdateStatus’ activity, make sure that input parameters are passed properly.
  4. Add a step ‘property-set’ method , set the local variables values to pySLAGoal and pySLADeadine.

Published October 7, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us