Is there an actual way in RAM to fully prevent assets with duplicate names?
![]()
I know the Unique Asset Name workflow policy can be used to prevent state transitions of assets that have duplicate names. However, users can still:
1. create an asset with a duplicate name 2. change the name, perform the state tranisiton, and then change the name back again to the duplicate name I know number 1 is a product limitation, but number 2 seems strange. There doesn't seem to be any way to enforce restriction when an asset is simply modified (as opposed to a state change). Am I missing something? |
One answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.