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

Setup question

System

I am re-evaluating the branch and workarea structure we have and have a question about visibility. Do users (editors or authors) in CCSTD typically see the datacapture.cfg file and the tpl files? Seems strange that they can see them since they don't have any real interaction. Or is there something about our setup that I don't have configured correctly?

Find more posts tagged with

Comments

reddyl

I am re-evaluating the branch and workarea structure we have and have a question about visibility. Do users (editors or authors) in CCSTD typically see the datacapture.cfg file and the tpl files? Seems strange that they can see them since they don't have any real interaction. Or is there something about our setup that I don't have configured correctly?

Usally editory or authors are the users that create DCR's generate output files etc, they should have read permission to to datacapture.cfg file and read & execute permission for tpl's.

Migrateduser

That I agree with, it's just that my users are Sales and Marketing types and the cleaner and less cluttered the better. There just doesn't seem to be any reasone that they actuall need to see datacapture.cfg and other configuration files in CCSTD. They should be invisible for users who are logged in as author, editor, and perhaps even admin. In my case, I'm the only one who works on creating datacapture.cfg files and no-one else has any need to see them in their workareas.

Not sure if I am making sense.

Adam Stoller

You asked if you were missing something - I think the answer is no.

The users need read access to the datacapture.cfg file in order to render the DCRs in the DCT form.

The users need at least read access (possibly execute) to the PTs because they will be using those to generated pages from the DCRs created from the DCT forms.

TeamSite *could* do some fancy manipulations to hide these files from users logged in as authors or editors - but it doesn't.

The other alternative is that you address the creation of DCRs through a workflow driven process such that the users never need to know anything about the templatedata directory structure - it takes a lot of design, implementation, and user-training - but it can be worth the effort depending on the organization's needs.