We would like to be able to have a story use an article page template based on some value that the user can supply (for example, taxonomy or tag, etc.) that would not require our dev group to write a resolver. The newsroom would like to have more control over this process rather than having to file a ticket to get a developer to get the ticket in a sprint, etc.
| Categories | User Workflow, Page List, New Functionality |
| I need it... | Quarter |
Thanks for the suggestion. We don't have any plans on this front. A static number of subtypes can serve a static number of templates
Sorry - I was reading the post the wrong way - I thought you were asking for more use cases.
I cannot access the link you provided. I don't have access to your staging environment,
I believe my statement above answers your questions about use cases and need to open a ticket for a resolver.
We are considering some optimizations to improve the overall experience around Resolvers in the future. We will consider this idea as we plan that future work, which may address some of the pain points in a manner that is aligned with our product direction.
We are looking for more information on the workflows needing creation of Templates and hence updating Resolvers frequently.
Creating or editing a resolver is not a task for a news producer - they do not even have access to this. So they must submit a ticket to our internal development group to do the task - that development groups has priorities and works in agile sprints the way your development group does.
Thanks for posting this idea. Can you please provide us details on the use-cases and the need to go through the ticket process?
Here is the documentation on Resolvers. Please take a look at the content mapped template section. https://redirector.arcpublishing.com/alc/arc-products/pagebuilder/user-docs/pagebuilder-editor-30-resolvers/