vRA 7.2 - Setting Properties coming from a Property Group to non-overwriteable

[Czernobog]

I am using a basic group of properties, which I have defined in the Property Dictionary and grouped in a Property Group, on multiple blueprints. I want those properties to be non-overrideable, that is, I do not want users to be able to edit the properties when requesting the catalog item.

When I add a single property from the Property Disctionary to a machine blueprint, I can remove the selection from "Overrideable".

When adding a group of properties, I cannot do this, the "Overrideable" column is not there.

What would be a way to to add a group of custom properties to multiple machine (vSphere VM component) blueprints, without much hassle?

I've tried it with vRO, but there is no "machine blueprint" object. Both the "Create / update property to machine blueprint" and "Create / update property to blueprint" workflows use the same action

"addUpdatePropertyFromBlueprint" which refers to a composite, not component blueprint.

[daphnissov]

Not sure that I fully understand what you're trying to do. When you create a property group, you define on the individual properties it contains things like overrideability and showing in request. If you don't want users to override it, just attach the property group to the blueprint (not the machine element on the canvas) and make sure they don't show in the request form. If the properties don't show, there's nothing to override. If this isn't what you want, could you explain a little further?

[Czernobog]

As an example, I define the property, with an empty value:

I then group & assign a value to this property in a Property Group:

As you can see, there is no "override" option you can select.

I understand there should be a column to the right, as there was one previousy in vRA 6, like described here, but it seems to be missing:

Create a Property Group

I know I problably made a really stupid error somewhere, but I do not know what the source of the issue is:| Tried it with FF54 and IE11.

[daphnissov]

I see what you mean. Yes, an "Overrideable" column isn't present for properties defined in a group although it defaults to "Yes". Still, though, if you aren't showing any of those custom properties on the request form, a user has no ability to override them in the first place.

[Czernobog]

They are not shown in the form, but can still be overridden in the Properties tab, that's the issue.

[daphnissov]

Only the users who are business group managers see the Properties tab in the request form. Users assigned either the Support or User role for a given business group do not. But yes, your BG managers could possibly override those properties. Is that a big concern?

[Czernobog]

It is a concern, I do not want users to edit properties on blueprints defined by me.

I have reached out to GSS about this and got told, that the feature was removed, even though it is still documented, the reason was not named though. I just hope this gets reverted since there even is no way to automate the setting.