Resource Additional Fields
Hello,
in our environment we found conflicts for the Resource Name field, which must be unique even if related to resources with different Resource Types.
The anomaly arises from the need for multiple Password Administrators to register credentials on the same resource, without however being legible by competing accounts: we have not identified alternatives other than to define different resources, traceable to the same object through additional fields. Is it possible to make an additional field mandatory?
What is the best practice for this series?
thanks
in our environment we found conflicts for the Resource Name field, which must be unique even if related to resources with different Resource Types.
The anomaly arises from the need for multiple Password Administrators to register credentials on the same resource, without however being legible by competing accounts: we have not identified alternatives other than to define different resources, traceable to the same object through additional fields. Is it possible to make an additional field mandatory?
What is the best practice for this series?
thanks