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

manish_rathi

"unlock" workflow is entered in available_templates.cfg 3 times for different branches and users.

Some users are registered having access to all tghe branches.

For one entry, the access is granted to branches as "/finance/Accounts" and in other entry access is granted to branches as "/finance/accounts/receivables"

So the users who have been registered for both these entries, what restrictions will apply on them ? Will they have access only to receivables or will they have access to all the branches under Accounts which includes receivables ?

Find more posts tagged with

Comments

chitresh

"unlock" workflow is entered in available_templates.cfg 3 times for different branches and users.

Some users are registered having access to all tghe branches.

For one entry, the access is granted to branches as "/finance/Accounts" and in other entry access is granted to branches as "/finance/accounts/receivables"

So the users who have been registered for both these entries, what restrictions will apply on them ? Will they have access only to receivables or will they have access to all the branches under Accounts which includes receivables ?

I guess the users will have access to all the branches under Accounts.

Baracus

For one entry, the access is granted to branches as "/finance/Accounts" and in other entry access is granted to branches as "/finance/accounts/receivables"

So the users who have been registered for both these entries, what restrictions will apply on them ? Will they have access only to receivables or will they have access to all the branches under Accounts which includes receivables ?

Assuming the user has access to all workflows, the main entry (finance/Accounts) will be available to all children branches, such as receivables. If you have a second workflow with the same name that is available within the child branch (finance/Accounts/receivables), it will be used when called/triggered from the child branch.

For example:
[html]

[/html]
If you are in the accounts branch, or any child other than receivables, you will get unlock1.wft... if you are triggering the workflow from the receivables branch, you will get unlock2.wft. Either way, you can use multiple WFTs with the same name and path, just use your branch list to control where the workflow is being triggered, as well as user/role lists if you need to restrict access.

I hope that helps clear things up...