Skip to Content
0

Agentry Work Manager 6.4: Duplicate notification items

Apr 18, 2017 at 08:52 AM

44

avatar image

Hi,

I already created an incident for SAP but there may be some workaround to this problem. All the questions about Agentry duplicates I found seem to talk about interrupted transmits and user reexecution but this is not what is happening to me now.

I modified Work Manager 6.4 to allow the work order header notification to be modified, for instance by adding new items with causes. This modification works properly and if the notification was modified the changes are posted during the transmit action.

In the WorkOrderPostLoop (action WorkOrderPost), I added a new subaction step that triggers NotificationPostCurrent for the work order header notification if modified.

So the wrong behaviour comes when I add a component to the parent work order at the same time I modify its notification. Then during the transmit action the component post is executed before my custom notification post which is OK, but when the Java of the Notification Post steplet accesses to the Agentry transaction properties it finds 2 items instead of 1 that I added (the second is an exact duplicate of the first).

Why could this be happening? How could I fix it?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Chung Yu
May 12, 2017 at 02:26 PM
0

Hi Marcal,

I see you have an open incident with one of the Support Engineer. Please continue working with Support Engineer to resolve the issue.

Regards,

Chung

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks for the notification, I'm not directly linked to the incident so I was not aware of the update.

0