AEMC Deployment Pipeline Change Request not using the configured template

[Mikael Karlsson]

We have AEMC configured since a week or so and we are ironing out a couple small issues.

When approval for production and change request is created, the chosen Standard Change template i've chosen in the configuration property is not used and instead a default standard empty one is used.

I would like to pre-fill the service, offering, assignment group etc but since it's not picking the template i'm not able to.

The template i created was for this automated purpose only and hence i left it as "not visible in the UI", could that be a reason why it's not used?

How can i troubleshoot the mechanism which creates the change, perhaps there is some kind of policy issue or similar preventing it and causing the fall back to blank.

I would also love to know if there are any hidden placeholder variables for example so that we could build the descriptions and insert <appName> <version> <requestor> etc at our own liking.

[Mikael Karlsson · Accepted solution]

My issue is resolved, now it's able to use the template.

The documentation was actually incorrect:
https://docs.servicenow.com/bundle/xanadu-application-development/page/build/pipelines-and-deploymen...