SAP Work Manager - Push is replacing order while user is processing and some pending transactions are lost

[Marçal_Oliveras]

Hi,

I have work order push and "background send" enabled for Work Manager. When user is processing the order using the iPad client, the work order is marked "to be pushed" in the backend if at least one transaction is posted. Then after a while, it is pushed to the device replacing the current work order.

In certain cases, the user has executed some changes in the Agentry client work order that are not yet posted to SAP, the order is replaced by the backend pushed data and the pending transaction changes are lost. By certain cases I basically mean temporarily lost of connection or when push of work order goes faster than posting the pending changes via background send.

How can I avoid this behaviour? I don't want the order to be replaced if the object (or any child) has pending transactions linked.

[bill_froelich]

Marcal,

I guess I don't understand why you are pushing the work order back to the device.  If the user is making the changes to the workorder locally, why do you need to have SAP update the workorder on the device again from the backend.  It should be the same already.

Also, by default Work Manger does not generate transactions for changes to the work order until the user clicks the transmit button.  This is due to the way the transactions are bundled together.  Unless you have modified the process, enabling background sending won't typically cause anything to happen with most of the updates.

--Bill

[Marçal_Oliveras]

Hi Bill,

I'm talking about operation change of status, which is background send enabled in the standard.

And then, we are pushing WO, because in case of any change done from the backend we need to have the work order updated in the device. The change of status from the mobile device, includes change of operation text which then can trigger the push.