DCR tag conversion to &lt; &gt;

Environment:

TeamSite 6.5 SP1
Windows 2003 EE

Problem:

I'm using the custom xml type in order to create form-generated Interwoven DCRs that can be validated against a custom XML DTD. The DTD includes <![CDATA[...]] tags that I'm hoping to incorporate within the DCR in one way or another. Currently, I make an onSave FormAPI call to append these tags to the corresponding field values. This appears to be fine when viewing the DCR through the form - however, when I look at the DCR itself, TeamSite has replaced the <, > tags with <, $gt;, respectively. My DCRs will be directly interpreted by a Flash parser, which cannot convert these back as an XML parser would. Since the DCRs will be interpreted directly, the solution can't involve a PT.

Any thoughts on how I can work around this?

Below are snippets of the DTD and resultant DCR...

Thanks,
Derek

DTD
====================
<category id="c1">
<display><![CDATA[Category One]]></display>
<question id="q1">
<display><![CDATA[Question One]]></display>
<answer><![CDATA[Foo Bar]]></answer>
</question>

</category>

DCR
====================
<category id="c1">
<display><![CDATA[Category One]]></display>
<question id="q1">
<display><![CDATA[Question One]]></display>
<answer><![CDATA[Foo Bar]]></answer>
</question>
</category>

Edited by djhalliday on 09/27/05 05:16 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Well, I'm not sure but what if you were to have a workflow run on tt_data (FINISH) and an externaltask parses your attached file, which is your recently modified / created DCR?

It's somewhat of a Rube Goldberg, but I am a fan of workflow!

Current Environments:
(1,2) TS 6.5 on W2K3
(3) Vignette V7 Portal on Solaris 9

cliffhanger

I find dave's solution to be a decent one.
But if you want to avoid having the users going through an extra step, perhaps on "onSaveDone" or "onClose" you could call a script on the server side that'd read this DCR and translate the &lt &gt tags back to < and > respectively.

Disclaimer: Just throwing my idea, never played around with anything like this, so not sure if there's any issue with making a server call on onClose

Migrateduser

I agree with your caution, but there's no extra step for the user, really. It's extra work for the developer(s), true, but a workflow would be kicked off which could consist of as few as one task and this task parses and saves the file back to its original location (being careful to put back any extattr's, if necessary).

Current Environments:
(1,2) TS 6.5 on W2K3
(3) Vignette V7 Portal on Solaris 9

djhalliday

I ended up using cliffhanger's suggestion - an 'onClose' formAPI event handler calls a server-side perl script that parses the file and replaces offending characters. This seems to work as expected. Thanks, cliffhanger.

If anyone is interested in this solution, a helpful variable to pass to the perl script was IWDatacapture.getDCRPath();.

jbonifaci

A better solution might be to do it onSaveValid with FormAPI, rather than doing a callServer. It should perform much better and be one less script to maintain.

~Jeff