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

WFM mail_template XSL: Where's the source XML?

LooseCannon

TS 671 SP1 / Linux
WFM 1.0.0.1

I'm looking to extend the reviewerNotification.xsl mail_template that is shipped with TS but do not know what data is available to the XSL.

I looked under /iwadmin/main/workflowModels/WORKAREA/iw-wa/Instance/ModelInstance but to no avail.

Do you know the location of the source XML records that get transformed by the mail_template? I need to look at one to determine if certain data is available to include in an email.

Find more posts tagged with

Comments

brvhrt

TS 671 SP1 / Linux
WFM 1.0.0.1

I'm looking to extend the reviewerNotification.xsl mail_template that is shipped with TS but do not know what data is available to the XSL.

I looked under /iwadmin/main/workflowModels/WORKAREA/iw-wa/Instance/ModelInstance but to no avail.

Do you know the location of the source XML records that get transformed by the mail_template? I need to look at one to determine if certain data is available to include in an email.

the data comes from the java class that handles the email task ...

Adam Stoller

TS 671 SP1 / Linux
WFM 1.0.0.1

I'm looking to extend the reviewerNotification.xsl mail_template that is shipped with TS but do not know what data is available to the XSL.

I looked under /iwadmin/main/workflowModels/WORKAREA/iw-wa/Instance/ModelInstance but to no avail.

Do you know the location of the source XML records that get transformed by the mail_template? I need to look at one to determine if certain data is available to include in an email.

Today's your lucky day ;-) As I happen to be slightly involved with trying to debug issues with the Java mail notification right now, I'll provide the template I'm seeing from taking the sample program MailNotificationClass and making it dump out the XML:[html]

...
...
...
...

...
...

...
...

...

...

...

...
...

<br> <CreationDate class="..." month="..." dayOfMonth="..." dayOfWeek="..." year="..." hour="..." minute="..." second="..." time="...">...</CreationDate><br> <User id="..."/><br> <Message>...</Message><br>
...

[/html]So far, I've noticed that these programs do not seem to include the transition comments in the dump, nor do they allow the use of mail header XSLTs so you have all sorts of replicated code with hard-coded values for each type of email notification -- why they didn't just re-code iw_solution_email.ipl in Java is beyond me - but the folks I'm working with may end up doing that, and then possibly send it over to IWOV so that it can get included in future releases (don't hold me to that, it's just a thought at this point -- also it is possible that IWOV may fix this themselves before we get around to it).

Have fun...

LooseCannon

the data comes from the java class that handles the email task ...

thanks. i see what you mean. the java class creates the xml record on the fly in memory.

LooseCannon

Today's your lucky day ;-) As I happen to be slightly involved with trying to debug issues with the Java mail notification right now, I'll provide the template I'm seeing from taking the sample program MailNotificationClass and making it dump out the XML.

Have fun...

cool! thanks! now i have a better sense of what the java class creates.

time to play Smiley Happy

Adam Stoller

...
So far, I've noticed that these programs do not seem to include the transition comments in the dump...

In further examination, it appears the comments are there - they're just at the top level (//Job/Comments), not at the task level (//Job/Current/Task/Comments) - and the mail template we started from had incorrect accessors anyway.

mdang

The idea of the Workflow Java mail is to provide flexibility and total control to the WF developers. The OOTB example is just a demo.

As the OP concluded, the data XML is generated on the fly in memory. If you review the example Java mail code closely, you can see that you are free to include anything you want in the data XML. You have full access to CSSDK which you can query any workflow data you wish. At the same time, you are free to write your XSLT in anyway you wish according to your defined in-memory data XML.

The proper email template design in my mind is:
1. Write the HTML page that you want your WF email to look like.
2. Take out the data from the HTML and you pretty much have your email XSLT.
3. Whatever data you want to fill in the template, code your Java mail class to get it from CSSDK.

The format and content of the source XML and the template XSLT is totally up to you to define.

--Michael

Adam Stoller

The idea of the Workflow Java mail is to provide flexibility and total control to the WF developers. The OOTB example is just a demo.

As the OP concluded, the data XML is generated on the fly in memory. If you review the example Java mail code closely, you can see that you are free to include anything you want in the data XML. You have full access to CSSDK which you can query any workflow data you wish. At the same time, you are free to write your XSLT in anyway you wish according to your defined in-memory data XML.

The proper email template design in my mind is:
1. Write the HTML page that you want your WF email to look like.
2. Take out the data from the HTML and you pretty much have your email XSLT.
3. Whatever data you want to fill in the template, code your Java mail class to get it from CSSDK.

The format and content of the source XML and the template XSLT is totally up to you to define.

--Michael

That's fine - except for for the following:

flexibility and total control to the WF developers."

mdang

Yes, we are fully aware of the missing getGroup() API of the CSGroupTask. I was the one who filed the internal bug and had been pushing it for the fix. Hope we can fix that asap.

For the other claims, I would really want to understand them. It would be a big surprise for me if you have to resort to iwgetwfobj system call or other means in the Java mail task.

I am looking at this example source file:
iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom/MailNotificationTask.java

the constants section has these


    public static final String MAIL_SUBJECT         = "Sample Task Notification";
    public static final String MAIL_ENCODING        = "UTF-8";
    public static final String MAIL_MIME_TYPE       = "text/html";

    // fill in your mail server host name
    public static final String MAIL_SERVER          = "smtp.corp.com";

    public static final String KEY_MAIL_TEMPLATE    = "mail_template";
    public static final String KEY_TARGET_TASK_NAME = "target_task_name";

    // web host to serve all the stylesheet and images to the HTML email
    public static final String WEB_HOST             = "localhost";

    // print lots of JavaMail mail session debugging info.  Turn this off when
    // email is working properly.
    public static final boolean DEBUG_MAIL_SESSION  = true;

So you can code your business logic to customize the subject line, encoding, html/plaintext, and also the debugging flag. In the following code like the sendMail() method, you can certainly customize your recipient list, from address, cc list, etc.

Maybe the current Java solution did not expose these customizations as config files like the Perl solution mail did. We may want to improve the Java solution in that way, but that doesn't hinder the flexibility of it, I think. Please let me know otherwise. I would like to kill your pain before it becomes mine. Smiley Happy

Also, I hear that we need to improve on the documentation part of the CS APIs.

--Michael

Adam Stoller

Response moved to new thread as I hadn't intended to hijack this thread (sorry)