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

WORKAREA path missing while doing NEW JOB

navjot

Greetings,

Env
Teamsite 6.5, Solaris

Problem
I have one workflow which works fine when i try to "Submit" . "Assign" but when i do New Job, it throws an error . "Missing areavpath in external task".
I went thru documentation and it says iw_branch and iw_workarea are not available to WFT when the workflow is initiated thru New Job.
The idea behind doing this is someone will just start the workflow and later somebody else will create content and attach to workflow.

What are the different approaches to have some WORKAREA here? I know 2.
1. Assume some default workarea and code the workflow.
2. Ask the user about WORKAREA path in Job Defn Screen.

Are there any better options? If not, which one is good?

TIA
Navjot SIngh

Find more posts tagged with

Comments

Adam Stoller

Are you using the CCStd or CCPro UI?

If you're using CCPro - it should work just fine.
If you're using CCStd, I believe it's essentially the same as launching a new job from the To Do List in previous versions of TeamSite - i.e. there is no branch or workarea context, so you have to prompt for it (or add some customizations to provide a New Job link within the workarea views as opposed to launching a workflow from the main portlet view)

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

gzevin

actually this leads to an interesting discussion - why this New Job button was available at all? What I saw is that people are trying to re-create the same TeamSite functionality, just because this button was available and IWOV consultants for some reason did not want to disable it. In my opinion, it's redundant .....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

navjot

Thanks for your inputs.

I can invoke New job from CCPro from 2 different locations.

1. When i am in Content Tab and i click on Action->NewJob. [In this case, WORKAREA and BRANCH are avaibale]
2. When I am in Workflow Tab and i click on New Job link in top right corner. [In this case, WORKAREA and BRANCH are NOT avaibale]

I am not concerned about option 1. Option 2 is what bothers me. Why option 2 is there?
TIA
Navjot Singh

gzevin

Option 2 is what bothers me. Why option 2 is there?

it bothers me for more than 4 years..

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

Number 2 is exactly like being in the To Do List in the old WebDeskPro interface - there is no context at that point in which the system can determine a branch and/or workarea - so if you expect to launch a workflow from there you better have it coded to prompt for branch and workarea if the environment / form variables you're using don't exist. Either that or train people not to use it or find a way within the UITK to remove the option from the workflow screen (the last would be my preference as it would save a lot of headaches in the long run).

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

tsrookie

Hi Navjot,

When we instantiate a workflow job to set the workarea when no context is available we have implemented the following in each of the wft files.

You will have to modify to suit your purposes.

I have a config file where we keep the live branch names as opposed to those that aren't live yet and a perl module to read same.

Regards
Colin

my @liveBranches;

{ # destroy the configReader once we are finished with it
my $Config = new egov::configReader('internet');
my $tmp = $Config->get_value('live.branches');
@liveBranches = split /\,/ , $Config->get_value('live.branches');
}

my @option;
push @option, qq[<option value=""></option>\n];
foreach( @liveBranches ){
push @option, qq[<option value="/default/main/det/$_/WORKAREA/internet">$_</option>\n];
}

my($workarea_html) = join("", "<select name=\"iw_workarea\">\n", @option, "</select>\n");

my $wf_Workarea = __VALUE__('iw_workarea');

unless ( $wf_Workarea ) {
## FORM 1 ##
TAG_info(
iw_workarea => [
html => $workarea_html,
label => "Workarea",
is_required => "true"
],
);
}

Adam Stoller

All that code for putting together the dropdown list of branches and workares should be within the same conditional as the TAG_info() section that uses it - otherwise you're wasting time performing all those operations when you may not need to do so.

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