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

Does setting require_workarea=false work for anyone?

lhdavis

TS 6.7.1 patch 1789, W2K3

We're using the new updated available_templates.cfg format. Per the workflow documentation (page 26 in the Release 6.7 Workflow Developer's Guide) I have the require_workarea attribute set to false.
<available_templates require_workarea="false">

Removing the attribute since it's default is false displays the same behavior.

With the one workflow (Create New Site) we have configured for a new_job command and I'm still prompted to select a branch and workarea.

<template_file name="Create New Site" active="yes" path="solutions/create_site.wft"">
<allowed">
<and">
<command name="new_job"/">
<or">
<role name="master"/">
<role name="admin"/">
<not">
<role name="editor"/">
<role name="author"/">
</not">
</or">
</and">
</allowed">
</template_file">

As this workflow is creating new branch and workareas, it doesn't need one selected. Selecting anything works but I don't want it displayed.

Has anyone else seen/experienced this issue?

Find more posts tagged with

Comments

Adam Stoller

TS 6.7.1 patch 1789, W2K3

We're using the new updated available_templates.cfg format. Per the workflow documentation (page 26 in the Release 6.7 Workflow Developer's Guide) I have the require_workarea attribute set to false.
<available_templates require_workarea="false">

Removing the attribute since it's default is false displays the same behavior.

With the one workflow (Create New Site) we have configured for a new_job command and I'm still prompted to select a branch and workarea.

<template_file name="Create New Site" active="yes" path="solutions/create_site.wft"">
<allowed">
<and">
<command name="new_job"/">
<or">
<role name="master"/">
<role name="admin"/">
<not">
<role name="editor"/">
<role name="author"/">
</not">
</or">
</and">
</allowed">
</template_file">

As this workflow is creating new branch and workareas, it doesn't need one selected. Selecting anything works but I don't want it displayed.

Has anyone else seen/experienced this issue?

Is this "one workflow" created via Workflow Modeler (WFM) or is it a WFT?

lhdavis

It's a .wft workflow. We're migrating our existing code from 6.1 SP2 to 6.7.1.

Adam Stoller

It's a .wft workflow. We're migrating our existing code from 6.1 SP2 to 6.7.1.

Hmm - I was thinking that this might be a WFM-specific setting - but I see it is in the "old" WF manual - for 6.7.0 as well as 6.7.1:[indent]The available_templates element is the container element for the file. This element contains the following attribute:abled?

However, that aside I have no working knowledge of this "feature" - sorry.

preview.png

lhdavis

I did create a support case for this Friday so I'll let you know what they have to say.

I've also attached the image here.

lhdavis

Here's what I've heard back from IWOV Support on this:
"This is a documentation bug. Bug #68666. The require_workarea=false is not a valid option to set for a new install, it was only intended for upgrade case to minimize the flexroles impact. The reason behind the error is when doing new job from the workflow tab, there is not branch context, so asking the system to show a list of authors,etc. is not a valid operation (since the system does not know who are authors without a branch). By default, require_workarea is true, so the WFT list will force the use to select a branch, that is how the role list can show. The documentation is going to be fixed so that it is more clear in the future (bug# 68666)."

While Interwoven may view this as only a documentation bug, this is a change in functionality for us when migrating from 6.1 SP2 to a clean 6.7.1 installation. As far as I can recall, this was not the default workflow behavior in 6.1, 6.0, 5.5, 5.0, and 4.5 so I've made a Feature Request for this functionality to be supported again.

Here's the business justification:
We have workflows that are administrative or system workflows that do not require a branch or workarea to execute. Or we have coded a specific branch/workarea in the workflow. So we do not require a user to select a branch/workarea. Therefore an option to NOT require a branch/workarea selection would be beneficial functionality to have.

The Feature Request description is "Allow workflows to be instantiated without having to specify a Branch/Workarea." and it's #71517. Please contact IWOV Support and add your company's name to the FR if you want this functionality back.

Migrateduser

Login to Teamsite as administrator. Go to Administrator tab--->Manage workflows--->Make require_workarea="false" --->save the Changes. Then try hitting New Job.

-- Kiran Shigli

lhdavis

1) That option is for Workflow models. We're using legacy workflows.

2) We filed a feature request, 71517, with Interwoven Support for "Allow Workflows to be instantiated without having to specify a Branch/Workarea."

Adam Stoller

1) That option is for Workflow models. We're using legacy workflows.

2) We filed a feature request, 71517, with Interwoven Support for "Allow Workflows to be instantiated without having to specify a Branch/Workarea."

If you're using a WFT - you should have control over whether you need to prompt for a workarea already - check the __VALUE__('iw_workarea') - if it has a value, don't prompt. If it doesn't have a value - prompt (or configure your workflows in available_templates.cfg so that the workflow is only accessible when within a workarea context)