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

Update Task error

JoshProx

I've created a workflow template which works fine except the update task which says "No successors defined" on workflow initiation. I've checked the wft file with iwwf.dtd and it's all OK. I'm attaching the code and error for reference. I am currently using successortset element which is deprecated in 6.7.1. I'll be later on modifying that but it should all work as it's still supported as per the dtd. Kindly let me know your feedback for the same.

Thanks,
Josh

Find more posts tagged with

Comments

JoshProx

No replies. Any feedback is much appreciated!!!

ISCBorisB

I've checked the wft file with iwwf.dtd and it's all OK...

No it's not.

Your "Invalid Workflow" Error Message is clear. You did not code <successors> Tags in several Tasks, not only Update_Admin.
You have <successorset> Tags, note though that they should be sub tags of the <successors> Tag.

JoshProx

Thanks for your reply. I am not sure if that is the reason as the workflow works fine if I comment out the updatetask. Also the successors are not required for all tasks as per iwwf.dtd. Here is an excerpt from the dtd

ELEMENT usertask (description?, areavpath, successors, timeout?,

ELEMENT submittask (description?, areavpath, successorset|(success,failure?),

ELEMENT updatetask (description?, areavpath, successorset|(success,failure?),

ELEMENT externaltask (description?, areavpath, successors, command,

ISCBorisB

I am not sure if that is the reason...

I am. If you are not, make sure.

Try to enclose naked successorset Tags into successors Tag. Double-check that you do that for all tasks where it's missing.
Does it work? Btw, why would IWOV make succession Syntax different for the update/submit Task?

JoshProx

I don't think successors are mandatory for each kind of task as per iwwf.dtd 6.7.1. Infact my workflow works perfectly if I comment out update task. successorset is anyway deprecated in 6.7.1 and I need to update my wft with success and failure tags, which I'll do it at a later point in time. In my post I've also put an excerpt from iwwf.dtd which confirms what I am saying.
I'll also try as you have suggested and see if that works.

ISCBorisB

I don't think successors are mandatory for each kind of task as per iwwf.dtd 6.7.1.

You do not have to convince me. It's your Project.

Just try to convince TS WF Engine first, as far as I know it is still complaining that "No successors declared in update task Update_Admin".
Guess what, this is correct. You did not declare any successors in this particular task (and at least one more). The way I read it, WF Engine
clearly disagrees with your thinking.

True, in 6.7 the 'successorset' element has been deprecated in favor of 'success' element. You still use them though, deprecated or
otherwise. Since you do, you might as well do it correctly. The fact that your WF really instantiates when you comment out an update task
means exactly zilch. If you do that, submittask becomes an orphan node in the WF oriented Graph and orphans are silently pruned out by WF Engine.

Adam Stoller

According to the DTD you either use a successorset or a success and failure sub-element - you cannot use a combination (e.g.: successorset and failure).

The updatetask is not supposed to have a successors element in it (at least according to the DTD - and it's been that way for a while.

The problem is two-fold. The error message is wrong and the WFT is wrong.

The first - I'll leave up to someone to file a bug with IWOV on.

The second - the code shows:

   <updatetask name="Update_Admin"
                owner="__TAG__('iw_dm');"
                start='f'
  lock='t' >
 <description>
                Copy_to_Area from Toyota Branch
        </description>
        __INSERT__("<areavpath v='$admin_vpath'/>");
__INSERT__("<srcareavpath v='$area_vpath'/>");
        <successorset description='Copying files to ToyotaAdmin branch workarea'>
         <succ v="Submit_Admin"/>
        </successorset>
        <activation>
              <pred v="Deployment_Mgr_Approval"/>
        </activation> 
   </updatetask>

The DTD, however, stipulates that the srcareavpath must come after the successorset. If you move that second __INSERT__ line below the successorset and above the activation tag - it should work.

ISCBorisB

The DTD, however, stipulates that the srcareavpath must come after the successorset. If you move that second __INSERT__ line below the successorset and above the activation tag - it should work.

Ah, yes... I've completely mis-diagnosed this one.
Guess I was doing all that with WFConstructor for far too long

Thanks Adam.

JoshProx

Thanks guys for your feedback....It works now...I guess the wrong error message confused me....

catorarn

TeamSite 672/win2003

I would like to ask a question as regards to this thread. I also put into place the updatetask:

[html]

owner="__TAG__('iw_areaowner');"
description="Update without Overwrite"
start="f"
overridemod="f"
lock="f"
delete="t" >

__INSERT__("");

__INSERT__("");

[/html]

I would expect the updatetask to NOT overwrite the version in the $workarea path as I have overwritemod="f". However, it overwrites the version with the STAGING version.

Am I wrong here?

I have the following setup:

I have 2 workareas. One workarea contains DCRs that have image paths like "imported/images/(..)/billboard.jpg. I have a urlexternaltask which transforms this path to an encrypted path and copies this file to the second workarea. Then from that workarea I submit to STAGING. I want to then update the original workarea keeping the original version with the unencrypted path, so that the user is presented with the path he/she entered. I hoped that the overwritemod flag to "f" would be equivalent to the get latest dialog option "keep my current version". In this installation, we do not want users to do any get latest actions (we took out all these options in using the UI toolkit).

Adam Stoller

TeamSite 672/win2003

I would like to ask a question as regards to this thread. I also put into place the updatetask:

[html]

owner="__TAG__('iw_areaowner');"
description="Update without Overwrite"
start="f"
overridemod="f"
lock="f"
delete="t" >
...

[/html]

I would expect the updatetask to NOT overwrite the version in the $workarea path as I have overwritemod="f". However, it overwrites the version with the STAGING version.

Am I wrong here?

...

Have you tried fixing your code? The attribute name is overwritemod not overridemod as you show in your code.