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

Get generated file name from FormAPI

Tim__D

I need find out the name of the output filename ie. /products/index.jsp from within formAPI. Is there a way to do this?

Find more posts tagged with

Comments

Adam Stoller

FormAPI operates at the DCT level.
Output pages (such as index.jsp) happen when you are processing a DCR (derived from a DCT) by a PT.
So - unless you've included the intended output file name as a field within the form, are using one or more fields within the form to determine the output filename, or are attaching an EA to a DCR and are editing an existing DCR from which you could extract that information ... I'm not sure that there's anyway to do what you are asking (I'm not sure it even makes sense?).

Can you provide a more detailed use-case scenario for what you are trying to accomplish?

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

Tim__D

The full file path to the file is a key piece of data that I am using for a component template used in all my PT's for this site. The file path is used to establish the context of the page within the site then then reders the nav etc. When I preview the pages the file name changes and the context is lost. For previewing I need another way to get the actual filename not the temprary one created by TS.

Adam Stoller

If you can derive the output file name and path from the file name and path of the DCR - you can do it - there's a hack solution for getting the DCR path in 5.5.2 FormAPI:var vpath = parent.gDCRVPath;and another hack for 6.0 / 6.1 FormAPI:var vpath = parent.datacapture.getDCRVPath();and finally in 6.5 there's a supported FormAPI call you can use:var vpath = IWDatacapture.getDCRPath();

Again - this is for getting the path to the DCR - not the generated file.

If you control your environment such that you use sub-directories under the data/ directory that correspond to top-level directories at the workarea root and also correspond to top-level directories at the docroot on your web server -- and base the output filename on the name of the DCR - you can derive the name of the output name.

E.g., If your DCR path is something like: /..../templatedata/General/Article/data/news/events/2004/coolstuff
then your output file might be: /..../news/events/2004/coolstuff.html
It's therefore a trivial task to take the DCR path - strip out the "/templatedata/General/Article/data" string and append ".html" to the end.

If you don't have a consistant naming scheme like this, it's pretty difficult (if not impossible) to derive the name of the output file based solely on information available via the DCT/DCR.

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

Tim__D

This is a self serve site so its likely that a formal structure may not be observed. What I may do is create a preview.tpl and provide a self referencing value in the dct if they wish to use the preview feature rather then clicking on the file to preview in the branch to preview. Thanks