nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Callback without Task in workflow

kaalraa

Hi there,

I have a workflow in which there is a reviewer task for manager to approve. Earlier he has the option to either Approve/Reject which in turn calls a callback to next success / reject task. Now the client has asked a new requirement to put a screen in between these 2 tasks asking the reason of rejection if rejected.

I have called the cgi using location.href onClick of Reject button of CGI file. its opens up a rejection screen and asks the reason. On this rejection form when user clicks submit... it uses that comment and the reviewer task object for callback. The callback is running successfully but my problem is it ADDS an extra comment in the JobComments section of workflow using user as IWUI. There is no issue on comment as it is needed to view as why the content was rejected but the main problem is WHO HAS rejected as the reviewer task is a group task.

Does any one know... how to change the owner of the rejection comment which would also reflect in the Job Comments section. All suggestions are welcome.

- ak's

Find more posts tagged with

Comments

JonathonG

I think if you sent your new location through the cgi wrapper, your second CGI would run as the same user as the first CGI and the comment would get logged properly.

Jonathon
Interwoven Developer
Allstate, Inc.

Adam Stoller

Alternatively - two back-to-back cgitask's using TeamSite::CGI_lite::iwcallback (or the URI equivalent? - not TeamSite::WFtask::CallBack) where the second cgitask is owned by the same user as the first cgitask and has the immediate="t" attribute set.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

kaalraa

Thanks Adam for your reply... but the issue i have is my first CGI file runs thru workflow as a CGI Task... whereas the second CGI file is called implicitly using http protocol with CGI object and task id as parameters.

From second CGI file using CGI object .. it uses iwcallback to move on to the next task of the first CGI task. This iwcallback is giving iwui as owner of the comments entered as rejection comments on second CGI file. My question was is there any way to change the owner of the comments given in second CGI file??

I hope you understand the query. Also i am using TS6.1 with SP 2.

- ak's

Adam Stoller

The word "Alternatively" was meant to suggest that a different method might offer better results - though I'm not sure where I got the idea that the review task was a cgitask [is it? - if so - then my alternative suggestion stands as-is]

If you're talking about a usertask or grouptask in which the owner of said task has the option to Approve or Reject - and you want to make sure that the Rejection is accompanied with a description of the reason - then you might be able to fall back on "user training" - in which the users should be trained to fill in the transition comment box *before* transitioning the task (I think there's a FR somewhere about being able to make that a 'required' field - check with Support); or you have to have a follow-on cgitask to prompt them for the reason behind the rejection and the cgitask should be owned by the same user who owned the review task (for grouptasks, this can be handled via an iwat trigger script that runs when the grouptask's ownership is "taken")

The subject of the post seems to indicate that you do now want an "extra" task - which again indicates user-training to me - however, if the review task is a cgitask to begin with - and the options to approve and reject are part of the CGI script's interface - then I would write the script to recurse upon itself or call it's own internal function to prompt for the rationale before performing the desired transition. As long as the task is properly owned by the reviewer and the CGI script is being called via the iw_cgi_wrapper.cgi (as JG already indicated) it should work correctly.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

kaalraa

Adam,

You are absolutely right as far as alternative way of doing the same is concerned. Actually .. in mycase this defect or change was told at the time when the code is already moved to production. So as a immediate step.. this was done.

But definitely... in due course of time the CGI task for rejection and approval ... would be added as a separate task. So as of now .. i am taking that there is no method to chnage the owner of a comment from iwui to any other user.

Thanks to all for your time ... the query and confusion is resolved now.

- ak's