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

Where's the XML that an .XSL mail template is transforming?

Bjorn

Disclaimer: I've never really worked with workflow prior to the current project we're on. So any Idiot's Guide or For Dummies answers are ok.

Anyways, I found it easy enough to put together my own workflow using WFM, building my own datasources, etc. Pretty cool. Not perfect, but pretty cool, especially since I'm a Java guy, so it makes sense to me.

For one of my reviewer tasks, I've built my own transformation (based on an existing one in /iwadmin/main/config/WORKAREA/shared/workflow/email/samples) to build out the reviewer email notification. Again, easy enough, especially since I didn't have to start from scratch.

But my question is...(drumroll)...how can I look at the XML that these files are actually transforming?

The reason I ask is that when I see an element such as...

<xsl:value-of select="//Job/CurrentTask/Owner/@id"/&gt;

...I want to look at the XML so I can see what an "Owner" element (or any other element actually) really looks like and what other attributes it might have. This isn't something that I can clearly discern from any user guides or documentation, at least at first glance. I think it's something I'd know by understanding how it all works together...which I don't.

Any hints?

Find more posts tagged with

Comments

ISCBorisB

Disclaimer: I've never really worked with workflow prior to the current project we're on. So any Idiot's Guide or For Dummies answers are ok.

Anyways, I found it easy enough to put together my own workflow using WFM, building my own datasources, etc. Pretty cool. Not perfect, but pretty cool, especially since I'm a Java guy, so it makes sense to me.

For one of my reviewer tasks, I've built my own transformation (based on an existing one in /iwadmin/main/config/WORKAREA/shared/workflow/email/samples) to build out the reviewer email notification. Again, easy enough, especially since I didn't have to start from scratch.

But my question is...(drumroll)...how can I look at the XML that these files are actually transforming?

The reason I ask is that when I see an element such as...
<xsl:value-of select="//Job/CurrentTask/Owner/@id"/&gt;
...I want to look at the XML so I can see what an "Owner" element (or any other element actually) really looks like and what other attributes it might have. This isn't something that I can clearly discern from any user guides or documentation, at least at first glance. I think it's something I'd know by understanding how it all works together...which I don't.

Any hints?

Look at [thread=28341]this[/thread], thread, it *may* help.
Note that it's usually a good idea to inclde Platform/Version Info in your Post

Bjorn

Look at [thread=28341]this[/thread], thread, it *may* help.
Note that it's usually a good idea to inclde Platform/Version Info in your Post

Usually a good idea or always a good idea? Smiley Wink

This is 6.7.2 SP1 on a Win2k3 box using the latest WFM.

I checked that thread and it didn't offer up any more info. Thanks.

Bjorn

This helped me out...

http://devnet.interwoven.com/forums_vb/showthread.php?t=27368&forumid=16&highlight=xslt+email

CRB

i had to go thru similar situation beforeand since the email template is just some xsl code (PT) parsing some xml data (similar to DCR). i just used xsl to print out everything the xml file had and i saved it to a file. i still have that file somewhere. it looks like you already got what you wanted, if you havent, let me know and i will share the xsl code or the xml file with you.

mdang

Yes the mentioned thread has the answer.
However, I would like to stress my point here too.

The XML data is currently constructed in memory from the specified Java class. That is just an OOTB reference implementation. You are free to define your own XML data scheme (usually by using CSSDK API) to couple with your XSLT.

--Michael

Bjorn

Yes the mentioned thread has the answer.
However, I would like to stress my point here too.

The XML data is currently constructed in memory from the specified Java class. That is just an OOTB reference implementation. You are free to define your own XML data scheme (usually by using CSSDK API) to couple with your XSLT.

--Michael

Yes - point taken and I do think this is powerful, as discussed in that other thread. But it's easier time-wise to use the existing class(es) than create a new one, especially given that all the info we need (in this case, the user "display name") was already supplied by the existing class.

Also, for what it's worth, those classes seem less like a ref. impl. than a piece of provided functionality because while they may have helped you find errors in your "specification", I think they could do a better job of helping others implement their own versions. Part of that is probably me being lazy, but I think there's still some validity to that point.