force page regeneration without prompting?

My goal is to not prompt the user AND to regenerate the file.
This does assume that we are working on a DCR with a generated file that does exist.

The user should click "Next/Finish" and workflow should kickoff. I would like the regenerated file and the DCR to move into workflow.

I've got the following to suppres the prompt to regnerate the file when a user clicks next:

IWEventRegistry.addFormHandler("onClose", noRegen);

Is there an easy way to also have the file regenerate?

Thanks,
Steve

Find more posts tagged with

Comments

gzevin

Is there an easy way to also have the file regenerate?

yes. iwregen in the context of an external task

Adam Stoller

My goal is to not prompt the user AND to regenerate the file.
This does assume that we are working on a DCR with a generated file that does exist.

The user should click "Next/Finish" and workflow should kickoff. I would like the regenerated file and the DCR to move into workflow.

I've got the following to suppres the prompt to regnerate the file when a user clicks next:

IWEventRegistry.addFormHandler("onClose", noRegen);

Is there an easy way to also have the file regenerate?

Thanks,
Steve

I think you're confusing 'regenerate' and 'generate'.

Regenerate applies to the pre-existing generated file, in which the extended attributes are examined in order to determine the DCR and PT for the already identified output file.

Generate applies to a DCR, for which a PT and output file must be selected/determined.

Since you're starting from an editing session of a DCR - you're looking for automated page generation, not regeneration.

If you follow best practices for simple implementations (1 output page per DCR) in which you have a 1:1 relationship between the directory path relative to the

data/

directory (for the DCR) and the directory path relative to the top of the workarea (for the output file) - and - a 1:1 relationship between the name of the DCR (e.g.: mumble.dcr) and the name of the output file (e.g.: mumble.html) - and have only a single PT (or a fairly simple mapping of PT to relative directory path) - then it should be easy to work this automation in either direction.

If you don't follow such best practices, or you have a more complex implementation (multiple pages generated from some DCRs and/or multiple PTs that are not logically determined) - then you have much more work to tackle.

Assuming the best practice / simple implementation - you can handle the page generation from either the templating side (FormAPI / callServer) or the workflow side (as already mentioned in one response). Generally, I'd tend to opt for a more controlled environment and do the latter (and completely remove all references to Generate and Regenerate from the TS UI) but there are cases where going the FormAPI / callServer route make sense too. That's your call.

Mr_Cruise

Automatically generating content is a real issue with TeamSite. The business do not care what is generated they just want to update their content. I wrote a module that is configured with an xml file. In that file you define the DCR to TPL relationship and most importantly where the content should be generated. If you are working on a large scale implementation then you need something like this.

If you do not have the time then create all the content (DCRs), generate the content (HTMLs) and use FromAPI to automatically regenerate the content when the DCRs are updated.

Adam Stoller

Automatically generating content is a real issue with TeamSite. The business do not care what is generated they just want to update their content. I wrote a module that is configured with an xml file. In that file you define the DCR to TPL relationship and most importantly where the content should be generated. If you are working on a large scale implementation then you need something like this.

If you map the filenames and directories to each other and only have single-page-per-DCR - you don't need an external mapping file - it's all very simple logic for automation.

If you generate multiple pages from a single DCR then you may need additional means of tracking the association between DCR / PT / generated pages - and an external configuration file such as you suggest, or extended attributes (as I've done in the past) tend to work just fine.

Mr_Cruise

I forgot to mention that the mapping is based on regex, so mapping allows you to generate content of a particular type into a particular directory. Below is an exaple mapping file :-

Adam Stoller

For those who are curious (reformatted to show code)

I forgot to mention that the mapping is based on regex, so mapping allows you to generate content of a particular type into a particular directory. Below is an exaple mapping file :-

<config>
<host name="server">
<branch name="/default/main">
<dcrmapping version="1.0">

<match name="Framework" vpath="templatedata/content/area">
<presentation alias="1" filter="1" type="directory" value="area.tpl" extension=".jsp" prefix="" postfix="" directory="vm/clients/jsp" hierarchy="true" generate="1">
</presentation>
</match>
<match name="Framework1" vpath="templatedata/content/handset">
<presentation alias="1" filter="1" type="directory" value="morePictures.tpl" extension=".html" prefix="" postfix="" directory="vm/clients/handset" hierarchy="true" generate="1">

<match name="Framework8" vpath="templatedata/content/phoneabroad">
<presentation alias="1" filter="1" type="specific" value="payg_countries.tpl" extension=".jsp" prefix="" postfix="" dest="vm/clients/jsp/phoneabroad/payg_countries" hierarchy="true" generate="1">
</presentation>
<presentation alias="1" filter="1" type="specific" value="payg_regions.tpl" extension=".jsp" prefix="" postfix="" dest="vm/clients/jsp/phoneabroad/payg_regions" hierarchy="true" generate="1">
</presentation>
<presentation alias="1" filter="1" type="specific" value="pm_countries.tpl" extension=".jsp" prefix="" postfix="" dest="vm/clients/jsp/phoneabroad/pm_countries" hierarchy="true" generate="1">
</presentation>
<presentation alias="1" filter="1" type="specific" value="pm_regions.tpl" extension=".jsp" prefix="" postfix="" dest="vm/clients/jsp/phoneabroad/pm_regions" hierarchy="true" generate="1">
</presentation>