When copying default virtual system, multivalued attribute 'rights' is not created as multivalued in its form definition
When you create a default virtual system, one multivalued attribute 'rights' is created. When you then make a copy of the system, the attribute is created as multivalued in the system scheme but it is not created in the system form definition at all (single valued attributes are created, though). If you then go and change the system (maybe name, maybe state) and save it, the attribute is created but not as multivalued.
This can potentially lead to an error when this attribute is used. If you have two roles, each connects to this copy of the virtual system and each fills different values into it, you will get a server error when you try to accept the request.
#2 Updated by Vít Švanda 8 months ago
- Target version set to 10.6.0
The system duplication operation provides a copy of all configurations from the system in the ACC module only.
The problem is that the "rights" attribute is attached to the VsAccount object and is part of the VS module. This is why this attribute is not duplicated.
The solution is to implement system duplication through multiple modules (ACC and VS).
This is a new feature for 2MD.
#8 Updated by Tomáš Doischer 3 months ago
This is also true for system export and import. If you have a virtual system with a multivalued attribute and try to export it, after importing it again the form definition does not have this attribute set to multivalued (it is still multivalued in the scheme).