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

iwconflictcheck.ipl

phenom

I am trying to write a workflow with four tasks - cgi task 1, cgi task 2, submit task and end task - in that order. Both the cgi tasks have same owner, immediate attribute set to "t" and cgi task 1 uses TeamSite::CGI_lite::iwcallback. The transition from cgi task 1 to cgi task 2 is also immediate as expected.

I am trying to re-use iwconflictcheck.ipl (unmodified and as provided by interwoven) within cgi task 2. However, I cannot seem to transition to the resolve conflicts screen. (Yes, the attached files are in conflict). iwconflictcheck.ipl shows "submitting files" within the cgi window and the window gets closed. But the workflow is active with "Resolve Conflict" as it's current task. But when I delete cgi task 1 within the workflow and use cgi task 2 (with iwconflictcheck.ipl) as the start task, the resolve conflicts screen shows up perfectly fine.

I tried to debug a bit and found that iwconflictcheck.ipl does a CallBack and then tries to check if submit task is active. If active, it redirects the browser to /iw-cc/resolveconflict with submit task's task_id as a parameter.
But when I use it as cgi task 2, the ipl cannot read the submit task's task_id.

Any ideas?

Find more posts tagged with

Comments

ISCBorisB

iwconflictcheck is a CGI Task in its own rights, with certain assumptions about underlying Workflow,
corresponding Task transition mechanisms etc. Moreover, unlike your schema it's the Task designed to run
after Submit Task that identified Conflicts, etc.

So, although it is feasible that you can re-use it somehow for your needs I doubt you'd be able to do that
in a "black-box" mode. If I were you, I would've tried to see what iwconflictcheck does and use it as a model
for what you are trying to accomplish

phenom

True. The iwconflictcheck.ipl is used to check conflicts after the submit task is initiated. But the transition to submit task takes place within the iwconflictcheck.ipl (via callback) and then the same iwconflictcheck.ipl checks for file conflicts and re-directs to the resolve conflicts screen. That is how the default submit workflow works. What I have done is - add a cgi task before the iwconflictcheck.ipl. This should work, right? But surprisingly, somehow the transition to submit task is not taking place within iwconflictcheck.ipl when it is used as a second task within the workflow? Does this mean that iwconflictcheck.ipl can only be used within a start task and no where else?

Adam Stoller

True. The iwconflictcheck.ipl is used to check conflicts after the submit task is initiated. But the transition to submit task takes place within the iwconflictcheck.ipl (via callback) and then the same iwconflictcheck.ipl checks for file conflicts and re-directs to the resolve conflicts screen. That is how the default submit workflow works. What I have done is - add a cgi task before the iwconflictcheck.ipl. This should work, right? But surprisingly, somehow the transition to submit task is not taking place within iwconflictcheck.ipl when it is used as a second task within the workflow? Does this mean that iwconflictcheck.ipl can only be used within a start task and no where else?

Since it is a Perl script - you could easily make a copy of the script and in your copy add a bunch of debugging to see where it gets hung up.

My guess though, just taking a look at the code (which you can do, because it is a Perl script) - is that you're running into an issue with not setting the task variable "submittask_name" on your cgitask, and the fact that the submittask is not yet "active" and does not yet "NeedAttention" (both aspects of the submittask that iwconflictcheck.ipl looks at.

Given all this - creating a copy of iwconflictcheck.ipl and reverse-engineering it to fit your needs (instead of the needs it was designed to fit) would probably be the only way you're going to get this to work the way you are trying to do so.