-
Type:
Epic
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Studio Modeler
-
Tags:
Context:
Our multi-layer approach allows us to override and edit dependent features
It does not, however, allow to fully disable them,
The current workaround of creating a 'non-visible' override is not ideal
The platform team has been able to deliver a disabling mechanism https://jira.nuxeo.com/browse/NXP-30586
Platform changes to:
- DocType
- Event Handler
- OperationType (chain + script)
- LifeCycle
- Structured Template
To Do
In terms, of Studio we should be able to
Disable a feature in a dependency (in a similar way and with similar iconography as we do in a local project)
Is this doable?
To which features can we apply this? Uniquely this list?
- DocType
- Event Handler
- OperationType (chain + script)
- LifeCycle
- Structured Template
Do we treat 'Global' features? Resources?
Error Scenarios
If I disable a feature that is used else where, such as an automation, will I et an error message?
If not, would it be possible?
