Hello,
We would like IBM FileNet Content Platform Engine to allow administrators to associate a Marking Set with an existing property, and not only when the property is initially created.
Today, if a property has already been created without a Marking Set, it is not possible to add a Marking Set to that property afterwards through standard administration. This creates a significant limitation when security requirements evolve after the initial data model has been defined.
Business Need
In real-world enterprise ECM projects, security models are not always fully finalized at the beginning of the implementation. Metadata models are often created first, and security rules are refined later based on business, compliance, or operational requirements.
For example, an existing property may later become relevant for:
- confidentiality classification;
- business unit-based access control;
- legal entity segregation;
- country-specific access rules;
- document sensitivity;
- department-level security;
- regulatory or compliance-driven restrictions.
In such cases, customers may need to apply a Marking Set to a property that already exists and may already be used by document classes, folders, searches, workflows, integrations, or external applications.
Current Limitation
Currently, the association between a property and a Marking Set must be defined at property creation time.
If this decision was not made initially, customers are forced to consider complex and risky workarounds, such as:
- creating a new property with the required Marking Set;
- migrating values from the old property to the new one;
- updating document classes and property templates;
- adapting ICN configurations, searches, workflows, reports, APIs, and integrations;
- managing coexistence or deprecation of the original property;
- performing potentially large-scale data remediation.
This increases project cost, complexity, and operational risk.
Expected Behavior
FileNet should allow administrators to add or associate a Marking Set with an existing property, provided that the property type and configuration are compatible with Marking Set usage.
The enhancement should ideally support:
- adding a Marking Set to an existing property template;
- validating compatibility before applying the change;
- applying the change without requiring creation of a replacement property;
- preserving existing metadata values;
- maintaining consistency across ACCE, APIs, ICN, and Content Platform Engine enforcement;
- providing clear warnings or validation messages if the change has security or data model implications.
Idea / Enhancement Request
We would like IBM FileNet Content Platform Engine to allow administrators to associate a Marking Set with an existing property, and not only when the property is initially created.
Today, if a property has already been created without a Marking Set, it is not possible to add a Marking Set to that property afterwards through standard administration. This creates a significant limitation when security requirements evolve after the initial data model has been defined.
Business Need
In real-world enterprise ECM projects, security models are not always fully finalized at the beginning of the implementation. Metadata models are often created first, and security rules are refined later based on business, compliance, or operational requirements.
For example, an existing property may later become relevant for:
- confidentiality classification;
- business unit-based access control;
- legal entity segregation;
- country-specific access rules;
- document sensitivity;
- department-level security;
- regulatory or compliance-driven restrictions.
In such cases, customers may need to apply a Marking Set to a property that already exists and may already be used by document classes, folders, searches, workflows, integrations, or external applications.
Current Limitation
Currently, the association between a property and a Marking Set must be defined at property creation time.
If this decision was not made initially, customers are forced to consider complex and risky workarounds, such as:
- creating a new property with the required Marking Set;
- migrating values from the old property to the new one;
- updating document classes and property templates;
- adapting ICN configurations, searches, workflows, reports, APIs, and integrations;
- managing coexistence or deprecation of the original property;
- performing potentially large-scale data remediation.
This increases project cost, complexity, and operational risk.
Customer Value
This enhancement would make FileNet security administration more flexible and easier to maintain over time.
It would help customers to:
- adapt security models without redesigning the metadata model;
- reduce costly migration efforts;
- avoid unnecessary duplicate properties;
- simplify long-term governance;
- reduce implementation risk;
- support evolving compliance and regulatory requirements;
- improve maintainability of enterprise ECM solutions.
Proposed Enhancement
Enhance FileNet Content Platform Engine and administration tools so that a Marking Set can be associated with an existing compatible property after its initial creation.
This would provide administrators with a controlled and supported way to evolve metadata-driven security models without requiring disruptive property redesign or data migration.
Thank you
