SCOPE attribute in HTTP connected system is not exported to Customization File.

RE: SCOPE attribute in HTTP connected system is not exported to Customization File.

Harshit Bumb (Appyzie) — Tue, 01 Feb 2022 05:27:06 GMT

Hi there,

I don't think there is any direct way of doing it. This can just be a part of your post-deployment steps that you need to follow like a checklist to ensure everything is on track after deployment.

RE: SCOPE attribute in HTTP connected system is not exported to Customization File.

Acacio Barrado — Tue, 01 Feb 2022 01:17:25 GMT

I see your point, unfortunately the SCOPE parameter does not even accept an constant what could be handy in this case.

Hope someone else come up with an idea.

Regards,

Acacio B

RE: SCOPE attribute in HTTP connected system is not exported to Customization File.

Mahi — Tue, 01 Feb 2022 00:56:36 GMT

Thank you Acacio B.

Yes I've checked that link and it is expected behavior.

But, my challenge is to avoid that manual step in Production. There is always risk with these manual steps, especially when someone forget to update that attribute. Then we will have production issues due to this.

So I'm looking for any suggestions in maintaining this attribute automatically without manual step ?

RE: SCOPE attribute in HTTP connected system is not exported to Customization File.

Acacio Barrado — Tue, 01 Feb 2022 00:46:57 GMT

Hi ,

This is the expected behavior according to the documentation:

https://docs.appian.com/suite/help/21.4/Oauth_connected_system.html

So I would assume that you need to manually change the SCOPE on each environment. Perhaps someone else will have a better idea how to maintain this values in different environments.

Regards,

Acacio B.