Posted: 5 Feb 2020 19:46 EST Last activity: 16 Feb 2020 11:04 EST
Comparison tool within skin rule
My idea is regarding having a comparison tool within the skin rule which compares the properties of a component style/format with others.
The issue is that as a project grows, different developers create different instances of the component style - E.g.: Creating multiple types of Dynamic Layouts or Containers with different names. This is done to handle different UI requirements throughout the life-cycle of a project.
Often, same format configurations exist with a different name but there is no way for a developer to know unless the developer painfully combs through all existing formats and opening and comparing each format property.
This causes skin rules to bloat. PEGA has given an option to disable formats but it is difficult to do the same without having a view of where a format is being used and the impact assessment is often difficult.
An easier way would be if PEGA had a comparison tool which would alert a developer with a warning if another format already existed within the skin rule containing the same properties (margins/borders/padding etc.) as the one the developer is trying to create.
This will lead to re-use of existing formats without the burden of finding the same.
PEGA has given an option to disable formats but it is difficult to do the same without having a view of where a format is being used and the impact assessment is often difficult.
For above issue mentioned in the post, pega provided the option to list the section rules where the format is used.
Navigation path: Open any layout format --> Actions --> List Sections (Pega Platform v 8.2.1)
Regarding the idea, it is very rare that developers creating duplicate format with exact styling like borders, padding etc.. Here the requirement might fit into the existing format. but there could be very minor differences in the format styling & that makes identification process difficult to find exact duplicate format. One way to avoid this, proper documentation with description & usage of format/mixins etc.. should be captured at skin level and knowledge should be shared with the team on regular basis.
I would like to disagree on this. In complex projects, spanning multiple locations, teams, and organizations, the problem Saurabh highlighted is very real. Unlike the solution provided above where the user is made accountable to maintain documentation and ensure mixins are appropriately used, The original idea puts the onus of following best practices on the system, which can highlight similar styles based on border or text input color. the ability to compare will allow even a simple developer with no knowledge of UI to be able to code optimally leading to better design practices.
Thank you for sharing your idea here in the Pega Collaboration Center (PCC)!
I have submitted this idea on your behalf in our internal system for feature enhancements and updated your post with the associated FDBK-ID. You can take this ID to your Account Executive for next steps.
Thanks and keep the ideas coming!
Marissa | Senior Moderator | Pega Collaboration Center