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

workflow access

nirali

Following is the available_templates.cfg I am looking at.

[html]

[/html]

As per this code, does it mean that user has to be from the specified list, specified branch and has to use specific command in order to use this wf.
If its so, then what does the second line in command_list,
[html][/html] is needed for ?

Pls explain.

Find more posts tagged with

Comments

Jcse

Following is the available_templates.cfg I am looking at.

[html]

[/html]

As per this code, does it mean that user has to be from the specified list, specified branch and has to use specific command in order to use this wf.
If its so, then what does the second line in command_list,
[html][/html] is needed for ?

Pls explain.

Hi
Workflow commands are specified by the command element. The command element specifies the user-activity that starts the corresponding workflow. For example, the following configuration:
[HTML][/HTML]
specifies that the associated workflow is started when performing a Submit and that it cannot be invoked by other means.

whereas the configuration

[HTML][/HTML]

I don't know the actual behavior,but when i try this in my available_templates.cfg then in the list of workflows shown for selection my wft under which i have used this is not coming, and it was still not coming even when i tried, I am using 6.7.1 SP1

[HTML][/HTML]

Well,one thing to ask which TS version you are using ?
As my available_templates.cfg does not look like this it is something like

[HTML]

[/HTML]

Adam Stoller

Following is the available_templates.cfg I am looking at.
[...]
If its so, then what does the second line in command_list,
[html][/html] is needed for ?

Pls explain.

I am assuming that you are on a version of TeamSite earlier than 6.7.1 (which is why Jcse's config file looks different).

What you are seeing is either a mistake, or a temporary change that someone forgot to undo when they were done testing something.

If I recall correctly - if you don't have any command_list section - it is the same as having a command_list section with the above statement in it. I.e.: the workflow is available for all commands. With that in mind, having the above be explicitly stated is fine, but then it makes no sense having the line that preceded it which declared a specific command for which it was available.

So - it's up to you as to how you want to "fix" it - either change "yes" to "no" in the above (leaving the workflow only available for the submit command) - or leave the above line in and remove the explicit enablement of all commands - or figure out what commands (plural) that it should be available for, list them explicitly, and change the above line's "yes" to "no".

Only you can know what is correct for your environment specific for this particular workflow.