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

available_templates.cfg

nirali

TS 6.7.1. SP2

Workflow manual I am referring - TS6.7.0 wf.pdf

1) In the available_templates.cfg file that I am referring[html][/html] tag is not used at all. Is it required to include [html][/html] tag in cfg file in order to grant access to individual users or users of a branch because thats how it is given in pdf manual?

2)In the pdf manual in the user list "name" attribute is used, while the file I am referring to "value" attribute is used. Is it ok to use either way ?

3) As per pdf (6.7.0)manual, workflow template must reside in either of
iw-home/local/config/wft/default/upload.wft
iw-home/local/config/wft/solutions/upload.wft
iw-home/local/config/wft/examples/upload.wft

while the file I am referring to is located in Capital(This is TS6.7.1), is this allowed ?

4) As per PDF manual(6.7.0), in the ACL
[html][/html]
This is an absolute path. So is it true both ways , with relative path and with absolute path ?

Following is the available_templates.cfg I am looking at.

[html]

[/html]

Pls explain

Find more posts tagged with

Comments

Adam Stoller

TS 6.7.1. SP2

Workflow manual I am referring - TS6.7.0 wf.pdf
...

Pls explain

First of all - there is no SP2 for 6.7.1 - there's only SP1 (there are several patches, but only one service pack) - there's also a 6.7.2 release. So I'm not sure what you're using.

Second - you should download the correct versions of the manuals - TeamSite WorkflowDeveloper’s Guide Release 6.7.1 Service Pack 1 (didn't change for 672) - and read that manual instead of the 6.7.0 version.

The DTD for available_templates.cfg changed when 6.7.1 was released, and the documentation for it was updated in the manual.

nirali

Its TS6.7.1 SP1

In available_tamplates.dtd of the config file I am looking at, in branch element there is no sub-element wherr you can specify branch details.

In the available_templates.dtd, branch element is specified as

[html]

[/html]

There is no branch-list element and there is no sub-element under branch element. There is no user-list element (only user). So how can we create available_templates.cfg as specified in my question ?
How to understand this DTD ?

In the branch element, can we specify path to WORKAREA level ? Will it mean that even in a same b ranch only specific workarea will have access to this workflow and not all WAs will have access ?

thanks

Adam Stoller

Its TS6.7.1 SP1

In available_tamplates.dtd of the config file I am looking at, in branch element there is no sub-element wherr you can specify branch details.

In the available_templates.dtd, branch element is specified as

[html]

[/html]

There is no branch-list element and there is no sub-element under branch element. There is no user-list element (only user). So how can we create available_templates.cfg as specified in my question ?
How to understand this DTD ?

In the branch element, can we specify path to WORKAREA level ? Will it mean that even in a same b ranch only specific workarea will have access to this workflow and not all WAs will have access ?

thanks

If you don't understand the DTD - perhaps you should search Google, get training, or get the manual I suggested in my previous post (why are you trying to use old manuals with a new version of the product?)

The branch element has always been just that - a branch element.
It has, in the past (and I believe still may) work through the workarea and even directory path) for some methods of invoking workflows - it has always been limited to just the branch path for tt_data (and tt_deletedcr) methods of invoking. For submit and new_job commands, it has (in the past) been able to take full path specifications through the branch all the way to a directory within a workarea - though that was claimed as a "bug" it was a "feature" that many customers (and consultants) used - so I assume it still works that way - but I haven't tried.

