Support Article
Work party index does not populate the Status column in a table
SA-80174
Summary
Work party index does not populate the Status column in a table.
Error Messages
Not Applicable
Steps to Reproduce
- Add a party to a work object.
- Ensure that when the party is written to the party table, the pyStatusWork of the work object propagates to the index table.
- Create an Alternate stage that expires the case by setting the status to Resolved-Expired.
- Create a local action that expires the case.
Root Cause
For any declarative, the system only views the Context page for changes to determine if it must fire. Though the system can retrieve changes on other pages (for example, parent) when it triggers, the declarative will not fire if the changes are on a non-context page.
Resolution
Here’s the explanation for the reported behavior:
The Context page for the Declarative is pyWorkParty().
If the only change for a particular action is to be made to a property on the parent page (in this case, pyWorkPage), then that change alone will not cause the Index rule to fire even when that parent's property is referenced by the Index rule. If the Index rule triggers for a different reason (for example, a property on the pyWorkParty() page changed), then the parent property value is captured at that time.
Published August 15, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.