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

Multiple component DCT design issue

motlnt

Hi,
I need some suggestions/comments on one of the scenarios we are trying to sort out.
Env: TS 6.7.2 on RH Linux

Basically we have the main homepage which consists of multiple components(aspx/html files) which are included in it.
Each of this components(aspx/html files) has an individual DCT for them in Teamsite.
We maintain a separate folder for the generated files(ASPXs/HTMLs) from each of this component DCTs and the homepage DCT for each individual HomePage.
The component DCTs and Main HomePage DCT are in 'templatedata' folder as separate data types.

We also have a master folder created for HomePage which has generated files and which user can just copy and build new HomePages from.
Each generated file in the Master HomePage folder is associated to respective master DCRs in templatedata folder.

Here is where the problem starts.As per the requirement , in order for users not to accidentally update the master DCRs we want generated files of the copied folder (from master folder) to not to link to master DCRs.

One of the solution we thought is to create a workflow which will,
a) when invoked ask user for new HomePage name
b) create respective new DCRs for each component as a copy of master DCR
3) auto-generate output files from each component DCR into a new folder named as the HomePage name provided by user.

I cant really think of any other idea fro this.

any other approaches/suggestions/solutions?

thx in advance.

Find more posts tagged with

Comments

motlnt

anyone with any thoughts /comments on this.
looking for some best practice scenario here.

Samir_Friend

I couldn't make out your problem/scenario from the above explanation.

Maybe you'd need to re-phrase it?

motlnt

ok...in simpler words...

The issue we have is with users updating content. We identified a risk where users could mistakenly update the master template and we want to reduce the risk of error as much as possible.

The plan is to create a "Create New Study" workflow where a researcher would go to generate the new study.

The form would have fields for study name, year, etc. Once the user completes' the form and submits it, the workflow generates all of the associated data files and html content and puts it into the appropriate folder structure.

The user is then directed to the new study where they can edit the pages and update content. When the new study is created any links to the master template are broken and recreated using the new files.
We don't need to worry about referential integrity of any kind and simply want a snapshot of the master template at any given time.

If you have suggestions on a different/better/faster way of doing this we welcome your suggestions.

nipper

OK, sounds easy enough. Have an admin template accessible to only certain people. Maybe with fixed variables (i.e. I can change this field only once - then it is readonly). Probably disable save as so people cannot copy the master DCR.

The WF or TPL goes ahead and generates the environment (other required files), sets EAs, etc.

Not too difficult.

It does sound like a reasonable approach. You could also do it with a custom menu item, CGI & IPL, though I like the DCT approach better.