This article includes information about the lifecycle of an Asset, and how to set asset states to reflect that lifecycle.
What are the Asset States
- In Development: Every asset's initial state. Asset editing is allowed.
- For software assets, install scripts can be edited and media file can be uploaded. See this article for information about updating software assets.
- For system assets, you can update the operating system, the system specifications, and the software asset list.
- For deployment assets, you can update the custom properties.
- Certified: The asset is locked down and cannot be updated.
- This state is designed for your configuration and process management. For example, your project can make a rule that "only Certified assets can go to production".
- Before an Asset can be set to Certified, it must have text under the License and Help tabs and must identify a POC and contact information.
- Only users with "Can share assets outside of the project." permission can set certified.
- Deprecated: The asset should no longer be sued but will not break existing users.
- Existing systems, scenarios or deployments with Deprecated assets will launch but cannot be added to new ones.
- This is a required step before the "Retired" state.
- Asset owners using a "Deprecated" assets will be notified at the time of the change.
- Deprecated assets will not appear by default in the UI view, unless the Include Inactive checkbox is selected. After selecting Include Inactive, deprecated assets appear but are greyed out.
Setting Asset States
- Click on an Asset from the Asset Library
- If you have appropriate permissions, you will see a Settings Gear next to the current asset state
- Click on the Settings Gear
- Only states that can be set appear in the list:
- To use Certified, you must enter text under the HELP and LICENSE tabs if available.
- Select the desired Asset State, as shown in the image