Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Divya Tejaswi Potukuchi (DivyaTejaswiP)
Carelon Global Solutions
Senior Software Engineer II
Carelon Global Solutions
IN
DivyaTejaswiP Member since 2017 12 posts
Carelon Global Solutions
Posted: Jun 19, 2018
Last activity: Jul 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.

To see attachments, please log in.
Low-Code App Development
Dev/Designer Studio
User Experience

Posted: 6 years ago
Posted: 19 Jun 2018 11:01 EDT
Anil Vanaparthi (vanaa)
PEGA
Senior Manager, Services Engineering
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. 

To see attachments, please log in.
Posted: 6 years ago
Posted: 19 Jun 2018 11:10 EDT
Krishna Chaitanya Abburi (KC-Abburi)
LTI Mindtree

LTI Mindtree
IN
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
To see attachments, please log in.

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