- Article Type: General
- Product: Verde
- Product Version: 2
The first task that is launched for the Renewal workflow depends on the decisions that were made in the Review workflow. In case there is more than one e-product related to the acquisition record, there are three possible scenarios:
1- All e-products were approved as part of the Review workflow. In this case, the task that will be launched for the Renewal workflow is <RN-12>: "Decide if sufficient concurrent users have been purchased on the acquisitions record".
2- All e-products were rejected as part of the Review workflow. In this case, the task that will be launched for the Renewal workflow is <RN-3>: "Cancel the acquisitions record".
3- Some of the e-products were approved, and some were rejected. In this case, the task that will be launched for the Renewal workflow is <RN-21>: "Cancel the existing acquisitions record".
The reason the workflow was designed this way is that it was written before the 'Unlink' function was developed. The logic was that if there's an acquisition record that is related to multiple e-products and then one of them is canceled/rejected, the acquisition should also be canceled, and a new acquisition should be created to reflect the change (After all, the conditions of this subscription were changed). However, since the development of the unlink function, it wouldn't be desirable to cancel the entire acquisition record and create it from scratch, when 'unlink' can work instead.
In such cases of subscriptions with some approved and some rejected e-products, take the following steps:
1) Stop the workflows
2) Change the status of the acquisition record to some temporary status
3) Unlink the rejected e-products
4) Change the status of the acquisition record back to 'Review'
5) Continue with the workflows as usual. This time, all e-products will be approved, so the problem will be avoided
- Article last edited: 10/8/2013