iwwf.dtd and workflow template

I was going through workflow template example. According to iwwf.dtd specifications workflow template starts from tag, while in the example workflow template starts from

Simple Workflow Template File
The following is a fragment from a simple workflow template file that fills in blank fields
(indicated by __TAG__ directives) with HTML-encoded CGI data.

-----------------------------------------------------------------------
<[! CDATA
TAG_info(
description => "",
job_name => "",
);
]]>

owner="__TAG__('iw_areaowner');"
description="__TAG__('description');">
-------------------------------------------------------------------------

Pls explain,
thanks

Find more posts tagged with

Comments

sumitk

The WFT file always starts with workflow tag and is always validated against DTD. If you want to embed perl code in your WFT / display user input screen, you need to include it in tag.

kalpana

thanks Sumit.
Your answer confirms my understanding. I did read that after posting on forum but still was in doubt. Your snswer helps remove that doubt.

Adam Stoller

For those following along from home - here's the original post in a slightly less cryptic format:

I was going through workflow template example. According to iwwf.dtd specifications workflow template starts from <workflow> tag, while in the example workflow template starts from <template_script> tag. So is this valid according to the specifications ? Why iwwf.dtd does not specify about the <template_script> tag and why does not dtd document start from <template_script> tag ? I am copying parts of example here.

Simple Workflow Template File
The following is a fragment from a simple workflow template file that fills in blank fields
(indicated by __TAG__ directives) with HTML-encoded CGI data.

[html]-----------------------------------------------------------------------
<[! CDATA
TAG_info(
description => "",
job_name => "",
);
]]>

owner="__TAG__('iw_areaowner');"
description="__TAG__('description');">
-------------------------------------------------------------------------[/html]

Pls explain,
thanks

The confusion is, I believe, because the XML of the WFT is pre-processed by the system to produce a job specification XML file - the WFT itself is not 100% XML compliant, but the job specification produced from it - is.
If you look at several of the solutions WFTs you'll notice a complete lack of the workflow tag - because the entire workflow template is generated in an object-oriented manner using TeamSite::WFconstructor all within the template_script section - but again, the end result is a job specification file which is XML compliant and does begin / end with a 'workflow' tag.

kalpana

How did you make sure that all the tags appear on the screen ? I write the message and browser is taking away all tags. Can you pls explain ghoti ?

ISCBorisB

How did you make sure that all the tags appear on the screen ? I write the message and browser is taking away all tags. Can you pls explain ghoti ?

vBulletin Tagging and Samples

Test-BhumiU.rptdesign