Application Accelator not giving right Class names
Application Accelator not giving right Class names !
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
US
If the accelerator is giving you class names that are not quite as desired, you can try using the class rename wizard after completing the generation.
This can be done with
Pega > System > Tools > Refactor Rules > Rename a class
Highmark
US
We are trying to create new implantation layer on Top of existing FW layer.
The new implementation layer class names is all wrong with "FW " appended in the text.
did anyone else face this issue?
Pegasystems Inc.
US
Hello Sneha, Could you provide screen shots of the application accelator wizard steps and mention the version being used?
Highmark
US
Hi Row
we are on 6.3 SP1 Care management FW.
Accelerator snapshots , We are doing New Implementation Layer on top on existing FW layer.
The wrong text is highlighted. Let me know if you need more information.
Right class name is the one without that highlighted text.
HMK-- Is our Organization
CLS- Is our Division.
We need new implementationUMMedBHIBC
Ideally the class names should be
HMK-CLS-UMMedBHIBC-Work with direct inheritance to existing FW class HMK-FW-UMFW-Work
Hi Row
we are on 6.3 SP1 Care management FW.
Accelerator snapshots , We are doing New Implementation Layer on top on existing FW layer.
The wrong text is highlighted. Let me know if you need more information.
Right class name is the one without that highlighted text.
HMK-- Is our Organization
CLS- Is our Division.
We need new implementationUMMedBHIBC
Ideally the class names should be
HMK-CLS-UMMedBHIBC-Work with direct inheritance to existing FW class HMK-FW-UMFW-Work
HMK-CLS-UMMedBHIBC-Work-AuthRequest with direct inheritance to existing FW class HMK-FW-UMFW-Work-AuthRequest
Pegasystems Inc.
US
Sneha,
You selected "Built on Framework" UMFW and are saying that the FW-UMFW piece of the class names are incorrect, although they are on classes extending classes from the framework. That's exactly what I would expect. Is your concern just with the name? You can definitely change that after finishing the wizard.
Thanks,
Mike
Pegasystems Inc.
US
Concur with Mike. You also might want to look at the class paths when you don't have the framework in the loop and when using an OOTB framework you have installed
Highmark
US
Implementation layer class name should not have FW-UMFW
Implementation class should be HMK-CLS-UMMedBHIBC-Work-AuthRequest this is the class group which will direct inherit to HMK-FW-UMFW-Work-AuthRequest.
HMK-CLS-UMMedBHIBC-Work-AuthRequest-Inpatient is a worktype belongs to the above class group this will have direct inheritance to HMK-FW-UMFW-Work-AuthRequest-Inpatient
Both these classes are direct inheritance they are not in pattern inheritance.. they should not have FW-UMFW appended in the name.
Workgroup and all the belongs to work group classes and also implementation layer class will all be pattern inheritance with same naming structure like
HMK-CLS-UMMedBHIBC-
HMK-CLS-UMMedBHIBC-Work
HMK-CLS-UMMedBHIBC-Work-AuthRequest
HMK-CLS-UMMedBHIBC-Work-AuthRequest-Inpatient
HMK-CLS-UMMedBHIBC-Work-AuthRequest-Outpatient
HMK-CLS-UMMedBHIBC-Work-AuthRequest-Pharmacy
Pega takes Pattern inheritance as precedence. followed by direct.
If implementation layer also has FW in it.. what is the need of FW layer.
Highmark
US
Accelerator does not give option to edit the class names.. its creating rules with that.. and once a class group is created with the key mapping.. its a log of effort to delete all the classes and rename them also the other rules that are created under those classes...
Infosys
AU
I agree with you Sneha that implementation classes should not have "FW" appended. I have tried generating a new implementation on top of an existing framework in Pega 7.1.7 and it did not include "FW" in class names, even for the case types that are inherited from framework.
Here are the examples of classes I got:
Implementation Class - Inherits From
OrgName-BPImpl-Work - OrgName-FW-BaseFW-Work
OrgName-BPImpl-Work-Amend - OrgName-FW-BaseFW-Work-Amend
Are you sure you have provided correct values to fields like name, Class etc. in wizard?
Murali...
Accepted Solution
Pegasystems Inc.
US
If the accelerator is giving you class names that are not quite as desired, you can try using the class rename wizard after completing the generation.
This can be done with
Pega > System > Tools > Refactor Rules > Rename a class