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

previous task identification in EmailNotification.xsl file

Faizi

Hi All,

I want to get email notification according to the previous task. I have gone through various thread related to "Wfvarfinishop" variable but i couldn't get solution how to compare this variable using script in next task. And how to check this property in "EmailNotification.xsl".
If i will get value than i can use same "EmailNotification.xsl" for different emails.

I am using WFM 1.0.0.1 and TS 6.7.1 SP1.

Kindly help me.

Thanks in Advance.

Find more posts tagged with

Comments

mdang

I think there is no concept of a single previous task. Multiple tasks can have a single task as the next task. So previous task can be more than one.

The best way to create a reusable (if that is your intent) email notification task is to have it accept a target task name. In your email notification task, it is straightforward to use CSSDK to lookup this target task name and query all properties of the target task, construct your email data xml from the properties, and transform using the email xsl.

This also means in your workflow instantiation time, you would need to supply this target task name to each email task you are creating.

Hope this helps.

Faizi

Thanks for reply.

Is there any way to change the global variable on a task without using perl/java coding and check it in the next task. In my case mail task (url task).

I am trying to use same Task (URLTask) by two different links. But in both case trying to send email in different format.

If it is possible to identify previous task or link on .xsl file then same .xsl file can reuse.

If it is possible to identify some variable on a task then using javascript i can set different .xsl file for the same task. In this case i need two different .xsl file.

mdang

> Is there any way to change the global variable on a task without using perl/java coding and check it in the next task. In my case mail task (url task).

You can use the CLT iwjobvariable to change any job variable which is global to all tasks in the job.

> If it is possible to identify previous task or link on .xsl file then same .xsl file can reuse.

I am not sure if there is a built-in mechanism(xpath locator) in the OOTB WFM url tasks for this, but everything is customizable if you do it your own way. The URL task is basically a java class that implements the CSURLExternalTask interface. And what it does is to collect the job/task information and turn them into a data xml string. Then combine it with the task variable mail_template (.xsl file), the mail content is created and send.

If you go this route, you have total control. You can do many tricks to get the .xsl to identify previous task data. iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom/MailNotificationTask.java has the boilerplate source for this.

> If it is possible to identify some variable on a task then using javascript i can set different .xsl file for the same task. In this case i need two different .xsl file.

Again I am not sure if there is a built-in way already, but you can always do your own.

Faizi

Once again thanks for answer.

You are correct but I am trying to solve using some built-in way.
Would you please let me know how to use “WF Variables Finish Op” and “WF Variables Start Op”. Because when we click on this property in its description show like:

The WF Finish Operation variable defines how Server variables can be set, modified, or deleted on the files contained by the task when the task becomes inactive.

Let I set a variable in “WF Variables Finish Op” property which is “set:var=value” now it’s a task variable or job variable? If it’s a job variable then can I change its value on next task using same way?

Adam Stoller

Would you please let me know how to use “WF Variables Finish Op” and “WF Variables Start Op”. Because when we click on this property in its description show like:

The WF Finish Operation variable defines how Server variables can be set, modified, or deleted on the files contained by the task when the task becomes inactive.

Let I set a variable in “WF Variables Finish Op” property which is “set:var=value” now it’s a task variable or job variable? If it’s a job variable then can I change its value on next task using same way?

It is a WF (workflow a.k.a. job) variable - so you can use it as a sort of global state variable for your workflow and the various automated tasks can reference it and do different things based on its value.

Faizi

It is a WF (workflow a.k.a. job) variable - so you can use it as a sort of global state variable for your workflow and the various automated tasks can reference it and do different things based on its value.

Thanks Ghoti

So, would you make me understand, how can i check it in the next task. i mean like $IW_CV, $IW_SCRIPT etc.

Adam Stoller

Thanks Ghoti

So, would you make me understand, how can i check it in the next task. i mean like $IW_CV, $IW_SCRIPT etc.

You can check it in the next task if the next task is an automated task (externaltask, cgitask, urltask) and you use either the Perl or Java methods for accessing task and job data.
The perl method (of which I am most familiar) is through the use of TeamSite::WFtask and TeamSite::WFworkflow modules - read the perldoc's for them and search the forums and you should find plenty of examples on how to access workflow variables using them.
For the Java variant - you'd have to read the javadocs to find the equivalent methods for accessing such information.

Faizi

Once again thanks Ghoti,

Is it possible to check this variable without using perl/java. I am trying to do it using javascript ($IW_SCRIPT).

Adam Stoller

My original response might have been correct ...
I don't believe Javascript applies here. The question of previous task identification is, I believe, being asked in the context of an instantiated workflow and the Javascript items you were talking about are only present in the workflow model prior to instantiation.

I don't believe there is any way in XSL to reference workflow variables (though perhaps there is through some sort of namespace extension?, I haven't done that much with XSL at this point).

If your use of the XSL is through an externaltask or cgitask then it makes sense to include the access to the job variable in that script prior to invoking the XSL.

As I haven't personally gone through the use of XSL for generating email notifications - and I can only assume you're doing this because you're working with non-OS users (another thing I have not [yet] been involved with) and thus cannot use the Perl iw_solution_email.ipl script instead.

If this is not the case - i.e.: you are not using non-OS users - then I'd recommend switching to externaltasks using iw_solution_email.ipl and putting the code to reference the job variable into the PT used to compose the body of the email.

Faizi

Now lots of things become clear. What are the limits of different type of WF Variables and its usability?

So thanks for your appropriate suggestions.