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

Nested workflow's job instantiation window

milind

Hii All,
Our requirement about Nested Workflow is like below.

Suppose a user task is followed by a nested workflow & transition between them is named as "Approve".

User Task---Approve--->Workflow Task

When user clicks on "Approve" he is provided with a button "Start Job". As user clicks it, the job instantiation window is opened, which means user has to click twice to get the job instantiation window. Is there any way so that user will need to click once and the window will be opened up?

In other words user clicks on "Approve" and the job instantiation window is opened.

We are using TeamSite6.5 on Win2k

Thanks & Regards

Milind

Find more posts tagged with

Comments

Adam Stoller

Hii All,
Our requirement about Nested Workflow is like below.
Suppose a user task is followed by a nested workflow & transition between them is named as "Approve".

User Task---Approve--->Workflow Task

When user clicks on "Approve" he is provided with a button "Start Job". As user clicks it, the job instantiation window is opened, which means user has to click twice to get the job instantiation window. Is there any way so that user will need to click once and the window will be opened up?

In other words user clicks on "Approve" and the job instantiation window is opened.

Thanks & Regards

Milind

You don't say what version of TS you're using, but assuming you're using at least 6.1 I think the following (from the IWHOME/local/config/wft/iwwf.dtd) applies:

<!-- ****************************************
     If background is 't', then TeamSite will attempt to start a job using the wftfile
     assuming necessary args will be provided in task variables (for details,
     see documentation for iwwft_compile.pl.  If background job creation fails,
     then the GUI will present the user the option to start a job.  Defaults
     to false (requiring user intervention).
     **************************************** -->
<!ELEMENT wftfile EMPTY>
    <!ATTLIST wftfile v CDATA #REQUIRED
                      background (t|f) "f">

milind

Hi Fish,
The TeamSite version is 6.5 on Win2k.

As per the documentation nested workflow is started in the background and it works.
What we are looking for is instantiation window when user clicks on the "Approve" transition.
In current WF, user has to click on "Approve" and then "Start Job".

Please let me know if I need to explain in more details.

Thanks & Regards
Milind

kaalraa

.
In current WF, user has to click on "Approve" and then "Start Job".

Thanks & Regards
Milind

Milind,

This would happen only be in case when the wft file is looking for any value to be passed out from the parent workflow. If your workflow has already been started in the background and has all the values needed within it, then it should start on its own without clicking "Start Job".

Just be sure that any value needed by wft file should be with it... before clicking on approve button. For example: if you are passing the value of as who has approved to the nested wft file.. then it always asked to Start the Job.

I hope you got what i meant to say.

milind

Hi Achin,

We want the job instantiation window, but the window should be opened up just after the user task.
Currently the sequence is
UserTask---Approve---Start Job--->Nested Workflow.

We need
UserTask---Approve--->Nested Workflow.

I hope you got what i meant to say.

Regards
Milind

kaalraa

Milind,

There are only three case... till now i have checked where a nested task ask for User intervention. (Start Job)

1. If the background=f or immediate=f is provided.

2. The nested workflow file is not valid. It can either be values still to get or any other issue.

3. The USER activating the nested workflow task is not a Master.

Still.... have any queries, anytime revert.

Hi Achin,

We want the job instantiation window, but the window should be opened up just after the user task.
Currently the sequence is
UserTask---Approve---Start Job--->Nested Workflow.

We need
UserTask---Approve--->Nested Workflow.

I hope you got what i meant to say.

Regards
Milind

Adam Stoller

Hi Achin,

We want the job instantiation window, but the window should be opened up just after the user task.
Currently the sequence is
UserTask---Approve---Start Job--->Nested Workflow.

We need
UserTask---Approve--->Nested Workflow.

I hope you got what i meant to say.

Regards
Milind

You might be able to get something like what you want by using a cgitask instead of a wftask and have the cgitask set with immediate="t" and be a simple wrapper that invokes the iwwft_instantiator.cgi - if you look at the file (it's a perl script in IWHOME/httpd/iw-bin) it provides information about the POST/GET arguments required.

milind

Achin,

I am not sure if I am conveying my requirements correctly to you.
I could start workflow immediately after a user task successfully (i.e. without opening instantiation window).
What I am trying is to open instantiation window in one click instead of two ( click1 = transition from user task, click2 = "Start Job" )

I hope this time I have made my point clear ! Please revert if I haven't ....

We are using TeamSite6.5, Win2K, Professional Interface.

Regards
Milind

milind

You might be able to get something like what you want by using a cgitask instead of a wftask and have the cgitask set with immediate="t" and be a simple wrapper that invokes the iwwft_instantiator.cgi - if you look at the file (it's a perl script in IWHOME/httpd/iw-bin) it provides information about the POST/GET arguments required.

Perfect, but I want to check possibility of job instantiator window to replace the CGI task.

Regards
Milind

chetansethi

Milind,

The owner of the wftask which should be a master user, then it wont give the "Start Job" button to the user.

Look at http://devnet.interwoven.com/forums_vb/showthread.php?t=15631&forumid=16 for more reference. This is exactly what you were so confidentaly talking about in this thread.

Cheers,
Chetan

Adam Stoller

Milind,

The owner of the wftask which should be a master user, then it wont give the "Start Job" button to the user.

Look at http://devnet.interwoven.com/forums_vb/showthread.php?t=15631&forumid=16 for more reference. This is exactly what you were so confidentaly talking about in this thread.

Cheers,
Chetan

I don't think you want to arbitrarily make the owner of the wftask a master user - unless you don't care who the job is instantied by (iw_user) or you don't think you're going to ever get audited by Interwoven for having all your users be masters...

kaalraa

As far as I have seen .... if the file given is a Job file then... it needs the user to be the Master else with the wft file.... it should work with any user who has access to run the workflow.

I don't think you want to arbitrarily make the owner of the wftask a master user - unless you don't care who the job is instantied by (iw_user) or you don't think you're going to ever get audited by Interwoven for having all your users be masters...

chetansethi

It is a trade off between keeping the history of the nested job or making a master user as owner. Depends on requirements.

I don't think you want to arbitrarily make the owner of the wftask a master user - unless you don't care who the job is instantied by (iw_user) or you don't think you're going to ever get audited by Interwoven for having all your users be masters...