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

Making Page Generation Optional

i69alot

Hi:

I've created a DCT that will capture data for our commentary pages. For awhile we've been capturing all the data in the form and posting it to our web site as HTML. However, we've added the ability to use the same form to specify a URL to a PDF instead, then just capture essentials about the document (URL, Title, Author, etc.) rather than embedding all the actual content.

It works fine, but on those form entries that utilize PDFs, we no longer need the HTML page to be generated upon clicking Save, Save As, Finish on the form.

Can someone describe how to conditionally generate this HTML page based on the value of one of the form fields (in this case, the PDF text field)?
Thanks!

Find more posts tagged with

Comments

vpatel

Your use case isn't clear but it seems like you'll probably need some FormAPI here.

i69alot

I've attached a screen cap for what the form looks like. If the highlighted field, PDF Path, contains a valid path to a PDF document, fields that normally include content such as Header and Paragraph are no longer required.

If there is no PDF Path value, then the fields mentioned above are required because they will be included in the generated HTML. Normally when clicking Save or Finish or Save As... the page will be generated and stored in the workarea. That is ideal unless there is a PDF link specified. An HTML file will not need to be created. What I'd like to do is conditionally create the page only if there is no valid PDF path. Hope this helps.

Pawan

...It works fine, but on those form entries that utilize PDFs, we no longer need the HTML page to be generated upon clicking Save, Save As, Finish on the form...

Based on what I understood from your questions, If currently the HTML page is generated after clicking the finish button, then its going into a workflow which has a task which is doing the generation. You should check your generation logic.