How to do both automatic Common Control updates (Reliant Entity Type) AND auto control generation?

[Paulkontheriver]

Is there a way of doing both automatic Common Control updates (Reliant Entity Type) AND automatic control generation?

When creating Common Controls, why don’t I see the desired “Reliant Entity Type” when adding using “Reliant Entity Type”?

Do I have to remove the control objective from the Entity Type to add “Reliant Entities” via the “add Reliant Entity Type” function?

• When the Control Objective is left associated with the Entity Type so controls can be generated automatically, the Common Control “Reliant Entity Type” add function does not show the desired “Entity type” and is not available.
  • When the Control Objective is removed from the Entity Type, the Common Control “Reliant Entity Type” add function works.

• The “Entity Type” add function allows for automatic updates of all Common Controls associated with a new Entity being associated with the Entity Type.

• Associating a Control Objective allows for automatic control generation when adding a new Entity is associated with an Entity Type

• Is there a way of doing both automatic Common Control updates (Reliant Entity Type) AND automatic control generation?

Thanks for any help on this issue,

Paul 

[Vinod Laxmeshwa]

@Paulkontheriver : 

I think this is expected behaviour  and may not be a bug. It's a deliberate uniqueness rule in the platform.

Why the entity type doesn't appear in the picker?

- When a Control Objective is linked to an Entity Type, item generation has already created one control per entity. Adding that same Entity Type as a Reliant Entity Type would create duplicates and so the picker filters it out.

Remove the Control Objective from the Entity Type → no auto-generated controls → no conflict → the Entity Type becomes selectable.

Item generation and Common Controls are alternatives, not layers:

• Item generation : one control per entity, each tested separately.
• Common Control + Reliant Entity Type : one shared control, results inherited by all reliant entities.

How to get both behaviours in your model?

Just a thought from what i understood,

try to split by Control Objective:

• CO A ↔ Entity Type (e.g: Servers) → item generation, one control per server.
• CO B → Common Control with Entity Type (e.g: Servers) as Reliant Entity Type → one shared control, auto-updates as servers are added.

Both behaviours run side-by-side on the same Policy and Entity Type just expressed through different Control Objectives. If both are needed for the same requirement, map the two COs to the same citation so they roll up together.

I hope this helps.