Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Needs more information
Created by Guest
Created on Aug 28, 2024

Rule Deployment to simultaneously show in 2 RES Instances in different datacenters

We are needing to know or determine if this capability is a new feature and will need evaluation or if this already exists with some type of implementation. Client has the following set up regarding the option of having 2 data centers (1 in DFW, and other in SA) connected to one SQL Server database in their ODM environment on Kubernetes. Client mentions that they deploy rules/rulesets from DC into RES. Depending on which RES data center they deploy to, the other datacenter is able to pick up the changes in their RES log, but its delayed. Client is wanting to obtain an almost 1 to 1 sync in which the logs show the deployment at the same times on both datacenter RES consoles. Client is only able to get the respective datacenter RES console to pick up the latest changes if they restart their kPods.

Idea priority High
  • Admin
    Antony Viaud
    Reply
    |
    Sep 2, 2024

    Hello,

    There is currently no plan to modify or extend the way ODM deployments are managed.A ruleApp (with 1 or more rulesets) can be directly deployed from DC to one or more RES servers. But there is no guarantee that there will be an "almost 1-1 sync" on the deployment times shown in the 2 RES Console. It should be very close though.

    I'm not sure I understand some aspects of the description:

    • "...having 2 data centers (1 in DFW, and other in SA) connected to one SQL Server database in their ODM environment on Kubernetes." Do you mean that there is only one DB, with some replication across the 2 data centers ?

    • "Client is only able to get the respective datacenter RES console to pick up the latest changes if they restart their kPods." Can you clarify the issue / limitation ?

    Thank you,