Menu item calls multiple workflows - Teamsite 6.7.2

We have a customized delete function in our Teamsite setup. Rather than trying to put all of the logic for different branches into one workflow which can make it hard to read, I wondered if I can have the delete function call workflow1 for XYZ branch and workflow2 for all other branches. Is there a clean way to have the delete function kick off a script that will determine the branch and then execute the appropriate workflow? I thought I could do this via available_templates.cfg, but this delete function doesn't use that file it uses a custom XML file that tells it to execute the one delete workflow today. Anyone have ideas to make this work and keep the code as clean as possible?

Thanks!

Find more posts tagged with

Comments

ISCBorisB

...this delete function [...] uses a custom XML file that tells it to execute the one delete workflow

What's stopping you from modifying "this delete function" slightly so that it branches to one or
another custom XML (WF Specs presumably?) depending on the activation Branch?

ALT

There isn't anything in the XML today used to execute the workflow that indicates the branch and I'm not sure how to go about doing that. If there is a way to tell Teamsite that the menu delete option executes xyz.wft when it is this branch and abc.wft when it is all other branches, that would be great, I just don't know how to make that happen.

ISCBorisB

There isn't anything in the XML today used to execute the workflow that indicates the branch and I'm not sure how to go about doing that. If there is a way to tell Teamsite that the menu delete option executes xyz.wft when it is this branch and abc.wft when it is all other branches, that would be great, I just don't know how to make that happen.

When TS executes Code behind your custom Menu command, it posts a certain Form to it.
One of the Form entries is 'cwd.vpath'. From there, you (your code rather) can get a
Branch where your customer was when he clicked Menu's link.

After that it is up to you to code conditional processing that is Branch-dependent, instantiate
different Workflows and whatnot.

As to "There isn't anything in the XML [...] that indicates the branch", well... This is your
custom code. We have no way of knowing what is or isn't there, how you process it and what
should be changed to alter this processing. You'd have to follow code and see if you can make
required changes.

Adam Stoller

In the spirit of giving and following the theme of what was already posted, and assuming your custom menu item is written in Perl ... you could do something like this:

use TeamSite::CGI_lite;
my $cgi = TeamSite::CGI_lite->new();
$cgi->parse_data();
my $vpath = $cgi->{form}{"cwd.vpath"};
(my $branch = $vpath) =~ s|^//[^/]+/[^/]+/main/([^/]+)/.*$|$1|;

my $configs {
    branch1 => "abc.wft",
    branch2 => "def.wft",
    branch3 => "xyz.wft",
};

my $config = $configs->{$branch};
...

Obviously the above is based on a simple root-branch approach, if you need to use a different part of the path just adjust the code accordingly or write it out in a longer if/elsif/.../else format.

(you could also use CGI instead of TeamSite::CGI_lite - but again, adjust the code accordingly)
Enjoy.

ALT

Thanks for the input! I'll put some code together based on the information provided and see if I can make this work.

Thanks again!