LinkedIn
Copied!

Table of Contents

Standard rules and extension points for case status

Version:

Only available versions of this content are shown in the dropdown

You can use standard rules and extension points to programmatically update, retrieve, or analyze the status of a case.

You can reference or override the following standard rules:

  • Work-.UpdateStatus — An activity that changes the status of a case based on the value that you provide.

  • Work-.WorkBasket — An activity that puts an assignment in a work queue and then calls Work-.UpdateStatus to change the case status.

  • Work-.Worklist — An activity that puts an assignment on a worklist and then calls Work-.UpdateStatus to change the case status.

  • Work-.pyStatusWork — A property that stores the current status of a case.

    Do not set the value of this property because the status that you provide might not be detected by case-dependency logic. Use an activity, flow shape, or case life cycle to set the case status instead.

  • Work-.pyElapsedStatusNew — A property that stores the cumulative time, measured in seconds, that a case has spent in any status with the New prefix.

  • Work-.pyElapsedStatusOpen — A property that stores the cumulative time, measured in seconds, that a case has spent in any status with the Open prefix.

  • Work-.pyElapsedStatusPending — A property that stores the cumulative time, measured in seconds, that a case has spent in any status with the Pending prefix.

  • Work-.Status-Resolved — A ticket that is raised when a case is resolved to communicate the status change to other business processes.

Have a question? Get answers now.

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