Review Task Success/Failure Capture

Hi,

I am using Interwoven workflow modeller 1.0.0.1 in which I am using a Review Task. Review Type is 'Serial' and Return on first Reject is set to 'false' and I need to capture the status of Success/Failure of each Review task in a form which is unique for different reviewers(the logic to update the DCR form is in a External task just after Review Task)
Ex: Reviewer1 --> DCR form Reviewer1-->need to capture the success/failure and continue with next review
Reviewer2 --> DCR form Reviewer2-->need to capture the success/failure and continue with next review and so on..

can anyone please suggest how I can implement this logic using wfm.
Thanks in advance.

Find more posts tagged with

Comments

Faizi

Hi,

I am using Interwoven workflow modeller 1.0.0.1 in which I am using a Review Task. Review Type is 'Serial' and Return on first Reject is set to 'false' and I need to capture the status of Success/Failure of each Review task in a form which is unique for different reviewers(the logic to update the DCR form is in a External task just after Review Task)
Ex: Reviewer1 --> DCR form Reviewer1-->need to capture the success/failure and continue with next review
Reviewer2 --> DCR form Reviewer2-->need to capture the success/failure and continue with next review and so on..

can anyone please suggest how I can implement this logic using wfm.
Thanks in advance.

Would you elaborate your requirement in detail? So that gives the complete scenario. What do you mean by Success/Failure of each Review task in a form which is unique for different reviewers(the logic to update the DCR form is in a External task just after Review Task)[color=Black].[/color]

gir

To ellaborate, There is a Review Task after which a reviewer approve the review or reject a process(which I mentioned as Success/Failure )
The Review Task is Serial and Return on first Reject is set to 'false'.

Consider this case where there are 3 reviewers.
All the reviewers in Review Task can approve or reject a process and I want to run an External Task after each review process to capture the event of each approve/reject done by reviewers and do some manipulation based on each approve/reject.

But in the current senario the External task runs only after the completion of the final review in this case after 3rd review and due to this issue I am only able to capture the last event.

can you help. let me know if there are any further info you require.

Faizi

To ellaborate, There is a Review Task after which a reviewer approve the review or reject a process(which I mentioned as Success/Failure )
The Review Task is Serial and Return on first Reject is set to 'false'.

Consider this case where there are 3 reviewers.
All the reviewers in Review Task can approve or reject a process and I want to run an External Task after each review process to capture the event of each approve/reject done by reviewers and do some manipulation based on each approve/reject.

But in the current senario the External task runs only after the completion of the final review in this case after 3rd review and due to this issue I am only able to capture the last event.

can you help. let me know if there are any further info you require.

Now it is clear. As per your requirement in current scenario it is not possible.
Calling an External Task between the process of Review Task does not make sense. What do you want to exactly manipulate during review task?

vpatel

Am I understanding it correct: that after each review, you want an external task? If that is it then that should be doable. Or there is more than that?

Migrateduser

This makes no sense. If you want the workflow to flow from:

Review1->ExtTask->Review2->ExtTask->Review3->ExtTask

Then just link it together that way. What's the problem?

gir

Thats the problem here. It will not happen in ReviewTask->Ext task->Review task->Ext Task...
As there are 3 reviews in Review Task when all the 3 Reviews are completed it goes to Ext task, but I need a one on one mapping so as to do some manipulation in external task.
I told you that Return on first reject is 'false' and Review Type is 'Serial' in Review Task.
I have done some search on it in manuals, but I need a logic for this real senario.

Adam Stoller

Thats the problem here. It will not happen in ReviewTask->Ext task->Review task->Ext Task...
As there are 3 reviews in Review Task when all the 3 Reviews are completed it goes to Ext task, but I need a one on one mapping so as to do some manipulation in external task.
I told you that Return on first reject is 'false' and Review Type is 'Serial' in Review Task.
I have done some search on it in manuals, but I need a logic for this real senario.

Skip the Review task and do it the old-fashioned way:
External-or-Email Task => User-or-Group Task => Success and Failure Transitions ... Repeat 3 times.

gir

Interwoven provides Datasource variables,Configurable variables,Script variables etc..In the Review Task we were using a Datasource variable using this would make the Review task reviewer list dynamic which had an advantage.
I am just frustrated that I put on so much effort in analysing and implementing things and finally when nothing works then I have to come to a very ordinary logic, If I had to implement such a logic then why Interwoven is providing such a tool which does nothing but wastes time.

Thanks for all your reply/suggestion guys, I dont want to waste any of your time on this issue.

Dave Smith, I am sorry to say this but when a user posts on something like this then atleast please get to know what he/she is asking for.. No user will come to this forum without reading manuals if that it is the case then forum wouldn't have existed. If you found out something in manual which you found helpful then please suggest.

Adam Stoller

...Dave Smith, I am sorry to say this but when a user posts on something like this then atleast please get to know what he/she is asking for.. No user will come to this forum without reading manuals if that it is the case then forum wouldn't have existed. If you found out something in manual which you found helpful then please suggest.

In Dave's defense (not that he needs it in this case) - there are quite a few people who post in the forums who seem to have never had training and never looked at the manuals - and it is usually from the phrasing of the post that one can detect that the person asking has in fact done some advance work before posting.

In this particular case - one might assume that you could do what you wanted, but Interwoven designed the Review Task based on their concept of what it should do. If you want to do more - you basically run into the problem you did. Your model and their model don't align with respect to the OOTB "packaged" feature - so you need to decompose and implent another way.

Personally, I still prefer WFT because there are fewer "black boxes" involved - but that's me.

gir

Ya I understand.. I think I am coming up with the idea to capture he event dynamically.. will keep you guys posted.

gir

Hi Guys,

Finally came up with a solution..
If we are using wfm ReviewTask and if the reviewers are more than one,
Review Type 'Serial', Return on First reject 'false' then an External Task gets created internally to validate the Review task whether to get into Success/Failure transtition state at the end of review.

The External Task name would be by default "EndReviewCycle-(Review Task name)" you can do GetTaskByName to get that task object then get the task ID, once you get the task ID you can get the task command which will have the Review Task's embedded in the code as below
(domain)/iw-cc/urlexternaltask?reviewtasks=ReviewTask-1,ReviewTask-2&acceptTransition=success&rejectTransition=failure
by this you can get the No. of Reviewers(if you want to keep the reviewer list dynamic).
then on you can use 'iwgetwfob' to capture the transition states for each Reviewer task

Do a External Task(apart from the External task created by wfm itself) after the Review task to Capture Accept/Reject events of each reviewers.

Thanks

Migrateduser

Dave Smith, I am sorry to say this but when a user posts on something like this then atleast please get to know what he/she is asking for.. No user will come to this forum without reading manuals if that it is the case then forum wouldn't have existed. If you found out something in manual which you found helpful then please suggest.

Good idea to come into a forum and insult the people who are trying to help you. I would explain what a signature is in a profile, but why waste my time?

gir

This has nothing to insult you or anyone in the forum.
If you feel that I have hurt you in any case then I am Sorry I Apologize.
This Forum helps a lot of guys who are keen to work in Interwoven.
Thanks to people like you who support and help us, I had only given my feedback looking at the signature.
I would be very glad if you consider my apologies.

Thanks