Data- and Rule- rules opened in portal do not use same skin
Developer has this functionality where they were opening both Rule- instances and Data- instances in their business user portal via a pxLink control using the WBOpen activity by providing the pzInskey.
When they do this, the UI is not consistent between both rule – and data – instances. Data- instance rules (Example, Operator ID, Workbasket) uses application skin, whereas Rule – instance rules (Example, paragraph, MapValue) uses Designer Studio skin.
Developer would like them both to have consistent UI and prefers the designer studio skin for the data- rules as well.
Steps to Reproduce
- Create links in user portal to launch at least one rule - instance rule and one data- instance rule using 'OpenURLInWindow' action using WBOpen activity and providing pzInskey as key.
What appears is the correct behavior (Rule- instances showing with designer studio skin and Data- instances showing with application skin) and intentional. But, one can override an existing out of the box rule (baseclass.pyUseDeveloperSkin and Rule-pyUseDeveloperSkin) to suit their needs.
Perform the following local-change:
There exists pyUseDeveloperSkin in both baseclass and Rule- class. One can play with either one of them or both or create a new one in Data- to achieve what they want.
The activity that looks for this pyUseDeveloperSkin rule is called GetWorkStyle
If one modifies either the baseclass.pyUseDeveloperSkin to be true or creates a new Data-.pyUseDeveloperSkin as a save as of Rule-, the Data- rules show with designer studio skin. However, as a side effect, the same occurs in the portal. See screen shots below.
Alternatively, if the goal is to make sure both Rule- and Data- skin matches, one can modify the Rule-.pyUseDeveloperSkin to false.
Now Rule- and Data- look alike (no designer studio skin)
One can choose whichever option is suitable to their needs.
0% found this useful