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

New WFConstructor Syntaxes

awizardly

I am trying to use the new TeamWFConstructor Syntax that I saw in the configurable default_submit, and things seem to be pretty useful, but I can't find documentation for this module, or any specific syntaxes on how to handle group tasks. Any help would be appreciated.

Find more posts tagged with

Comments

Migrateduser

On Windows,
`iwgethome`/iw-perl/bin/perldoc.bat TeamSite::WFconstructor

Brinko Kobrin
Interwoven Staff Engineer

awizardly

I have found most of what I am looking for in delving through the perldocs, and through the example scripts.

The one area that was not clear to me, but I eventually figured out is the sharedby attribute of a group task.

I eventually found that the input should be an array of 2 element arrays. The 2 element arrays should be [ "user" , "$username" or [ "group" , "$groupname"]. Replacing the variables with your appropriate information. What was not clear was the way to pass the array into the task declaration. I found I had to pass the array using \@ for the array.

Example
undef @groupvalue;
$groupvalue[0] = ["group" , "$app_group"];
$groupvalue[1] = ["user" , "$iw_user"];
declare_task('promote_to_dev_errored',
name => "Promote to Development Errored",
description => "Error in Development Promotion",
type => "grouptask",
sharedby => \@groupvalue,
areavpath => $areavpath
);
Overall I have found the "network" method for developing workflows infinitely easier to manage than the standard xml definitions with mixed perl. It takes a little getting used to, but works very well.

Now I am having some problems with the iw sendmail script in HTML mode, but that is another post. Sorry for the formatting but the input form seems to crank on the tabs and spacing of the code.

Migrateduser

That's unneccessarily convoluted. Since you are populating the array right there, just do an anonymous array, e.g.


declare_task('promote_to_dev_errored',
    name => "Promote to Development Errored",
    description => "Error in Development Promotion",
    type => "grouptask",
    sharedby =>  [ ["group" , "$app_group"],
                         ["user" , "$iw_user"] ],
    areavpath => $areavpath
);

awizardly

An anonymous array is only feasible when the amount of data is small. The code snippet I posted before is an example of how I have found a way to assign members to a group task.

In my specific implementation I manage the members of reviewer, developer, approver groups through a secondary configuration file that I have developed.
With this configuration file I pass into group tasks a list of users and not a group.

There are several reasons for this.
1 the configuration file is in a versioned location in a configuration branch in TeamSite and is therefore editable by people don't have root access to modify OS group permissions. (Most people in our environment)

2 The 16 group limit per user in Solaris based implementations of TeamSite precludes the mass use of groups to primarily designate tasks that are only relevant to the workflow and not file access.

So even though the reference syntax looks more complicated it is necessary. Also what do you think passing an anonymous array into the instantiator does? It passes an array reference.