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

submittask success/failure logic

NathansDIS

I understand that somewhere in TS 6.x, the notion of branching to different successors based on the success/failure of a submittask was implemented by Interwoven. This is apparently much like the ability to branch based on the outcome of a lock task? Does anyone have any idea where to find the documentation or an example of this feature? Thx!

-Nathan
Washington State DIS

Find more posts tagged with

Comments

james1

The documentation covering locktask (regarding success/failure successorsets) should be applicable to submittask and updatetask. Do you have any specific questions?

-- James

--
James H Koh
Interwoven Engineering

NathansDIS

Thanks for your reply. Can you post some example XML on this? I am new to tinkering with workflow and would really appreciate it. I want to have my submit task transition to a deploy task on success and transition to another submittask owned by an administrator(who will resolve the conflict) on failure. Here is my workflow XML as it sits now if that will help. Thanks!

-Nathan

~~~

<workflow name="Author_Submit"
owner="__TAG__('iw_areaowner');"
creator="__TAG__('iw_areaowner');"
description="__TAG__('iw_submit_comment');">

<externaltask name="Email_Review"
owner="__TAG__('iw_user');"
description="Send Email"
start="t">

<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Review">
<succ v="Review"/>
</successorset>
</successors>
__INSERT__("<command v='$perl_cmd $mail_cmd -t $review_email' />");
<template_script><![CDATA[
if (@submit_file != 0)
{
__INSERT__("<files>\n");
for (my $i=0; $i < @submit_file; ++$i)
{
__INSERT__("
<file path='$submit_file[$i]' " .
"comment='__TAG__(File_comment_$i);'/>");
}
__INSERT__("</files>\n");
}

]]></template_script>
</externaltask>

<grouptask name="Review"
owner="__TAG__('iw_areaowner');"
description="Content Review"
start="f"
readonly="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="7:30am Deploy">
<succ v="Submit"/>
</successorset>
<successorset description="Emergency Deploy">
<succ v="SubmitDeploy"/>
</successorset>
<successorset description="Reject">
<succ v="AuthorWork"/>
</successorset>
</successors>
<sharedby>
__INSERT__("<group v='$approver_group' />");
<user v="dshs/colsoc" />
</sharedby>

</grouptask>

<usertask name="AuthorWork"
owner="__TAG__('iw_user');"
description="Author Work">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Changes Complete">
<succ v="Email_Review"/>
</successorset>
</successors>
</usertask>

<submittask name="Submit"
owner="__TAG__('iw_areaowner');"
description="Content Submission"
unlock="t"
savecomments="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successorset>
<succ v="End"/>
</successorset>
<variables>
<variable key="submit_cmt" value="__TAG__('iw_submit_comment');"/>

</variables>
</submittask>

<submittask name="SubmitDeploy"
owner="dshs/colsoc"
description="Content Submission."
unlock="t"
savecomments="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successorset>
<succ v="Deploy"/>
</successorset>
<variables>
<variable key="submit_cmt" value="__TAG__('iw_submit_comment');"/>

</variables>
</submittask>

<externaltask name="Deploy"
__INSERT__("owner='$external_task_owner'");
description="Deploy"
>

<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Done">
<succ v="End"/>
</successorset>
</successors>
__INSERT__("<command v='$perl_cmd $od_cmd' />");
</externaltask>

<endtask name="End">
</endtask>

</workflow>

james1

I hope you find this intuitive:


<submittask name="Submit"
    owner="__TAG__('iw_areaowner');"
    description="Content Submission"
    unlock="t"
    savecomments="t">
  <areavpath v="__TAG__('iw_workarea');"/>
  <success>
    <succ v="Deploy"/>
  </success>
  <failure>
    <succ v="AdminSubmit"/>
  </failure>
  <variables>
    <variable key="submit_cmt" value="__TAG__('iw_submit_comment');"/>
  </variables>
</submittask>

-- James

--
James H Koh
Interwoven Engineering

NathansDIS

Indeed, thanks!

Migrateduser

I have a question. Why isn't it reflected in the documentation? And please don't give me the same answer as the last Interwoven guy did: It's in the DTD file. That's not acceptable. It should be in the Workflow Manual, especially since the DTD is cut and pasted into the Workflow Manual - I shouldn't have to look at a DTD file because the documentation might not be complete. Make the documentation complete. We certainly pay enough for it.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com