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.

[WORKFLOW-COWBOY]

Hi @Mikael Karlsson, 

Can you confirm you have a value set for both properties? 

sn_deploy_pipeline.change_management.default.model

sn_deploy_pipeline.change_management.default.template

Regarding the descriptions, can you specify which fields you want to dynamically update? 

(Ex. "sn_deploy_pipeline_deployment_request.short_description") 

[Mikael Karlsson]

Hi @WORKFLOW-COWBOY , yup the model is configured as Standard.
You don't have the template configured in your screenshot and you likely have the Normal change model, give it a go if you wish and see if it's honored.

The question regarding the placeholder variables is if we would be possible to configure how for example the short description of the change will look, the default one looks like this for my example app:
Deployment of Managed Resource Objects [2.0.0]

[Mikael Karlsson]

I've found the SubFlow which is responsible for this process: "Integrate Change Management for deployment pipelines".

It calls action "Create Change Request for Deployment" and there are no errors, the lookup of the template sysid gets done correctly but i get the feeling that the field value templating part isn't applied.

[Mikael Karlsson]

I think i'm onto something now when i looked at one of the scripts, it was looking up the provided Change Template in the sys_template table and the sys-id was not found there. If i open the Standard Change Template and view the XML, there is a reference there to the sys_template counterpart which is the one which seems to be needed here.