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.

Discussion

 Piyush Agrawal (piyush.agrawal)
Inovar
PRPC Certified
Inovar
SA
piyush.agrawal Member since 2015 8 posts
Inovar
Posted: Apr 27, 2016
Last activity: Feb 5, 2017
Posted: 27 Apr 2016 13:19 EDT
Last activity: 5 Feb 2017 2:29 EST
Closed

Questions related to Case Type, Framework - Implementation (Not a coverable class)
I have created a parent Case which has 1 child case (defined in the case type as coverable case)
FW Layer
----------
Case Type 1 (Parent) (XX-FW-Work-classA
Stage 1 (step 1) Stage 2 (step 1 , Step 2) Stage 3 (resolved)
At stage 2, step 2, I have a flow (FlowSTG2Step2) that has a shape to create the child case (Case Type 2) through the flow shape create Cases.
Case Type 2 (Child) XX-FW-Work-classB
Implementation Layer
------------------------
Case Type 1 (Parent) XX-DIV-XX-Work-ClassA
Stage 1 (step 1) Stage 2 (step 1 , Step 2) Stage 3 (resolved)
At stage 2, step 2, I have referenced the FW layer flow (FlowSTG2Step2).
Case Type 2 (Child) XX-DIV-XX-Work-ClassB
Question 1- Do I always need to create the Case Type rule in imp Layer ? duplicate as framwork ?
Question 2- When I am running the application from implementation layer and reaches the stage 2 to launch the child case pega gives me an error says "XX-FW-Work-classA not a covered class". If I save the flow(FlowSTG2Step2) in implementation layer it works fine.
Qustion 3- Do I need alternate stage to launch child case ?
To see attachments, please log in.
Case Management

Posted: 8 years ago
Posted: 27 Apr 2016 13:57 EDT
Phani Sahukaru (sahup1)
Pegasystems Inc.
Phani Sahukaru
Pegasystems Inc.
IN
 
Question 1- Do I always need to create the Case Type rule in imp Layer ? duplicate as framwork ?
we need to create a case type in impl layer
 
Question 2- When I am running the application from implementation layer and reaches the stage 2 to launch the child case pega gives me an error says  "XX-FW-Work-classA not a covered class". If I save the flow(FlowSTG2Step2) in implementation layer it works fine. 
have to update the class name (coverable item) in parent case of impl layer to get away from the issue.
Show More
 
Question 1- Do I always need to create the Case Type rule in imp Layer ? duplicate as framwork ?
we need to create a case type in impl layer
 
Question 2- When I am running the application from implementation layer and reaches the stage 2 to launch the child case pega gives me an error says  "XX-FW-Work-classA not a covered class". If I save the flow(FlowSTG2Step2) in implementation layer it works fine. 
have to update the class name (coverable item) in parent case of impl layer to get away from the issue. dymanic class referening would be helpful.
 
Qustion 3- Do I need alternate stage to launch child case ?
we can create child cases on alternate stage if required (business use case) example adhoc case [general request].

Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 29 Apr 2016 10:35 EDT
Piyush Agrawal (piyush.agrawal)
Inovar
PRPC Certified
Inovar
SA

Thank you for the reply. 

Regarding your reply to Question 2, there is no option to specify the class name via dynamic class referencing using OOB create child shape as it is a dropdown.

 

 

Anyone has any other idea?

To see attachments, please log in.
Posted: 7 years ago
Posted: 5 Feb 2017 2:27 EST
Sreenivasa Kilaru (Sreenik)
Coforge DPA Australia Pty Ltd
Solution Architect
Coforge DPA Australia Pty Ltd
AU

Hi,

I see your answer in Question 1. I have few more questions following to it.

1. Does implementation layer pyDefault Case Type rule should be deleted which is created by New Application wizard and then SaveAs same rule from corresponding framework class?

2. Above steps applicable for all case types?

3. Does WorkParties rules also should be removed from implementation layer which are created by application wizard. SaveAs them from FW layer if needed. Am I right?

4. Are there any specific steps/wizard to extend FW layer case to implementation layer?

5. In implementation CaseType rule, Class names in Coverable work types is not allowing dynamic class reference. It is expecting hard coded class name. So following SaveAs of FW CaseType, Do these classes should be updated with implementation class names?

To see attachments, please log in.
Posted: 8 years ago
Posted: 29 Apr 2016 15:17 EDT
Phani Sahukaru (sahup1)
Pegasystems Inc.
Phani Sahukaru
Pegasystems Inc.
IN

Pega version?

we generally select the case type as Other and specify the flow name, class name from data page defined on requestor scoped page.

To see attachments, please log in.
Posted: 7 years ago
Posted: 5 Feb 2017 2:29 EST
Sreenivasa Kilaru (Sreenik)
Coforge DPA Australia Pty Ltd
Solution Architect
Coforge DPA Australia Pty Ltd
AU

Hi,

I see your answer in Question 1. I have few more questions following to it.

1. Does implementation layer pyDefault Case Type rule should be deleted which is created by New Application wizard and then SaveAs same rule from corresponding framework class?

2. Above steps applicable for all case types?

3. Does WorkParties rules also should be removed from implementation layer which are created by application wizard. SaveAs them from FW layer if needed. Am I right?

4. Are there any specific steps/wizard to extend FW layer case to implementation layer?

5. In implementation CaseType rule, Class names in Coverable work types is not allowing dynamic class reference. It is expecting hard coded class name. So following SaveAs of FW CaseType, Do these classes should be updated with implementation class names?

To see attachments, please log in.

Related content:

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