Hi James, thanks for your answer. I agree with you and Alain that moving to ADS or DecisionFirst would be the right solution, but not feasible at this time.
The customer has a lot (more than 300) models developed and in production. There is no time to stop and think, They need to continue operating their large legacy and attend new business requirements at the same time. They cannot afford Installing and migrating to a new product, and less if K8S is a requirement.
They started some year ago, following IBM recommendations by that time, but now IBM has new product strategies in place and they're not aligned.
------------------------------
Eduardo Izquierdo Lázaro
Automation Architect
DECIDE
MADRID
+34609893677
------------------------------
Original Message:
Sent: Mon August 23, 2021 01:10 AM
From: James Taylor
Subject: Missing functionality in DC for decision models.
For decision modeling there is another approach. We have been working with the ODM and ADS teams to provide a DMN decision modeling capability. DecisionsFirst Modeler supports decision models, the Decision Model and Notation standard, branching, versioning and synchronization with ODM decision tables. We are actively engaged with the ADS team to also allow models to be synchronized with ADS. Contact me if you would like details.
You can also find information on DecisionsFirst Modeler in Seismic and it is the ODM team's officially supported solution for decision modeling with ODM/DMN. Feel free to reach out to the ODM/ADS product management team for their input.
James
------------------------------
James Taylor
Original Message:
Sent: Fri August 20, 2021 08:23 AM
From: Eduardo Izquierdo Lázaro
Subject: Missing functionality in DC for decision models.
A legacy customer of Decision Composer was using extensively the functionality of duplicate and rename decision models. They had template projects they used as starting point to create new decision services without having to define the business data and decision model from scratch. As this product has been discontinued, they are moving their projects to ODM Decision Center, but this functionality is not available.
What is the best approach to have equivalent functionality in DC? preferable without custom extensions.
I was thinking in implementing the template project as a base project and then create branches from it that can be deployed independently. Don't know if there is a scalability issue for having a decision model with many branches that are never merged.
Or maybe there is a plan to add this functionality to DC, that actually makes a lot of sense specially for decision models that are targeted for business users and cannot be synchronized with Rule Designer.
------------------------------
Eduardo Izquierdo Lázaro
Automation Architect
DECIDE
MADRID
+34609893677
------------------------------