Question
Bank Of America
IN
Last activity: 17 Sep 2021 10:00 EDT
usage of pyworkpage in data layer level what is best design
hi Pega community,
Pega theory says to develop assets which support max reusability and extensibility.
In my scenario i have tried to follow the following design where i see some challenge when controlling display of the fields.
we have a case (BBB-TTT-CCC-Work-MMMM-DDD-US)
in this we have created Data Layers to hold related information
pyWorkPage(BBB-TTT-CCC-Work-MMMM-DDD-US)
-->BBB(BBB-TTT-CCC-Data-BBB)
-->XXX(BBB-TTT-CCC-Data-XXX)
--->YYY(BBB-TTT-CCC-Data-ZZZ)
The Workflow UI is using the YYY Page context and rendering Data ,however the business scenario needs fields conditional visible based on certain events which are in workpage context.
so what is best approach to achieve this.
-->
1.refer the workpage in when rule of data layer.
easy but establish workpage presence at data layer making view not reusable.
2.Create a property at data layer which declaratively find out the workpage property presence and set in data layer.
complex but reference of workpage problem again comes.
3.when event happens populate a property at data layer.
moderate but maintenance issues.
4.Circumstance the section based on above property.
but if there are many events its again maintenance issue.
hi Pega community,
Pega theory says to develop assets which support max reusability and extensibility.
In my scenario i have tried to follow the following design where i see some challenge when controlling display of the fields.
we have a case (BBB-TTT-CCC-Work-MMMM-DDD-US)
in this we have created Data Layers to hold related information
pyWorkPage(BBB-TTT-CCC-Work-MMMM-DDD-US)
-->BBB(BBB-TTT-CCC-Data-BBB)
-->XXX(BBB-TTT-CCC-Data-XXX)
--->YYY(BBB-TTT-CCC-Data-ZZZ)
The Workflow UI is using the YYY Page context and rendering Data ,however the business scenario needs fields conditional visible based on certain events which are in workpage context.
so what is best approach to achieve this.
-->
1.refer the workpage in when rule of data layer.
easy but establish workpage presence at data layer making view not reusable.
2.Create a property at data layer which declaratively find out the workpage property presence and set in data layer.
complex but reference of workpage problem again comes.
3.when event happens populate a property at data layer.
moderate but maintenance issues.
4.Circumstance the section based on above property.
but if there are many events its again maintenance issue.
Any ideas or direction you can suggest.
EAI Systems
SA
@Nerella Dileep As per your below case class information,
A case (BBB-TTT-CCC-Work-MMMM-DDD-US)
in this we have created Data Layers to hold related information
pyWorkPage(BBB-TTT-CCC-Work-MMMM-DDD-US)
-->BBB(BBB-TTT-CCC-Data-BBB)
-->XXX(BBB-TTT-CCC-Data-XXX)
--->YYY(BBB-TTT-CCC-Data-ZZZ)
Is BBB, XXX, YYY(ZZZ) data fields directly in the pyWorkPage class if so you can use conditions for display.
Is YYY has a direct inheritance of XXX and BBB has a direct inheritance for XXX?
Bank Of America
IN
@bendr1 hey thank for taking time to answer my question.
To have better understanding of scenario
Is BBB, XXX, YYY(ZZZ) data fields directly in the pyWorkPage class if so you can use conditions for display.--[@Nerella,Dilee]yes they are fields created as data relation ships(properties not bringing from Data Pages ) just three layers of embeded pages. if we use condition since layer is in data class system only lets to create in data layer class only however the display of a field in UI is driven by a attributed which is on very top layer.
workpage --layer1
BBB
XXX
YYY are depths within workpage and YYY display attributes are conditionalized by attributes of workpage which is making me to create a hardcoded workpage reference in when rules.so i am try to understand if there is any better approach rather than using hardcode reference.
Is YYY has a direct inheritance of XXX and BBB has a direct inheritance for XXX?
[@Nerella Dileep] lets assume they are independent classes just we are using composition in workpage.
EAI Systems
SA
@Nerella Dileep If YYY class fields to be displayed based on some conditional values of pyWorkpage then you can place that condition on the YYY UI embedded in the pyWorkPage section/view. By this, you don't require to hard code pyWorkPage inside YYY display attributes.
If only certain fields of this class to be displayed for values of pyWorkPage then separate the fields for example, Display fields irrespective of conditional values and fields which depend on conditional values as two separate sections/views.
Updated: 22 Jun 2021 2:15 EDT
Bank Of America
IN
Yes so in this approach we are propagating data to embedded levels or grouping fields together. However in business scenarios approach1 if i understand your intention correctly then we also have to take additional responsibility propagate that data.
second approach also involves grouping of conditional driven data which might not be case always.
some where we might again bring to that hardcode referencing.
Bank Of America
IN
Found one more Approach as well using the page referencing functions such as getTopLevelPage,getParentPageReference can be used to execute the when rules based on context we design
there is a some kind of risk when doing changes but this appears to be a efficient way instead of propagating things to each embeded level.
Updated: 17 Sep 2021 10:00 EDT
Rulesware
PE
This is a question I have been pondering for a long time.
As you say, the data layer must be -Work agnostic because it must work independently of the work being done (the current case type), moreover data just exist, not work.
But also this poses a challenge due to business requirements. For example, they may need to condition the visibility of a -Data field (in a -Data standard view/section) according to the current case.
One solution I have found is to create a SUBCLASS of -Data-XXX. For example, in the class -Data-BankAccount we will store the independent and clean rules independently of the WORK being done (like standard views/sections), and create a -Data-BankAccount-MyCaseType where I will specialize the -Data-XXX rules that have a particular modification for the particular MyCaseType.
Also, remember to specialize just the minimal piece that really needs to be specialized. For example, If you have a big section in -Data with two buttons, but for -MyCaseType you need a third button, it is better to replace the layout that contains the buttons for an embedded section and specialize just that sub-section in -Data-BankAccount-MyCaseType.
This is a question I have been pondering for a long time.
As you say, the data layer must be -Work agnostic because it must work independently of the work being done (the current case type), moreover data just exist, not work.
But also this poses a challenge due to business requirements. For example, they may need to condition the visibility of a -Data field (in a -Data standard view/section) according to the current case.
One solution I have found is to create a SUBCLASS of -Data-XXX. For example, in the class -Data-BankAccount we will store the independent and clean rules independently of the WORK being done (like standard views/sections), and create a -Data-BankAccount-MyCaseType where I will specialize the -Data-XXX rules that have a particular modification for the particular MyCaseType.
Also, remember to specialize just the minimal piece that really needs to be specialized. For example, If you have a big section in -Data with two buttons, but for -MyCaseType you need a third button, it is better to replace the layout that contains the buttons for an embedded section and specialize just that sub-section in -Data-BankAccount-MyCaseType.
Doing this way -Data-XXX will be clean, work-agnostic. Your specializations will be stored in -Data-XXX-MyCaseType for -Work-MyCaseType. Furthermore, if you follow an application-components architecture, every application component will encapsulate its -Data-XXX-CaseType, so that the implementation application will only see -Data-XXX and not the subclass.
I would like to hear opinions on this approach. I don't know if it's the best but it works for me.