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

Workarea constraints

chandrachv

this is my problem, i have three workareas in my branch

they are......
news,
articles,
Common.

but deployments to the production servers to be allowed only from Common workarea and from the rest it should throw an error or it should be invisible

and all the files submitted to staging from the news and articles should reflect in the common workarea. therefore files should only be deployed from the common workarea

how do i set constraints to my available_templates.cfg as per above req

Find more posts tagged with

Comments

Pawan

The purpose of available_templates.cfg is to allow/restrict workflows to start from a path and allow/restrict users for a particular workflow.
The scenario you just described cannot be achieved by available_templates.cfg, you have to use this logic in your workflow.

chandrachv

yes pavan u are right, but i just had to set the path of the workarea in the branchlist element in available_templates.cfg
and it is solved

thank you.