I have requirement to call service now API before every manual deployment. Appian support team should not be able to deploy package in Production if change ticket from service now is not approved or not in start time and end time window. I have achieved the integration by calling service now API but I am not able to restrict the "DEPLOY" button on Appian Production screen based on the check. Is there any way we can restrict the deployment here?
Discussion posts and replies are publicly visible
I think this is not supported.
Who is calling this API? Are you aware that you can configure the target environment so that each deployment must be approved? Why not make the same group that calls the API also approve the deployments?
I have created an application where support team will enter the change ticket number and on pressing the submit button, invokes a process model to create user task, where API is called to get the details of change ticket. But this is independent of deployment interface of appian. Wanted to connect these two in some way so that deployment can not be done if my application returns false.
And can you throw some light on configuring target environment for deployment approval please? In any case the deployment should be integrated with service now to check change ticket timings and approval status.
I understand.
This becomes difficult as two applications fight for control. I think you should either only use Appian, or only user an external tool.
https://docs.appian.com/suite/help/23.4/Appian_Administration_Console.html#deployment-settings
To add deployment approval for your deployment process, select the Require Review option and specify a reviewer group. In addition to system and application administrators, this group can approve or reject deployments.