< Previous | Next >

Lesson 3.4: Verifying unique names for assets submitted to the repository

You can add the Unique Asset Name policy to ensure that all assets being submitted having unique names.
This lesson applies the Unique Asset Name policy to a master lifecycle, however, you can apply this policy to any lifecycle type you have permission to edit.
  1. Select the Draft state and click Go.
  2. Click Add Policies.
  3. Select Default Policies > Unique Asset Name Policy.
  4. Click Add.
  5. The default times this runs is on Asset Save and Entrance to State. So as soon as someone puts an asset in the draft state or saves changes to the asset, this policy runs.
  6. Click Configure to add more details on the policy.
  7. Change the name if you want.
  8. Select a search scope of Entire repository to check the community for the same asset name. You can also select Current Community to ensure that all assets within a single community have unique names.
  9. For the On failing the policy option, select Issue error. The submitter is unable to save a duplicate name. If you select Issue warning, the user can still save the asset with a duplicate name.
  10. Click Save. You are given an informational message that This policy is currently not used in any exit conditions. Select a transition to configure conditions. For this policy type, you do not need to add a transition condition.
  11. Click Save and Finish to finish editing the master lifecycle.
Each asset is checked when it is entered into the draft state to ensure that the name is not already used on another asset.

Lesson checkpoint

You learned how to apply and configure the Unique Asset Name policy.
< Previous | Next >

Feedback