Maximo

Hi Shane,

I can't think of anything else to check. What exact version of Maximo are you using? Go to Help - System Information and copy all the text there and paste it into a reply to this post. Or better yet, open a Case with Support and ask that it be assigned to me. And include the Sys Info on that Case.

Then we can set up a webex and get logs and all that.

As you are using Maximo you will likely have a support contract allowing you to open Cases. If you are a consultant then your client should have all that and you can open a Case with their customer number.

But send me the Sys Info at least for now. .............dick

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?

Hello,

Are the emails also being sent twice through comm templates or is it just logging twice and sending email once? Can you try to remove wait node and add a task node and accept the assignment through task node and see if you face same issue? you can add status change action on the line going out of task node.

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?

Hello,

Are the emails also being sent twice through comm templates or is it just logging twice and sending email once? Can you try to remove wait node and add a task node and accept the assignment through task node and see if you face same issue? you can add status change action on the line going out of task node.

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?

Hello Everyone,

I also have a similar issue - duplicate communication log entry created on WO when its dispatched. Email also sent twice in my case.

But here we are using a custom workflow on PO (without any wait node) but has a custom class action associated and that is sending email when WO is dispatched.

For most of the WO's its working fine (sending only one email with one communication log entry) but for few of the WO's issue is happening.

As email is being sent from class file, I have also verified the class logic and found that respective methods are triggering only once with no repetition/loop. 

What could be the issue here, is it something related to JVM? Please share your thoughts. Thanks in advance.

Thanks,

Channa

Hello,

Are the emails also being sent twice through comm templates or is it just logging twice and sending email once? Can you try to remove wait node and add a task node and accept the assignment through task node and see if you face same issue? you can add status change action on the line going out of task node.

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?

Hi Channa,

Is there any pattern for which WO's this is happening? Are there any other configurations such as automation scripts invoking similar action? Try to turn on admin mode and test again. If it works then there must be something else as well doing same action.

Hello Everyone,

I also have a similar issue - duplicate communication log entry created on WO when its dispatched. Email also sent twice in my case.

But here we are using a custom workflow on PO (without any wait node) but has a custom class action associated and that is sending email when WO is dispatched.

For most of the WO's its working fine (sending only one email with one communication log entry) but for few of the WO's issue is happening.

As email is being sent from class file, I have also verified the class logic and found that respective methods are triggering only once with no repetition/loop. 

What could be the issue here, is it something related to JVM? Please share your thoughts. Thanks in advance.

Thanks,

Channa

Hello,

Are the emails also being sent twice through comm templates or is it just logging twice and sending email once? Can you try to remove wait node and add a task node and accept the assignment through task node and see if you face same issue? you can add status change action on the line going out of task node.

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?

Hi Suhas,

Thanks for your reply.

i dont see any difference in WO pattern. I have verified other configurations like automation scripts.. etc so same action is not invoked.

Today from logs i found one difference between WO's (success and failed one). The difference is, for WO where email is sent twice, there is one query executing on WO object (log message --> [WARN] [MaxCRON01] [CID-CRON-573985] BMXAA6720W - USER = (MAXADMIN) SPID = (263) app (null) object (WORKORDER) ) which is not triggered/shown up for other WO (where email is sent once).

Seems like some lag/delay in sql execution (BMXAA6720W) might be causing this issue but not very sure.. 

Hi Channa,

Is there any pattern for which WO's this is happening? Are there any other configurations such as automation scripts invoking similar action? Try to turn on admin mode and test again. If it works then there must be something else as well doing same action.

Hello Everyone,

I also have a similar issue - duplicate communication log entry created on WO when its dispatched. Email also sent twice in my case.

But here we are using a custom workflow on PO (without any wait node) but has a custom class action associated and that is sending email when WO is dispatched.

For most of the WO's its working fine (sending only one email with one communication log entry) but for few of the WO's issue is happening.

As email is being sent from class file, I have also verified the class logic and found that respective methods are triggering only once with no repetition/loop. 

What could be the issue here, is it something related to JVM? Please share your thoughts. Thanks in advance.

Thanks,

Channa

Hello,

Are the emails also being sent twice through comm templates or is it just logging twice and sending email once? Can you try to remove wait node and add a task node and accept the assignment through task node and see if you face same issue? you can add status change action on the line going out of task node.

Hi All,

New to Maximo here and attempting to create a workflow on the Work Order table with the intention of firing a Communication Template on each status update of the work order. I have the concept of this working but for some reason I am getting two update entries and I have no idea why (and is probably something simple)!

Workflow:

On the workflow, after the start I have a WAIT node, the event on this wait node is: maximo.workorder.statuschange.* which then moves onto a condition to check the stats not in ('CAN','COMP','CLOSE'). The negative flow here moves to the stop node, the positive flow moves back to the wait condition.

When enabling the logging on the communication template I can see this logged twice when the status is changed - any ideas why? Is there anything I can check?