on 2021 Mar 03 2:39 PM
Hi Experts,
I have enabled the WO Operation Push in our solution recently (Custom Work Manager 6.5.6). As we use Cloud Platform to host our Agentry App, I followed the Push Configuration guide that further details about what needs to be done for SCP when enabling Push.
I have succeeded in getting the push working to some degree, I can see the Push queue (Under Syclo Admin panel) filling properly when I create and assign a high priority WO and also I can see in the Server logs that the control performs a call to the 'WorkorderPushCallback' service event.
In addition to the above, I have setup a debug point at my Steplet class (This class is mapped for the 'WorkOrdersPushForEvent' Push definition). The control successfully gets to my steplet and then to the Stephandler and then to the PushBapi. In the Push BAPI (as per standard) there is a call to the native parent WO fetch BAPI class to retrieve the Workorders, this is where I have a problem.
I found that the Work Order ET table is empty when WO Fetch class is being called from the Push BAPI class. Because of this the whole Push fails.
I can't find why this happens. Any directions will greatly help.
Thanks in advance
Regards,
Madan KM
We have managed to fix this issue by changing the 'Mobile Data Object Configuration' of the 'SMM3_ISU_WORKORDER_PUSH' in such a way that the filter 'Assignment Type' has been changed to a 'Static Value in Range format' rule type and we selected our assignment type manually from the drop down.
Regards,
Madan KM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
10 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.