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

Generate page in specific Directory

carlo30lo

Hi,

I'd like to develop a simple template that should be used from a large number of authors but how can I perform the following scenario:

- user A can generate page only in /Branch/WORKAREA/folder A
- user B can generate page only in /Branch/WORKAREA/folder B

without define userA and userB in tempate.cfg file?

Thanks
Carlo

Find more posts tagged with

Comments

Adam Stoller

Hi,

I'd like to develop a simple template that should be used from a large number of authors but how can I perform the following scenario:

- user A can generate page only in /Branch/WORKAREA/folder A
- user B can generate page only in /Branch/WORKAREA/folder B

without define userA and userB in tempate.cfg file?

Thanks
Carlo

My stock answer - remove Generate options from the UI and control page generation via workflow.

You might be able to put controls in the PT itself - but I think that's a bit late in the process.

ravio

I'd like to develop a simple template that should be used from a large number of authors but how can I perform the following scenario:

- user A can generate page only in /Branch/WORKAREA/folder A
- user B can generate page only in /Branch/WORKAREA/folder B

without define userA and userB in tempate.cfg file?

I too suggest you leave the generation process to workflow as Adam suggested earlier on.
[left][/left]
However depending on your requirements if you *have to* do it this way,
Generate the file name by whatever logic you have, if user entered you will need a field in your DCT for it.

var fName = foo;
if (IWDatacapture.getUser() == 'userA'){
IWPageGeneration.setOutputFile ("/Branch/WORKAREA/folder A/" + fName);
}
if (IWDatacapture.getUser() == 'userB'){
IWPageGeneration.setOutputFile ("/Branch/WORKAREA/folder B/" + fName);
}

And yes, disable the buttons for users either through templating.cfg or write an onSave button handler function to virtually inactivate them.(you will find this covered in the manual)