[ALM Accelerator - BUG]: Flows are not activated after import

[manuelap-msft]

Describe the issue

Hello, we've configured flows to be on in the deployment settings

but they're off after solution import. Have opened the solution.zip file and also the solution meta-data shows the flow status as off there.

Expected Behavior

Flows turn on after import.

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

latest

Steps To Reproduce

No response

Anything else?

No response

[mikefactorial]

Thanks for reporting this @manuelap-msft. Always good to have internal eyes on what we're doing :) @RajeevPentyala any chance you can take a look at this on Monday? If not I'm happy to take it as an action item after our bug bash for the April release.

[manuelap-msft]

Hello,

I did some more testing and hoping that helps with the triage

• Other flows activate fine, so it seems to be specific to the ones highlighted
• The solution has about 90 flows and the once we want to activate are alphabetically at the bottom, so could it be a pagination issue / or not retrieving all flows?
• The flow names contain a special character >, not sure if that could lead to an issue (e.g. comparing > with > if there's encoding in place or so)

[mikefactorial]

This ended up being an encoding issue with ConvertTo-Json in powershell that was creating unicode escaped values for the > character in the name of the deploymentSettings.json. Solution was to Unencode the json before storing it. microsoft/coe-alm-accelerator-templates#292