OOTB to disable creating CN on an object which is present in the resulting objects of another CN

[OP_11714882]

Hello, is there any OOTB functionality to disable creating a Change Notice on a version of an object which is already present in the Resulting Objects of another Change Notice?
Because it can be quite a common business requirement that if there is an ongoing change on an object, I don't want to add another change on it before completing one change.

Regards,

Om Panchdhane

[Fadel]

when an object is under change you have a flag for it : 

if you have an issue with concurent changes, you may be interested in About Redline 

[OP_11714882]

But we can still create another change notice on it right? Is there any configuration to disable the CN creation?

[Fadel]

Not OOTB , I can only think of customizing the the CN/CT workflow to move the affected objects to Lifecycle state with a set state robot to a state   where there is no change transition, defined , this should hide the action .

[OP_11714882]

Okay. Thanks!

[RandyJones]

---

@OP_11714882 wrote:

But we can still create another change notice on it right? Is there any configuration to disable the CN creation?

---

FelcoSolutions has their ObjectValidator app. It is intended for issues like this:

https://www.felcosolutions.com/objectvalidator

[OP_11714882]

Thank You!