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

default save location for DCRs

Hans

Does anyone know how to control the default save location for a DCR ?

e.g.
templatedata/category/type/data/news/2005

instead of
templatedata/category/type/data/

We have some formapi that objects if user saves to a different folder but this would be nice.

thanks everyone.

TS 6.1 on Solaris 8

Find more posts tagged with

Comments

Adam Stoller

My standard response - do all DCR creation through workflows rather than via OOTB menus -- have the workflow create the DCR with the right name in the right place and then let the user Edit it [only - disable the Save As feature].

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

saumil

Hi,
You can do using Form-API as well.
Define a field in dcr (textbox), where content author can put dcr name.
Capture onSave()/onSaveValid() Event, write your own method to save dcr (i.e. never asking name to content author), take name from text field and save in your required path.

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

Adam Stoller

The "required path" was part of the issue in the original post - but yes - you could capture that information in the DCT form as well and use it via FormAPI as suggested.

However ... you would also want to use FormAPI to ensure that the field(s) used to define the path/name of the DCR become read-only as soon as a value is found within them (both on init() and onChange) or else you have to deal with the mess of deleting pre-existing versions of the DCR that were in different locations or had different names.

Again - I still think using a workflow to drive the creation of DCRs (and the generation of pages from them) is a much cleaner solution in the long run.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

saumil

Hi,
Yes, onInit() need to check the value and make it read-only.
For existing dcr can write a script that will amend all the dcr with new field and appropriate value (dcr name).

The approach is depend on exact requirement, If architecture is already in place and don't want to change user experience, then form-api can done the trick.

Saumil
BTWholesale | CMS
TS 5.5.2 - Solaris 8.0

timeaggregation.JPG