Skip to main content
Contact a Moderator

Question

2
Replies
3777
Views
 Divya Tejaswi Potukuchi (DivyaTejaswiP) Legato Health Technologies
Legato Health Technologies
IN
DivyaTejaswiP Member since 2017 11 posts
Legato Health Technologies
Posted: June 19, 2018
Last activity: July 6, 2018
Posted: 19 Jun 2018 9:24 EDT
Last activity: 6 Jul 2018 3:30 EDT
Closed

assignment & work object

Hello,

Can an assignment be without workobjects? and can an worobject exist without assignement? justify with explanation.

Thanks in advance.

Low-Code App Development Enterprise Application Development Dev/Designer Studio User Experience
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 19 Jun 2018 11:01 EDT
Anil Vanaparthi (vanaa) PEGA Senior Manager, Software Engineering, Case Management
Pegasystems Inc.
IN

Assignment exist without workobjects: An assignment cannot exist without a work object, assignments can only be created for a flow or case, So they exist with work object.

worobject exist without assignement: yes, workobjects can exist without assignments, there can be cases where there isnt any need of an assignment. Cases like which have no assignment shape or all automated steps. 
Posted: 3 years ago
Posted: 19 Jun 2018 11:10 EDT
Krishna Chaitanya Abburi (KC-Abburi) Bits In Glass
Bits In Glass
GB
Assignment:
Assignment is a pause in the flow and it signifies that a person or external system must act on a work object before the flow can progress.
An assignment is an instance of a class derived from the Assign- class. 
In certain situations assignments can be processed completely or in part by a Process Commander agent rather than by a person
Assignments are created by a flow operating on a work object, but they are not themselves part of the work object.
The system saves data relating to an assignment in instances of the Assign-Workbasket class, Assign-Worklist class, or other subclasses of the Assign- base class. Means whenever a workobject reaches an assignment, it creates an instance of respective Assign-* class.
Show More
Assignment:
Assignment is a pause in the flow and it signifies that a person or external system must act on a work object before the flow can progress.
An assignment is an instance of a class derived from the Assign- class. 
In certain situations assignments can be processed completely or in part by a Process Commander agent rather than by a person
Assignments are created by a flow operating on a work object, but they are not themselves part of the work object.
The system saves data relating to an assignment in instances of the Assign-Workbasket class, Assign-Worklist class, or other subclasses of the Assign- base class. Means whenever a workobject reaches an assignment, it creates an instance of respective Assign-* class. This instance stores all the assignment pertaining information rather than work object itself.
Work Object:

Work object is an single object which cannot hold other object. In versions of Pega 7, think of work objects as "cases". Cases are instances of your case types.

At a high-level, case type instance = work object = work type instance. Technically, a work type class will directly inherit Work-Object-, and a case type class will directly inherit Work-Cover-.

Thanks

 


Show Less

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

Pega Collaboration Center 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