Maximo Open Forum

Hi Folks,

Using Maximo 7.6.1.3, we currently we have an Automation Script that is tied to the COMMLOG.MESSAGE attribute which updates a placeholder (#TEXTHERE#) in the Message Body of the CommLog with a table of child records associated to an SR. This works flawlessly when the Communication Log is invoked via the user in the UI.

In configuring and testing a Workflow which is looking to leverage this same template, I'm hoping to tie this same script via a separate launchpoint to catch the emails that are being sent as part of our Workflow Task Node Notification that come from WFNOTIFICATION object. There MESSAGE is a non-persistent field, and my initial attempts to catch this with an OBJECT INIT script have been unsuccessful.

Just checking to see if anyone else has done this before? Or if I should be looking at an alternative approach?

Cheers,

Hi Matt,

Did you try with attribute launchpoint with 'Action' event?

Thanks!

Hi Folks,

Using Maximo 7.6.1.3, we currently we have an Automation Script that is tied to the COMMLOG.MESSAGE attribute which updates a placeholder (#TEXTHERE#) in the Message Body of the CommLog with a table of child records associated to an SR. This works flawlessly when the Communication Log is invoked via the user in the UI.

In configuring and testing a Workflow which is looking to leverage this same template, I'm hoping to tie this same script via a separate launchpoint to catch the emails that are being sent as part of our Workflow Task Node Notification that come from WFNOTIFICATION object. There MESSAGE is a non-persistent field, and my initial attempts to catch this with an OBJECT INIT script have been unsuccessful.

Just checking to see if anyone else has done this before? Or if I should be looking at an alternative approach?

Cheers,

Hi Sankar, 

Thank you for the reply. This is how I'm setting it on the COMMLOG.MESSAGE script, but I have not had success on the WFNOTIFICATION.MESSAGE attribute with the same type of event. On WFNOTIFICATION, MESSAGE is non-persistent with an associated class (psdi.workflow.FldNotifyText) which I believe is conflicting with my attempt to intercept the body of the email. 

Hi Matt,

Did you try with attribute launchpoint with 'Action' event?

Thanks!

Hi Folks,

Using Maximo 7.6.1.3, we currently we have an Automation Script that is tied to the COMMLOG.MESSAGE attribute which updates a placeholder (#TEXTHERE#) in the Message Body of the CommLog with a table of child records associated to an SR. This works flawlessly when the Communication Log is invoked via the user in the UI.

In configuring and testing a Workflow which is looking to leverage this same template, I'm hoping to tie this same script via a separate launchpoint to catch the emails that are being sent as part of our Workflow Task Node Notification that come from WFNOTIFICATION object. There MESSAGE is a non-persistent field, and my initial attempts to catch this with an OBJECT INIT script have been unsuccessful.

Just checking to see if anyone else has done this before? Or if I should be looking at an alternative approach?

Cheers,