This article describes the overall release journey of draft assets. The steps of this journey have each been described in their own articles:
Conditions to release
Asset info
Usage rights
Type of update
Schedule release date
Cohero's release journey follows a sequence of steps, visualized below. We'll explain each step in this article.
Conditions to release (Barrier to proceed)
Before a user can actually begin the release journey, Cohero checks whether all the configured criteria are met - for the release journey to commence. If any of these criteria are not met, the user is returned to the canvas, to complete them first:A completed approval workflow
An expiry date
Asset info (Quality gate)
The second step is a quality gate, that screens the completeness of the asset info. Any field left empty will be listed - encouraging the user to return to the asset canvas, to complete the remaining asset info, boosting the overall asset quality. As this is a quality gate, it is not a barrier to proceed. The user can choose to discard the warning, and proceed to the next step.
Usage rights (New assets only)
The next step, in releasing original, new assets - is to confirm the intended usage rights for this asset. If the user already defined them as part of the asset info, that selected answer will be prefilled in this step. The user confirms the desired usage right here.
Type of update (New versions only)
The next step, in releasing new versions, is to classify the significance of the update, compared to the predecessor. More on choosing the right type of update on the dedicated article about that.
Schedule release date
The last step to release the asset, is the step in which the time of the release can be chosen. At this step, the user can choose a future step - which will schedule the asset to be released on that date. He can also discard the date selection, and proceed to release the asset immediately.