< 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.

About this task

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.

Procedure

  1. Select the Draft state and click Go.
  2. Click Add Policies.
  3. Select Default Policies > Unique Asset Name Policy.
  4. Click Add.
  5. By default, the policy runs on Asset save and Entrance to state. Thus, as soon as any user 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. Optional: Change the name of the policy.
  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. If you instead select Issue warning, the user can still save the asset with a duplicate name.
  10. Click Save. The following informational message is displayed: This policy is currently not used in any exit conditions. Select a transition to configure conditions..
  11. Add conditions to transitions to enforce the result of the policy. To learn more about adding conditions to transitions, see Lesson 4.1: Creating complex lifecycle conditions. If you do not add conditions that are linked to this policy, assets with duplicate names can be saved.
  12. Click Save and Finish to finish editing the master lifecycle.

Results

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