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; } } }

Waiting Window generation

Nidhi_Agrawal

Hi,

on my workflow i am using a external task for generating some html files and storing them within a folder.
But this process takes some time .So i want to show a intermediate window with some message likes "Processing files........".And as soon as files generation is complete the window should automatically get closed and also workflow get end.
Pls tell me what i hv to used for this and how???

Thanks in advance
Nidhi...

Find more posts tagged with

Comments

kaalraa

If i have understand your query right.... you want to have something called a in between processing page. As far as web development is concerned... you can use a CGI file as your external task.

Within the CGI file ... on start of it call a animated gif file to show as processing... and beyond that you can process your generation of HTML ffiles.

- ak's

Adam Stoller

you can use a CGI file as your external task.
Uhm - that's called a cgitask not an externaltask then.

In order for a cgitask to run immediately, without need for user interaction to initiate it - the cgitask must either:

run as a start task owned by the user who instantiated the workflow; or
run directly after a usertask owned by the same user; or
run directly after another cgitask which uses TeamSite::CGI_lite's iwcallback() function and is owned by the same user

If one of those scenarios is in hand (and the task is defined with immediate="t") then you should be able to do what is desired.

In any other scenario - the answer is "no" you cannot [reliably] do what was asked for -- in the case of the use of an externaltask the answer is "no".

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

kaalraa

Uhm - that's called a cgitask not an externaltask then.

Adam, I know that.. but i was just explaining the same in a little extra depth. Still thanks for correcting me out. Moreover i hope Nidhi would understand what i meant to say.

- ak's

Nidhi_Agrawal

Thanks for replies....
It is working now.But one more problem i am facing.
On my workflow there are two external task ,two user task and one cgitask and one endtask.
And all the externaltask and cgitask are not working without setting attribute start="t".
Even i hv set properly succ and pred but not getting success.

Nidhi..

Nidhi_Agrawal

ya,you had given me the direction of doing that job,which made me continue to work on.
thanks.

Nidhi....

Adam Stoller

On my workflow there are two external task ,two user task and one cgitask and one endtask.
And all the externaltask and cgitask are not working without setting attribute start="t".

This sounds like either a mis-diagnosis or some other form of confusion.

I already explained the conditions under which a cgitask will start immediately (and this is documented elsewhere as well).
An externaltask will run as soon as the task is transitioned to / [fully] activated - there is nothing about it being a 'start' task that has any bearing on whether it will run or not.

My guess is that you have incorrectly coded the workflow such that you have compound activation statements for these tasks and those conditions are never met -- but I cannot verify that without seeing the actual WFT (preferably as a job-description-file where it's pure XML; preferably as an attachment)

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

kaalraa

Could you please brief some more details on your workflow as what are the succ and pred defined.

- ak's

Nidhi_Agrawal

Even when i was not using cgi task ,then also it was asking for start="t" for both the externaltask.
Here is my attachment files.

Nidhi....

kaalraa

As per your attachement.. the start and immediate attribte should be used along with java call task. I think this is to be the first task you want to execute on calling the workflow. And rest on any successor task which should become active on transition just use immediate=t without using start attribute. In your case all CGItasks should have immediate=t.

Also i cant get use of the Intermediate_Task being used before external task (Email_Approver)... as you can directly use callback from within CGItask.

Hope this would help you to an extent.

- ak's

Nidhi_Agrawal

Hi Achin,

I am new for workflow.
can u explain me how to use callback from cgi.
I hv tried but not successful.
This will be more helpful if u can send me a sample code for that.

Is there any way to get information of task completion.As on my workflow u can see html files are generating.
Is there any flag is set when all the files are generated???

Nidhi....

reddyl

my $task = TeamSite::WFtask->new($task_id);
$task->CallBack($transition_no, $transition_comment);

or
`__IW_HOME__/bin/iwcallback $task_id $ret_code`

kaalraa

There are two ways to do that:

1. Using a CGI object: $cgi->iwcallback("Filelistconfirm","<description of succ task>")

2.Using the task object: my $success = $task->CallBack(0, "next task is called back");

- ak's

Nidhi_Agrawal

thanks .
How can i access the second parameter of callback ie the comment part, on my workflow.

Nidhi...

kaalraa

You need not to access that parameter.... as in first case it has to be the description of the task you want to run as its successor. And in second case the number 0 would automatically takes on the first succ task with in your element.

For example... if your task have 3 tasks ... then you can give the transition number either 0 or 1 or 2.

- ak's

Nidhi_Agrawal

thanks for reply.I got it now.

Nidhi..

Adam Stoller

I suggest you read the Workflow Tutorial Supplement (search for it by that string on this site) and/or take an Advanced Workflow Development training course (if it's still being offered - you do NOT want the course that focuses on Workflow Builder)

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

kaalraa

For which company you are working and where?? Can send Private message.... if dont want to disclose.

- ak's

Nidhi_Agrawal

I am still facing the problem of start="t" attribute.
My workflow is asking for this attribute for all the external tasks and cgitask.
Even i have used $task->CallBack() also on ipls.
Because of this i am not getting the exact sequence of tasks.
some tasks r running in parallel.When i see in log file i got first external task is started then without finishing it second task is also started and then so on..
So please suggest me some way to overcome this problem.

Nidhi...

jbonifaci

Please post your wft. You should not be required to have every task be a start task. But, obviously if they are all start tasks, every task is going to be started when the workflow is instantiated. TeamSite::WFtask->CallBack() shouldn't have anything to do with start tasks. It is used to transition external tasks once they are completed, so it's a good thing you have it in your external task perl scripts. I would strongly suggest that you take some workflow training through Interwoven. For now, please post your wft and hopefully someone can help you out.

~Jeff

kaalraa

Nidhi,

As Jeff has said.... not alll task need to be the starttasks. Secondly... are you specifying start=f in all the tasks?? Also i would suggest while attaching your wft file... please brief along what is the task sequence you are looking for?

- ak's

Nidhi_Agrawal

Thanks for ur replies.
Now it is done.I added only $task->Callback() to one ipl file,which i left.

Nidhi...

MyGroupTest.rptdesign

MyGroupTest.pdf

MyGroupTest.doc

Adam Stoller

From the previously posted wft - you had:[externaltask:java call (start="t")][usertask:Cgi_Intermediate][cgitask:CGI Task (start="t")][usertask:Intermediate_Task][externaltask:Email_Approver (start="t")][endtask:End]Assuming the WFT still looks like the above - if you remove the two start="t" attributes highlighted above and attempt to instantiate the workflow - what error do you see?
If you're not seeing an error what problem are you encountering that you thought was fixed by adding the start="t" attribute?

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

kaalraa

Adam,

Even i think the task [usertask:Intermediate_Task] is not needed because the CGI task is able enough to callback directly to the external task. If i am wrong somewhere please correct me.

- ak's

Adam Stoller

I don't know what is and is not needed because I don't really know what your workflow is trying to do.
However - your statement that "the CGI task is able enough to callback directly to the externaltask" is mostly correct. The callback is to the workflow engine, which can then allow transition to the next task (which in this case would be an externaltask)

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