Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Filtering Component Policy In Policy Console of a Core Component

Avatar

Avatar
Boost 1
Level 1
ved_s
Level 1

Like

1 like

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
ved_s
Level 1

Like

1 like

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile
ved_s
Level 1

04-12-2020

Hi,

In our project, we are using editable templates and core components combination as the foundation for Content As A Service Api's (CaaS). Also, we have components wherein certain dialog fields are populated using design policy values (cqDesign).

As the policies are shared across templates, in the Policy console, the Select policy dropdown shows all policies created for that component across all templates. This list is big and the large drop-down select values are not very intuitive and it is also a usability issue.

 

My question is - do we have a mechanism to filter policies that show up in the Select policy dropdown - say based on a certain flag or parameter like template name or path. I want to show only those values(policies) in the Select policy dropdown which are applicable to the current editable template.

policy.png

 

Thanks

Ved

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

564 likes

Total Posts

707 posts

Correct Reply

234 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

564 likes

Total Posts

707 posts

Correct Reply

234 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

07-12-2020

Hi @ved_s,

This will involve custom implementation and not available OOB.

Existing flow works like :

  • The policies that we create are saved in generic location - /conf/<<customproject>>/settings/wcm/policies in the hierarchy of component path and not specific to templates. 
  • Given the way it is saved and with the help of resource type of policy (which is the component's resource type), it makes sense to lists all policies configured as part of a specific component and not per template basis.
  • Datasource logic for the same is available in /libs/cq/gui/components/authoring/dialog/policy/policydatasource/policydatasource.jsp
  • Policy related data attributes are framed in /libs/cq/gui/components/authoring/dialog/policy/policy.jsp

Answers (0)