Close popover
Nizam Mohammed (NizamM46)
Axiom Technology Group
Technical Manager
Axiom Technology Group
NizamM46 Member since 2017 26 posts
Axiom Technology Group
Posted: February 4, 2019
Last activity: February 6, 2019

Need details on the UserWorkForm HTML fragment

Hi Team,

I have one implementation application with three different rulesets. It was built on a single framework. Each team is working on different ruleset and the entire application is part of a single implementation application.

Problem statement: I need to call a common javascript function across all the portals/screens and other UI elements of TeamA application. I have placed this code in UserWorkForm HTML fragment. Team A is working on RulesetA, TeamB is working on RulesetB and TeamC is working on RulesetC. It was working as expected when application stack holds only my current ruleset. But lets say if the other rulesets are added to my application stack, my UserWorkForm is not getting picked. It will pick the top one from the above stack. This was working as per the rule resolution algorithm.

Now, how to make sure that my javascript code from UserWorkForm of my ruleset will be picked irrespective of any number of rulesets on top of my ruleset stack?

Options which I have now:

1. Need to create a new HTML fragment and add it to all the portal harness rules, screen flow and work flow harness rules. If there is any new harness created, it should be added by default to the harness else it wont pick my JS rules.

2. The other option is to maintain three different fragments as shown below in the UserWorkForm. It is like creating nested fragments as shown below.

Main UserWorkForm:

<pega:include name="TeamAFragment" type="fragment"/>

<pega:include name="TeamBFragment" type="fragment"/>

<pega:include name="TeamCFragment" type="fragment"/>

They was a confusion that the UserWorkForm should only be used for framework applications and cannot used for implementation layer. I don't see any problem with approach two as it is future proof as compared with approach 1 in the above case. If I use approach 1, I need to call the HTML fragment in every new harness of the application. Is there any alternative for this? Which would be the best approach in my scenario? Branching should solve this problem but the development will happen with individual rulesets and stack is getting updated at the later point of time.

Note: All the three teams are working in parallel on three different requiremnts of a single implementation in the individual rulesets. Any application can be moved to higher environments at any given time.

Please suggest your thoughts on this.

Pega Platform Low-Code App Development User Experience
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.