When several improvements are carried out in parallel on a model, what are the best practices to prevent stickiness between each other?
F
Fathia Jama
started a topic
over 2 years ago
When several improvements are carried out in parallel on a model, what are the best practices to prevent stickiness between each other ? Is there a solution to allow the delivery of an improvement (or a fix), even when others are still under development or test ?
Best Answer
F
Fathia Jama
said
over 2 years ago
Hi Nicolas,
There's nothing to stop two users from working on a model at the same time. However, they should coordinate their activities and be aware of what each other is doing or has done. They should communicate and be well organized. Outside of communicating the changes, there is currently not a built in solution. However, there is an enhancement request for deploying parts of the model at different times. The internal reference id is MDM-8863
1 Comment
F
Fathia Jama
said
over 2 years ago
Answer
Hi Nicolas,
There's nothing to stop two users from working on a model at the same time. However, they should coordinate their activities and be aware of what each other is doing or has done. They should communicate and be well organized. Outside of communicating the changes, there is currently not a built in solution. However, there is an enhancement request for deploying parts of the model at different times. The internal reference id is MDM-8863
Fathia Jama
When several improvements are carried out in parallel on a model, what are the best practices to prevent stickiness between each other ? Is there a solution to allow the delivery of an improvement (or a fix), even when others are still under development or test ?
Hi Nicolas,
There's nothing to stop two users from working on a model at the same time.
However, they should coordinate their activities and be aware of what each other is doing or has done. They should communicate and be well organized. Outside of communicating the changes, there is currently not a built in solution. However, there is an enhancement request for deploying parts of the model at different times. The internal reference id is MDM-8863
Fathia Jama
Hi Nicolas,
There's nothing to stop two users from working on a model at the same time.
However, they should coordinate their activities and be aware of what each other is doing or has done. They should communicate and be well organized. Outside of communicating the changes, there is currently not a built in solution. However, there is an enhancement request for deploying parts of the model at different times. The internal reference id is MDM-8863
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 276 topics