Enable the publish or activation of a single action from a lower environment into Production, without requiring direct edits in the Production instance

To enable the publish or activation of a single action from a lower environment (e.g., Dev or Staging) into Production, without requiring direct edits in the Production instance. This would allow teams to isolate environments and maintain compliance with client security protocols and change management processes.

The goal is to support a workflow where:

A team can create or modify an action in a non-production environment.
That action can then be promoted individually to Production via API or controlled interface.
The Production environment remains isolated, with no need for direct access or edits.
The team responsible for emergency messages can approve activation without modifying the action itself.

This feature is essential for implementing Emergency Messages, allowing rapid deployment of critical updates while respecting GMUD (Managed Change Process) and security constraints. It also supports the architectural need for coexistence of Assistants and Agents, enabling more granular control over deployments.

Idea priority

High

Post comment

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.

Please enter your email address

RELATED IDEAS

Enable the publish or activation of a single action from a lower environment into Production, without requiring direct edits in the Production instance