Approval mechanism for Change Process

ankitbeohar

In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:

Use Case: - There is no approval mechanism over changes that would be promoted to production environment.

Problem: - Unintentionally there may be wrong deployment to prod environment which will lead to major prod outage.

Workaround: - Manual approval process

How often is this impacting your users?

Very often

Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)

All

What would your ideal solution be? How would it add value to your current experience?

There should be a way when anyone raise code change from non-prod to upper env.

Please include any images to help illustrate your experience.

david.savarin

there should be a deployment admin role / rights, separate from model builders / wsa roles rights that can execute the deployment / sync.

Ideally a fully customizable source code / ci / cd integration would be great, but basically at least a 2 steps workflow with submit / approve deployments