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_template.cfg | workflow access restriction on directory

rohitspathak123

Hi,

I want to use available_template.cfg to retrict the access of workflow to directory level (not just Branch level).

I have a category called "MYTEST" under 'templatedata'. I want that my workflow should be avaliable only when a user has seleted any file under "templatedata/MYTEST"

1. Can I use "branch" tag for this . I tries something but it not working.
2. Does "branch" tag just works for TeamSite Branch restrictions. Can I extend it to "directory" level ?
3. I know that I can put such restrictions in my workflow using some CGI task etc.

Please let me know if this is possible using available_template.cfg ?

~ R

Find more posts tagged with

Comments

Adam Stoller

Hi,

I want to use available_template.cfg to retrict the access of workflow to directory level (not just Branch level).

I have a category called "MYTEST" under 'templatedata'. I want that my workflow should be avaliable only when a user has seleted any file under "templatedata/MYTEST"

1. Can I use "branch" tag for this . I tries something but it not working.
2. Does "branch" tag just works for TeamSite Branch restrictions. Can I extend it to "directory" level ?
3. I know that I can put such restrictions in my workflow using some CGI task etc.

Please let me know if this is possible using available_template.cfg ?

~ R

For pre-671 versions of TeamSite - for 'new_job', 'submit', and possibly 'assign' workflows - yes, you can go down to the directory level;
for 'tt_data' workflows you cannot go beyond the branch level.

For 671+ versions of TeamSite it might be different as there were modifications made to the DTD for available_templates.cfg (mostly for the benefit of WFM) which might allow you to specify the vpath down to the directory level even for tt_data workflows.

Jcse

Hi,

I want to use available_template.cfg to retrict the access of workflow to directory level (not just Branch level).

I have a category called "MYTEST" under 'templatedata'. I want that my workflow should be avaliable only when a user has seleted any file under "templatedata/MYTEST"

1. Can I use "branch" tag for this . I tries something but it not working.
2. Does "branch" tag just works for TeamSite Branch restrictions. Can I extend it to "directory" level ?
3. I know that I can put such restrictions in my workflow using some CGI task etc.

Please let me know if this is possible using available_template.cfg ?

~ R

Hi

In case of WFM we can do this just by changing the code as

[HTML]

[/HTML]

Now this WFM will only be accesible when user will submitt/assign/new an file from this DataType under this Category.

Something should also be present in available_template.cfg for WFT.

Jcse

Hi

If you check DTD of available_templates.cfg,we have an element "vpath-regex".
Use this element under the "and" element as i have mentioned in my earlier post.

HTH

Adam Stoller

Hi

If you check DTD of available_templates.cfg,we have an element "vpath-regex".
Use this element under the "and" element as i have mentioned in my earlier post.

HTH

I believe the question is with regard to tt_data - the command used by FormsPublisher to initiate workflows. Thus the question is whether tt_data provides the full vpath to be checked against the vpath-regex or whether it just provides the branch path (as it did in earlier versions of TS).

Jcse

I believe the question is with regard to tt_data - the command used by FormsPublisher to initiate workflows. Thus the question is whether tt_data provides the full vpath to be checked against the vpath-regex or whether it just provides the branch path (as it did in earlier versions of TS).

That may be, but my reply was in the concern of

I want to use available_template.cfg to retrict the access of workflow to directory level (not just Branch level).

I have a category called "MYTEST" under 'templatedata'. I want that my workflow should be avaliable only when a user has seleted any file under "templatedata/MYTEST"

VisibilityBasedOnDataSetSize.rptdesign

Adam Stoller

That may be, but my reply was in the concern of

Point taken - I read it differently, but on re-reading it - the vpath-regex should certainly work.

RajatChopra

Having read replies on this thread, and testing tt_data, I found that it doesn't work with complete vpaths.

Is there a suggestion or design alternative to not show options that are not relevant for a particular content type?

Thanks,
Rajat