Is it possible to have a template policy available globally?

[smithchar]

I'd like to have a singular template policy usable by templates across multiple groups. Is it possible to configure a policy in the global settings, and then use it templates elsewhere? If not, is there some other means to accomplish the same?

[arunpatidar]

I don't think so it is possible, template can have policy references within same tree e.g. /conf/myproj/settings/wcm

i,e. templates inside /conf/myproj/settings/wcm/templates can reference policies defined at /conf/myproj/settings/wcm/policies 

[Rite18]

@smithchar when you say global understanding is between projects if yes consider storing policies in locations such as /conf/global/settings/wcm/policies so that they are reusable across different projects/ templates. I never tried though but worth checking it 

[smithchar]

Yeah, this is what I was to accomplish, and your approach is what I was trying prior to asking. Doesn't appear to be working, which is unfortunate.

[Rite18]

@smithchar  good to know then question what is the use case around  /conf/global/settings/wcm/policies  if  it is can not be used across projects/template . can you open ticket with Adobe support and check 

[smithchar]

The intent was to use it for multiple templates across projects. This would allow us to centrally manage the policy while allowing template authors to customize their templates for the their project needs.

> can you open ticket with Adobe support and check 

I've reached out to the Adobe support channel through my employer. I haven't opened a ticket yet, but I could I suppose.

[Rite18]

yeah but it is not working , please share your finding and Adobe response to this thread  @smithchar  thx.

[kautuk_sahni]

@smithchar Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[smithchar · Accepted solution]

I was able to open a ticket with Adobe and get some direction on this. Ultimately, I was able to get something to work, but I'm unsure if it is the ideal implementation, so I'd rather not share it here and lead someone astray. Additionally, there's no Adobe authored documentation to this scenario that I was able to find. Ideally, Adobe could take some time to review this scenario to see if there truly is a documentation gap, and provide a recommended implementation.