Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.

.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

The Asset review process has to undergo three steps:

  1. Compliance Review.
  2. Processing Review.
  3. Quality Review.

I. Compliance Review

This is the first step of Asset review. An Asset comes under Compliance Review when the user who uploaded the Asset sends the Asset for review and the configuration for Compliance Review is anything other than 0.

Icon

The number of Accepts and Rejects for any review varies from 0 to 15.

Icon

When the Number of people needed to accept an asset to approve it for Compliance Review Configuration is kept as 0: The Asset will skip this review step and move to the next review step depending on the Project's configuration, or it will be assigned the Completed status if no accept votes are required for the remaining review steps.

When the Number of people needed to accept an asset to approve it for Compliance Review Configuration is kept as 1: The Asset will go to the Compliance state when sent for review from the Draft state. Any user having the Compliance Review permission can review the Asset and either accept or reject it.

When the Number of people needed to accept an asset to approve it for Compliance Review Configuration is kept as anything greater than 1 (i.e 2-15): The Asset will retain the Compliance state until it gets the required number of Accept votes, as per the Project's configuration, to move to the next state as per the Project's configuration.

Icon

If an Asset is accepted or modified, then it is passed for the next review step as per the Project's configuration, or it will be assigned the Completed status if no accept votes are required for the remaining review steps. If rejected, it will be assigned the Rejected state with HIPAA compliance image. This image will be returned to the uploader.

II. Processing Review

This is the second step of Asset review. An Asset comes under Processing Review in three cases:

a. If the Asset has been accepted in the Compliance Review when the configuration for processing is anything other than 0.

b. If the configuration for Compliance Review for Accept is 0 and for Processing Review is a value other than 0.

c. If the Manager has changed the state of the Asset to Processing.

Icon

When the Number of people needed to accept an asset to approve it for Processing Review Configuration is kept as 0: The Asset will skip this review step and move to the Quality Review if it is required as per the Project's configuration, or it will be assigned the Completed status if no accept votes are required for the Quality Review.

When the Number of people needed to accept an asset to approve it for Processing Review Configuration is kept as 1: The Asset will be able to attain the Processing state from its previous state. Any user having the Processing Review permission can review the Asset and either accept or reject it.

When the Number of people needed to accept an asset to approve it for Processing Review Configuration is kept as anything greater than 1 (i.e 2-15): The Asset will retain the Processing state until it gets the required number of votes, as per the Project's configuration, to move to the next state as per the Project's configuration.

Icon

If the Asset is accepted or modified, the Asset is passed for the Quality Review as per the Project's configuration, or it will be assigned the Completed status if no accept votes are required for the Quality Review. If rejected, it will be in Rejected state and will be returned to the uploader for further modifications.

III. Quality Review

This is the third and final step of review. An Asset comes under Quality Review in four cases:

a. If the Asset has been accepted in the Processing Review when the configuration for Quality is anything other than 0.

b. If the configuration for Processing Review for accepts is 0 and the value for Accept for Quality is a value other than 0.

c. If the configuration for Compliance Review and Processing Review for accepts is 0.

d. If the Manager has changed the state of the Asset to Quality.

Icon

When the Number of people needed to accept an asset to approve it for Quality Review Configuration is kept as 0: The Asset will skip this review process and move to Completed state.

When the Number of people needed to accept an asset to approve it for Quality Review Configuration is kept as 1: The Asset will be able to attain the Quality state from its previous state. Any user having the quality review permission can review the Asset and either accept or reject the Asset.

When the Number of people needed to accept an asset to approve it for Quality Review Configuration is kept as anything greater than 1 (i.e 2-15): The Asset retain the Quality state until it gets the required number of votes, as per the Project's configuration, to move to the Completed state.

Icon
If the Asset is accepted or modified, then it is passed to Completed State and, if rejected, it will be in Rejected state and will be returned to the uploader for further modifications.
  • No labels