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

Generate a page and kick off workflow with "Finish" Button

tirrudev

Hi,

I have a requirement:

1.Onclicking of a Finish Button in the DCR--A html page should be generated and that page should be deploying to staging Environment...

For this to be accomplished I need few suggestions:

I did in the following way:

I did hide save,saveas,preview,generate using templating.cfg view options.
and changed the text of Finish as "Save and Deploy"
OnSaveDone--->Handle Generate function which would call a callserver and running iwgen in that...

1.But How Can I kick of a preview here?

But my problem here is:
If I do that I am hardcoding the name of the output html and If I edit html or DCR..It would not say that there is already a html with that name...It Justs overwrites..To see if the html already exists...Do I have to write seperate function to handle this?

Do Every Template need to have a field from which the html name would be set?or what is the better way of handling the names of html?

2.To Intiate a workflow-->I still did not do this need some suggestions..Do I have a diiferent function in OnsaveDone which would call a ipl and in that using iwmodelc.bat -i to initiate a workflow...But How does that workflow know the generate html path?

Are these the better ways to do?

Thanks in Advance

Find more posts tagged with

Comments

Adam Stoller

I think you should reconsider your design and use the tt_data command to initiate a workflow when the DCR is saved / finished - and put all the code for taking care of page generation and deployment into the workflow.

Or am I missing something that requires this complexity you seem to be trying to deal with?

ISCBorisB

Q. How to start Workflow on Finish?
A. Use tt_data Command. I *believe* you already had a thread discussing it. If not - search for tt_data

Q. How to generate HTML on "Finish"...
A. Since you need a workflow anyway, DO NOT use FormAPI, Events and the like. Make generation part of a Workflow,
use External or CGI Tasks to do it and show the result

Q. Do(es) every Template need to have a field from which the html name would be set?
A. In general - no. There are numerous ways to name generated components. Set naming explicitly within DCR itself is just one of them.
If you have one-to-one DCR-HTML relation, naming HTML after a DCR is the common approach. Note that it is also a good practice to introduce
and enforce business-driven DCR naming Convention.

Just my 2 cents

tirrudev

Thanks for the reponses:

I think you should reconsider your design and use the tt_data command to initiate a workflow when the DCR is saved / finished - and put all the code for taking care of page generation and deployment into the workflow.

Or am I missing something that requires this complexity you seem to be trying to deal with?

Yes:This would be fine..So then I have all the functionalities Save,saveas,preview..But I would hide Generate Button...Because Workflow is taking care of the generation, Is that correct and page generation is handled in the workflow..? Let me know If my understanding is wrong?

Thanks in Advance

Adam Stoller

Thanks for the reponses:
I think you should reconsider your design and use the tt_data command to initiate a workflow when the DCR is saved / finished - and put all the code for taking care of page generation and deployment into the workflow.

Or am I missing something that requires this complexity you seem to be trying to deal with?
Yes:This would be fine..So then I have all the functionalities Save,saveas,preview..But I would hide Generate Button...Because Workflow is taking care of the generation, Is that correct and page generation is handled in the workflow..? Let me know If my understanding is wrong?

Thanks in Advance

If you're going to quote someone's message - do so as a "quote" to make it clear.

Personally, I do not like offering "SaveAs" as an option to users - it causes far more problems than it helps (IMO), but yes, there's no reason to offer Generate if that is taken care of by the workflow.
Of course, along with this should be plenty of documentation and at least some amount of user-training...