OOTB Adhoc not able to use in CLM framework
Unable to use the out-of-the-box adhoc case (Work-cover-SimpleCase) in the Implementation layer.
Steps to Reproduce
Use the adhoc case in Client Lifecycle Management (CLM) application Implementation layer.
A defect or configuration issue in the operating environment
A class cannot have two direct inheritance paths and cannot extend directly from CLM.
This is resolved in the field with a bridge class (for example: PegaCLMFS-Work-SimpleCase). This class inherits by Pattern from CLM and by Directed from Work-Cover-SimpleCase.
Perform the below steps to create a bridge class:
1. Create a class in the CLM structure in the ruleset. Ensure it points by Directed from Work-Cover-SimpleCase.
Below is the image for Class inheritance structure for this class.
2. At the Implementation layer, create the final class (for example: MyCo-Work-SimpleCase) and set it to 'Extend by direct' from the new CLM class created.
A few rules may need to be overwritten from the SimpleCase.
Note: PegaOBFS rules cannot be accessed. Pega supports one Pattern path (PegaCLMFS) and one Directed path (OBFS or SimpleCase). However, this depends on the logic which must be accessed. It must also be considered that PegaOBFS will be removed from the stack in Pega 7.4.
Published September 7, 2018 - Updated October 8, 2020
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.