The allowed element is now a container element for the entire specification of a workflow template (instead of a sub-sub-container) - there are now *_list elements - now there are just the basic elements of command, role, user, branch - and group (which didn't exist before).

nirali

thanks for the answers.

I can understand DTDs very well. Problem here is I dont see branch_list or user_list specified in DTD and its used in CFG file.

So whats the syntax for this branch_list or user_list ? I did go through ts6.7.1sp1wf manual and in that also syntax is not specified. Thats why Im confused and still I have not got answer about how to use branch_list and user_list.

Pls explain.

DPC williams.rptdesign

Adam Stoller

thanks for the answers.

I can understand DTDs very well. Problem here is I dont see branch_list or user_list specified in DTD and its used in CFG file.

So whats the syntax for this branch_list or user_list ? I did go through ts6.7.1sp1wf manual and in that also syntax is not specified. Thats why Im confused and still I have not got answer about how to use branch_list and user_list.

Pls explain.

If you're seeing it in the config file - then the config file is old and didn't get updated, or someone put back the old one not realizing that the format changed.

There is no branch_list or user_list anymore as of 671

sniv

Hi Nirali !

For Point 1: No need to include the "allowed" tag if not required.

For Point 2: Yes ! you can use "name" attribute instead of "value" attribute. It can be ok to use either ways.

For Point 3: Here your "Capital" dir should be located under the >> iw-home/local/config/wft/default/ folder only

For Point 4: you can refer branch value as:

branch value="/default/main/ Your_branch_name/.*" include="yes"

Regards !
Vinayak.

nirali

Thanks Adam and Vinayak.

1) Adam as you said, user_list and branch_list is old format. But will this old coding still work with new format in ts6.7.1 sp1 ?

2) In workflow manual of ts6.7.1sp1, I still see some coding with user_list and branch_list is some examples. Are they still using this format with newer formats ?

3) Vinayak, capital dir is located as iw-home/local/config/wft/capital - There is no default folder.

Thanks

Pawan

3) Vinayak, capital dir is located as iw-home/local/config/wft/capital - There is no default folder.

In your case, the Capital folder is at the right location, it should be under the /wft folder.

Adam Stoller

Thanks Adam and Vinayak.

1) Adam as you said, user_list and branch_list is old format. But will this old coding still work with new format in ts6.7.1 sp1 ?

2) In workflow manual of ts6.7.1sp1, I still see some coding with user_list and branch_list is some examples. Are they still using this format with newer formats ?

What page of the manual are you looking at - I just searched through ts_671sp1_wfdev_v01_en.pdf and found no hits for branch_list or user_list - though I do see mention of command_list - which I believe is in error (contact IWOV Support - ask them to verify, and if it is in error - ask them to open a documentation bug report on it)

I do not believe the old format will work - at least not in conjunction with the new format (two different DTDs) - instead you should just look to convert your existing available_templates.cfg file to the new format and stop trying to coerce it into using the old format (you don't lose any functionality, in fact you gain some) and in most cases, I believe the configuration file is cleaner and easier to read.

Adam Stoller

For Point 1: No need to include the "allowed" tag if not required.
For Point 2: Yes ! you can use "name" attribute instead of "value" attribute. It can be ok to use either ways.
For Point 3: Here your "Capital" dir should be located under the >> iw-home/local/config/wft/default/ folder only
For Point 4: you can refer branch value as:
branch value="/default/main/ Your_branch_name/.*" include="yes"

nirali

Yesterday night I downloaded workflow 6.7.1 sp1 documentation from the support site and today I cant find it there.

Anyways, Adam, the command_list that I am talking about is in two examples in documentation of workflow manual.

If this command_list is an old format(6.7.0), then this is the format used in available_templates.cfg I am looking at. When I click on "about" tab on CCPro, info I get is "TeamSite6.7.1 SP1". So its 6.7.1.

How can this 6.7.0 format work with newer version of 6.7.1 SP1 ? And yeah, this coding in older format(6.7.0) is working fine with 6.7.1 SP1.

Pls explain.

Adam Stoller

Yesterday night I downloaded workflow 6.7.1 sp1 documentation from the support site and today I cant find it there.

Anyways, Adam, the command_list that I am talking about is in two examples in documentation of workflow manual.

If this command_list is an old format(6.7.0), then this is the format used in available_templates.cfg I am looking at. When I click on "about" tab on CCPro, info I get is "TeamSite6.7.1 SP1". So its 6.7.1.

How can this 6.7.0 format work with newer version of 6.7.1 SP1 ? And yeah, this coding in older format(6.7.0) is working fine with 6.7.1 SP1.

Pls explain.

My feeling is that it's a bug in the documentation (command_list) and that Interwoven may have provided backwards-compatibility, but how far and whether it works in mixed-mode is anyone's guess (unless you have access to the actual code).

If you don't want to "fix" your configuration file to conform to the latest DTD - open a case with Support - give them all the information that's been provided here - and when they give you an official answer, post it here.

nirali

Thanks.

Your answers help big time.