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

Initial directory for generate

iwovGraduate

When you hit generate from a DCT, the file dialog always point to the root of the workarea. There needs to be a way to specify an initial directory other than the root of the workarea so users don't have navigate to the right place each time.

Is there a solution to this ? (other than autogenerate via externaltask)
Is there a FR# for this ?

TS 6.1 SP1

Edited by iwovGraduate on 08/12/04 10:02 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

I'm pretty sure there's a FR# for this - as it's been asked for so many times in the past (everyone assumes that the validation-regex is used to set the directory path, and when it doesn't they become confused). I don't recall the FR# though, perhaps Lissa or someone else can track it down.

My way of getting around this is to never allow users to create DCRs or generate pages outside the context of a workflow and then to handle all of that stuff programmatically so that they *can't* do it "wrong".

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

iwovGraduate

Would be good if somebody can get me a FR# and what is the status of it. Is this feature scheduled for release anytime soon ? If not, I would be very curious to know why.

I recall customers wanting this for about 4 years now. And this shouldn't be difficult to implement - afterall you can specify initial directory for things like <browser> tag.

Workflows are a great way to avoid this lacking feature, however not everybody wants to go that route. Over here, the issue is not that they accidently create files in the wrong place, but the fact that they can have to navigate to the right sub-directory everytime they generate a page.

Migrateduser

OK, I did a search on Templating feature requests with the word Generate.

I'm pretty sure you want the first or second FR, but I included the others for reference....

32166 - open
default/allowed directory should then be the root of the generate webpage chooser window.

30530 - open
In the generate page window, depending on the catagory/data type, users would like to have default values show in the field to where the output file should be generated. Client would like the ability to set default locations for templates and have that show on the generate page window.

But there are other related FRs:
42510 - open -
In the templating process, you can save the DCR by clicking save button. Using FormAPI, it is possible to assign DCR name.

Now, in the same process, when you click generate button, the GUI prompts you to enter name of the file to be generated. How, using FormAPI, can you assign same name to generated HTML file as DCR name?

32991 - open
Customer would like the "Generate" function to detect the current working directory and use that as the default when saving generated pages.

32162 - open
would like to request the ability to set a default name (and/or location) for a generated file...

the specific relevance is that 99% of the time our users are working with new DCRs, so they do "New Data Record" to pull up the DCT, enter the information, then click the "Generate" button...it prompts them for a filename for saving the DCR, then immediately prompts them for a filename for the generated page...the naming convention here (and probably numerous other places) is to use the same name for the generated page as for the DCR, so it's rather redundant...

lissa

iwovGraduate

Thanks Lissa,
I will contact support and add a few to the list.

ReggieRWalker

Was this feature ever added?

Adam Stoller

Was this feature ever added?

There were several features requested - the FormAPI feature was added (Read the FormAPI Developer's Guide for more details) - but, at least IMO, the "best practice" is to do the templating development within the context of a workflow

By driving the entire process through the workflow - you control the process and automate the naming and directory placement of DCRs and generated pages and let the content contributor focus on what they're supposed to - the content.By taking care of the pre-creation of the DCR based on information retrieved through the workflow - you take care of the naming and location of the DCR, and then also the naming and location of the generated output which can utilize the FormAPI features.