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

iwaddtaskfile does not relase locks

ProfessorX

Any body having problems using iwaddtaskfile...then when the WF is complete and the files are submitted to stagging those files added by the iwaddtaskfile CLT remain locked?

Here are the steps

A WF is created
A CGI calls a DCR which is locked (submit locking) and edited
A file is added to the task by the CGI script calling...
# add the newly created DCR file to the task
$cmd = "$IWHOME/bin/iwaddtaskfile $taskID \"$dcr\" \"Associated DCR\"";
The users clicks a "Complete" button on the CGI task and then...




<submittask name="Submit"
owner="__TAG__('iw_editor');"
unlock="f"
savecomments="t"
description='Submit to STAGING'>

__INSERT__("<areavpath v='$editor_wa'/>");
<successorset>
<succ v="Publish"/>
</successorset>
</submittask>

The DCR still remains locekd
This happens when I click remove job as well.
This DOESN'T happen when I add the DCR directly using the GUI
[/b}

The Professor-

Find more posts tagged with

Comments

jbonifaci

Did you try unlock="t"?

ProfessorX

Thank you

yes that did work for submitting the files but how about when you remvoe the wf job?

Shouldn't any files associated with the wf be unlocked or how is that done?

The Professor-

james1

Just guessing here. The workflow job may only remove locks that it placed on the files. Since it didn't lock the DCR, it isn't going to unlock it either.

-- James

--
James H Koh
Interwoven Engineering

ProfessorX

Thanks James... I do believe we are on the right path.

I added to the group task right after the CGI task
<grouptask name="Editorial Review"
description="Select 'Start Task' from 'Operation' dropdown to approve or reject work"
lock="t"

... and it worked fine (when job was removed the files were unlocked)

The last glitch is that it is possible for the Approver to remove the WF Job while the CGI Task has not yet been completed or fails or other (See my orignal post)

So I guess what I am asking is how in my CGI script can I associate a lock with a WF Job The workflow job may only remove locks that it placed on the files??? I don't think iwlock.exe will do it? Anyone know of anyway you can?

The Professor-

james1

Sounds like your goal is to get the DCR locked by the workflow, which, I think, means a task has to be transitioned to a lock='t' task after the DCR is added to a task.

So, off the top of my head, here is one workaround/hack:

When the user interacts with the cgitask to add the DCR, you can do the following:

1. add the DCR to the cgitask
2. take an alternate transition from the cgitask to an externaltask
3. have the externaltask immediately callback
4. have the successor of the externaltask be the cgitask

Now the cgitask is active again, but the DCR is attached to it. If you make the cgitask lock='t', then the DCR will be locked too.

There are probably other tricks you can play, using other tasks, similar to the above scheme.

-- James

--
James H Koh
Interwoven Engineering