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

How to set priority flag during WF creation

HolgerOstermann

Hello everybody,

We are testing TS 6.1 on a solaris 8 box.
The new TS GUI provides a priority flag in the task/job list. Itś a nice feature but only visible/accessible in the todo-list.

We want to set the priority flag already in the Job instantiation. Is there a TAG_info directive for the priority flag ?
We want to get information of the priority flag in an external task (customized email task) too. If this is possible, we can relay this information to the email priority. How can we get e a perl TeamSite::WFtask function to gather the value of the flag?

Thanks in advance...

Find more posts tagged with

Comments

Jeremy

Hi,

I believe you need to make some changes to your iw.cfg file for the UI to pick up these fields.
The priority would then have to be set as a job variable I think.
I haven't done this myself as yet, but take a look at this TechArticle:
http://devnet.interwoven.com/site.fcgi/techlib/051363
Also take a look at the suer customisation guide.

I am sure someone who has done this would be able to chime in with the exact changes.

HTH

Jeremy

rollo

For the sake of the archives, I'll answer this since I just figured it out (priority and due date for good measure)

The TAG_info directives are:
iw_setwfarg_priority
iw_setwfarg_due_date

You can then access them later in an external task in the usual way:

my $job = new TeamSite::WFworkflow($wfid);
my $priority = $job->GetVariable('priority');
my $due_date = $job->GetVariable('due_date');

(that of course assumes that you've identified the workflow ID in @ARGV as $wfid, and that you're use-ing TeamSite::WFworkflow but then you probably knew that already).

That's how I did it anyway. It does work, although I couldn't say if it's supported or not.

Phil

Adam Stoller

It's supported because the prefix iw_setwfarg_ on TAG_info() variables causes them to be automagically turned into job variables during instantiation - and the job variables is how the feature of priority and due date were originally (and currently) implemented.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rollo

Great, even better. I only wondered as I could find nothing about it in any of the 6.x WF docs I have, and I seemed to remember that some iw_setwfarg stuff way back was considered 'back door' (in fact looking at the 5.5.2 WF docs there's no mention of iw_setwfarg at all, which is odd considering how useful I have found it).

So I guess rather than whether it's supported, the question is how long it will continue to work. But it's hardly a major customisation so it probably doesn't matter all that much.

Phil

Edited by rollo on 06/06/05 09:11 AM (server time).

Adam Stoller

iw_setwfarg_ should remain supported for as long as the current wft structure remains supported. It missed getting documented in the original workflow manuals and a number of subsequent revisions but it was intended as a supported fuction and *IS* documented:
- in the 5.5.2 Workflow Developer's Guide (p. 59) [*this might be the SP3 rev of the docs*]
- in the 6.0 Workflow Developer's Guide (p. 56)
- in the 6.5 Workflow Developer's Guide (p. 120)

6.7 is supposed to introduce a new form of workflow development - but I believe that will be co-existing with the current wft implementation for at least a release or two (chances are that wfts, as we know them, won't go away until at least 7.0 - and hopefully by then they'll have a way of automagically converting existing wfts to the new format). Don't run in panic yet though - wait until they actually release 6.7 and you get a chance to look at it before worrying too much.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rollo

Thanks for the reply. We only just got to 6.1 so I imagine I'll be living on the moon and driving a hovercar before we install 7.0.

cheers Smiley Happy

Phil

Adam Stoller

FYI - on behalf of 6.7's new workflow stuff - I've seen a demo, it's reasonably nice, but [as of GearUp] wasn't quite "ready for prime time" (as I don't think 6.7 is due out until early 2006 - that's okay).

Hopefully I'll get to peek at it a few more times over the coming months to see how things are progressing and stick my $0.025 in here and there.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

HI ghoti,

In continuation to the above discussions, is it possible to Display the Due date set in the Workflow INitiation form onto the job details page in the Content Centre????

-dixit

kaalraa

HI ghoti,

In continuation to the above discussions, is it possible to Display the Due date set in the Workflow INitiation form onto the job details page in the Content Centre????

-dixit

Set two job variables as "Priority" and "Due_Date" after workflow initiation form.

$job->SetVariable("Priority", $priorToMe);
$job->SetVariable("Due_Date", $dateDue);

Due date value should be in mmddyyyy format.

Migrateduser

Set two job variables as "Priority" and "Due_Date" after workflow initiation form.

$job->SetVariable("Priority", $priorToMe);
$job->SetVariable("Due_Date", $dateDue);

Due date value should be in mmddyyyy format.

I am doing that only, it does not work.. The due date set here does not appear in the contentcenter

-dixit

awizardly

Try something along the lines of

    
      iw_setwfarg_priority =>
          [ html  => '
                           High
                           Medium
                           Low
                         ',
            label => "Priority",
            is_required => "true",
            ],

That block should be in your TAG_INFO declarations.

I believe due date can be set in a similar way, but I believe the appropriate variables are all lower cased

If someone can tell me how to get that select to show up as code as opposed to html that could help me out.

Adam Stoller

Try something along the lines of

    
      iw_setwfarg_priority =>
          [ html  => '<select>
                           <option value="1">High</option>
                           <option value="2" selected>Medium</option>
                           <option value="3">Low</option>
                         </select>',
            label => "Priority",
            is_required => "true",
            ],

(I write it out as <<x>tag>...<<x>/tag> the 'x' part gets consumed leaving behind the desired '<' part)

awizardly

thanks, I was playing with the editor and not having alot of luck

Adam Stoller

I am doing that only, it does not work.. The due date set here does not appear in the contentcenter

-dixit

I'm not positive - but I believe the variable names need to be "priority" and "due_date" - all lower-case.

kaalraa

I'm not positive - but I believe the variable names need to be "priority" and "due_date" - all lower-case.

Dixit,

Please share your experience if the variable names are case-sensitive.

awizardly

I know priority has to be lowercased, I have this implemented in a workflow from which I pasted the TAG_INFO segment. It also should be due_date all lowercased. You can verifiy this by setting due_date in an existing workflow and see what variable gets set in the job variables.

Adam Stoller

I know priority has to be lowercased, I have this implemented in a workflow from which I pasted the TAG_INFO segment. It also should be due_date all lowercased. You can verifiy this by setting due_date in an existing workflow and see what variable gets set in the job variables.

It's not a question of what variable gets set as a job variable (if you use iw_setwfarg_DuEdAtE - the variable will be DuEdAtE) - it's a question of what variable the OOTB Workflow UI is set to track - and that, I believe is "due_date" all lower-case - but I don't have a system to use to verify that right now.