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

[7.2.1] Workflow hangs on "Attaches Dependencies"

Hokumet

I am trying to create a custom WF. I am doing this with the help of the default "Publish livesite content" workflow.
After starting the workflow I come to the step "Attaches Dependencies". Then ist says "Added x new dependencies". And I see a loading icon.
But that's it. I wont go further than that.
When I go back to the "Workflow tab -> Tasks" I see that I can click on "Start input task" button. I see also the other 2 attached files. After clicking on this I goes to the "Attaches Dependencies" screen with message "No new dependencies where found".

What's wrong with my workflow why doesn't it go further?
Workflow node info

Transferonly false
Lock false
Immediate true
Name Attaches dependencies
Owner SVICSNL11\hikmet
AreaVPath /default/main/intranet/nl/WORKAREA/work
Variables TaskBeanId=workflow.task.DependencyTask|ImmediateTransition=true
Files sites/intranet-nl/boinb.page=;
Readonly false
CGIScriptName /iw-cc/Workflow/WebTask.do
Description Attaches dependent files to the job.

Find more posts tagged with

Comments

Adam Stoller

I am trying to create a custom WF. I am doing this with the help of the default "Publish livesite content" workflow.
After starting the workflow I come to the step "Attaches Dependencies". Then ist says "Added x new dependencies". And I see a loading icon.
But that's it. I wont go further than that.
When I go back to the "Workflow tab -> Tasks" I see that I can click on "Start input task" button. I see also the other 2 attached files. After clicking on this I goes to the "Attaches Dependencies" screen with message "No new dependencies where found".

What's wrong with my workflow why doesn't it go further?
Workflow node info

What kind of task immediately precedes the Attach Dependencies task?
Who owns the task that immediately precedes the Attach Dependencies task?

"immediate" for CGI Tasks (which Attach Dependencies appears to be) only works under certain conditions (detailed in the Workflow Developer's Guide)

Hokumet

There is no preceding task before the "Attach dependencies". Only Start

After "Attach dependencies" we have the "Review" task

Transferonly false
Lock false
Name Review
ReturnOnFirstReject false
ReviewOwner g-ics-intranet-nl-admins
NotifyReviewer true
Available Groups ics-intranet-nl-admins
ReviewType Serial
AreaVPath /default/main/intranet/nl/WORKAREA/work
Readonly true
Available Users ICS\interwoven
Brief Description Review Work
NoOfReviewers g-ics-intranet-nl-admins

Rick Poulin

The attach dependencies task from the PLC workflow uses some special code (WebTask.do) to do all the transitions via AJAX so the user never needs to leave the screen. My guess is that your next task needs to conform to whatever magic they did there, and you probably won't be able to transition to just any task. Either that, or you missed some properties of the task when you copied it over.

Adam Stoller

There is no preceding task before the "Attach dependencies". Only Start

After "Attach dependencies" we have the "Review" task
Transferonly false
Lock false
Name Review
ReturnOnFirstReject false
ReviewOwner g-ics-intranet-nl-admins
NotifyReviewer true
Available Groups ics-intranet-nl-admins
ReviewType Serial
AreaVPath /default/main/intranet/nl/WORKAREA/work
Readonly true
Available Users ICS\interwoven
Brief Description Review Work
NoOfReviewers g-ics-intranet-nl-admins

I asked the question because nowhere in the above do you indicate that it is a start task - so the next questions are:

Hokumet

What I meant with "Start" was, that "Attach dependencies" is the first task in the WF.

* Is the Attach Dependencies task owned by $IW_USER (the user who initiated the job)?

Yes, When I look at the WF in the WorkflowModeler it says "Owner=$IW_USER"

* Are you launching the workflow via Submit, New Job, Assign, a customer menu item, or a command-line oriented script?

I am launching the WF via Submit.

Maybe I should use something else for attaching dependencies but because I am new I thought I can copy the tasks from default WF and use it.
The WF worked well because it was a simple WF. But then I copied "Attach dependencies" from the default "publish livesite content" WF and it does not go further Smiley Sad

.
I just need a simple -> Submit workflow which do the following:
Attach dependencies (Does not work)
Review (Works now)
Author Rework (Works now)
Submit files (Works now)
Deploy files (Works now)

Adam Stoller

What I meant with "Start" was, that "Attach dependencies" is the first task in the WF.

Yes, When I look at the WF in the WorkflowModeler it says "Owner=$IW_USER"

I am launching the WF via Submit.

Hmm - not sure what to tell you, assuming that Attach Dependencies is a CGITask, a start task, owned by $IW_USER, with immediate=true, and you are initiating the workflow through the GUI - it should start immediately without requiring the user to click on Start Input Task.

Maybe there's something in one of the log files that might shed light on why it isn't doing so.
Maybe Support can help you figure it out.

Hokumet

Thanks for everything.
I don't know what happened. But "Attach dependencies" does work now. It goes further. But I am facing the following problem now.
The way it should work ( I think)

Start deploy workflow
Execute "Attach dependencies" task
Close window
Another user with enough rights go to the workflow tab
Chooses the right Task
Then clicks on the "Take" button
Can chose between the two possibilities (Accept or Reject)
etc
etc

What actually happens

Start deploy workflow
Execute "Attach dependencies" task
Window does not close, but user needs to fill in some comments in attachment "ScreenShot115.jpg"
After filling up something and selecting Accept or reject user clicks on Next an come to the "ScreenShot116.jpg"
Another user with enough rights go to the workflow tab
Chooses the right Task
Then clicks on the "Take" button
Can chose between the two possibilities (Accept or Reject)
etc
etc

Point 4 is optional because. You can also click cancel. And go further to the WF tab. But it's an annoying and unneeded step. So why do I have this step? How can I remove it?

If you have any question or my situation is not clear, contact me please

jasonmcneil

Would you be able to post a screenshot of your workflow model?

Hokumet

Thanks you in advance

This is my workflow.

Crsb

Thanks for everything.
I don't know what happened. But "Attach dependencies" does work now. It goes further. But I am facing the following problem now.
The way it should work ( I think)
Start deploy workflow
Execute "Attach dependencies" task
Close window
Another user with enough rights go to the workflow tab
Chooses the right Task
Then clicks on the "Take" button
Can chose between the two possibilities (Accept or Reject)
etc
etc
What actually happens
Start deploy workflow
Execute "Attach dependencies" task
Window does not close, but user needs to fill in some comments in attachment "ScreenShot115.jpg"
After filling up something and selecting Accept or reject user clicks on Next an come to the "ScreenShot116.jpg"
Another user with enough rights go to the workflow tab
Chooses the right Task
Then clicks on the "Take" button
Can chose between the two possibilities (Accept or Reject)
etc
etc
Point 4 is optional because. You can also click cancel. And go further to the WF tab. But it's an annoying and unneeded step. So why do I have this step? How can I remove it?

If you have any question or my situation is not clear, contact me please

This is a known issue, support has a workaround for it.
I don't remember the details of the workaround but it involves adding some dummy cgi task with cgi cmd before the task that is not closing. the workaround will work for you according to the requirements you listed.