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

"locktask" -> Help on success/failure propety

madmonkey

Hi,

I have been trying to declare successors for my locktask. its throwing an error asking me to pass in an array ref !! I tried declaring arrays for success and failure and passing in \@success and \@failure, still cant see anything. Can anyone please enlighten me on this ? Thank you in advance !

Find more posts tagged with

Comments

nipper

give some details, like what OS, what rev of TS

you may want to post the wft.

Andy

madmonkey

Sorry about that, its windows. TS version 6.0

declare_task( 'name'

name => "name",
desc => "name",
owner=>$iw_user,
avpath=>$iw_area,
success =>
failure =>

);

I am trying to use this locktask between a grouptask and a endtask.
So say I start the wf, attach files at the grouptask and fire off the lock task. On success it should get me back to the grouptask and on failure to the endtask.
I am positive that I have to declare the success and failure elements as task properties and not where we actually link them (correct me if I am wrong). So this is the scenario. Please give me your comments or suggestions. Thank you

nipper

That is not a WFT, what are you working with ? Is this a custom script that initiates a workflow ? Or is that one of the IWOV provided WFs ?

madmonkey

Thats part of a wft which has this task. The whole wft would be just another three tasks and the necessary code to support it. My question is just about how to declare a success or failure property on the "locktask" to link it to other tasks on success and failure transitions. So it would be great if you can help me link a "locktask" to other tasks in any wft.

madmonkey

To be more elaborate

declare_task( 'group'

name => "group",
desc => "group",
type => "grouptask",
owner=>$group,
avpath=>$iw_area,
);

declare_task( 'lock'

name => "lock",
desc => "lock",
type => "locktask",
owner=>$iw_user,
avpath=>$iw_area,
success => I dont know this part here
failure => I dont know this part aswell

);

declare_task( 'end'

name => "end",
desc => "end",
type => "endtask",

);

link_task("group", "lock", "go to lock task");

link_task("lock", "group", "success");this cant be used wfconstructor.pm throws an error. But this is what i want to achieve

link_task("lock", "end", "failure");this cant be used wfconstructor.pm throws an error. But this is what I want to achieve

I dont have the file on me to upload so cant do that, hopefully this will help you understand what i am trying to do. Thanks for taking interest in replying

Sailesh

you have to pass the task ids for the success and failure.

e.g. success => \@successIDs

Adam Stoller

you have to pass the task ids for the success and failure.

e.g. success => \@successIDs

Just to be clear here - the 'ids' are the initial value you use in the defintion of the task - for instance:

declare_task( 'lock'
              name => "My Lock Task",
              [...]
);

in the above example, 'lock' is the ID for the locktask named "My Lock Task".

madmonkey

Thanks you all. I think its a bug in the wfconstructor.pm so got it resolved.

Adam Stoller

Thanks you all. I think its a bug in the wfconstructor.pm so got it resolved.

The above statement is rather unclear.

You think it is a bug in WFconstructor.pm?
"so got it resolved" - ? Did you modify WFconstructor.pm? If so - how?
Or are you assuming that it is a bug in WFconstructor.pm and that it will eventually get resolved?

Please clarify.

nipper

The above statement is rather unclear.

You think it is a bug in WFconstructor.pm?
"so got it resolved" - ? Did you modify WFconstructor.pm? If so - how?
Or are you assuming that it is a bug in WFconstructor.pm and that it will eventually get resolved?

Please clarify.

I like that logic. Hmmm, doesn't work. Must be a bug. Someone else will fix it sometime. Lunch time. Bye...... :-)

Sailesh

A good one too Smiley Happy

kaalraa

Thanks you all. I think its a bug in the wfconstructor.pm so got it resolved.

Please provide details as how you have done? We have also identified some of them while working through wfconstructor.pm Smiley Happy