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

Email Task not populating Some fields

vijay1240

Recently we migrated from TeamSite6.7.1 to 6.7.2. In 6.7.1 all the workflows used to work fine and send emails with all required fields.

We are using java(CSSDK) and XSLT to send emails.

But after migrating to 6.7.2 some fields are missing in Email for eg:
TaskFiles,JobID, Requested By etc.

Looking for help..

Find more posts tagged with

Comments

Rick Poulin

The OOTB Java email tasks use CSSDK object's toElement() methods to produce the XML data source on which your XSLT is applied. It is possible that this has changed somewhat. I'd suggest you print out the datasource as is in your email, and then you can inspect and tweak your stylesheets as required.

Use something like <xsl:copy-of select="/" /> to print out the XML.

vijay1240

I displayed XML content and found only Target details are getting printed. Current task details are not getting outputted.

Any idea why is this happening.

Rick Poulin

Check the iwui logs (iw-home/local/logs/iwui/stdout.log) for error messages? Grasping at straws here, because if there was an unhandled exception, it would probably not send the email at all...

Send details of the task properties for your email and target tasks.

vijay1240

In the java code they are using
Element currentTaskElement = currentTask.toElement();

where currentTask is CSTask Object.

This is working fine in 6.7.1 version but not working in TeamSite 6.7.2 version

Any turnaround for this.

Adam Stoller

In the java code they are using
Element currentTaskElement = currentTask.toElement();

where currentTask is CSTask Object.

This is working fine in 6.7.1 version but not working in TeamSite 6.7.2 version

Any turnaround for this.

Is this 6.7.2 or 6.7.2 SPx (what 'x') or 6.7.2 SPx with Patch y (what 'x', what 'y')?

vijay1240

Interwoven TeamSite 6.7.2 Service Pack 2 Patch 10208

Rick Poulin

Define "not working", meaning what exactly does currentElement.toElement() produce? null? empty element?

The only time I've seen this fail for me was when I have an unassigned group task and I call groupTask.toElement()... fails because <no user> can't be resolved as a valid CSUser.

May I suggest writing your own task to XML conversion to convert the information you need and that way you can make sure it doesn't change through product upgrades? If you have loads of time on your hands (ha!) it would be neat to write a generic object to XML converter using reflexion. Smiley Very Happy