Picture attachments not downloading stuck in Queue

[Former Member]

Hi All,

I'm currently setting up Work Manager 6.4 at my client and I had issues with the attached documents download functionality. After I did all the config that was required I'm now able to download documents but when I try and download a picture it goes and fetches the picture, but it stays in the queue it never gets delivered to the device.

Is there any config that I'm missing?

Kind Regards,

CJ Bester

[Former Member]

Another strange thing I have just noticed. If I download the image attachment first and then download a document when the document gets pushed to the device the image attachment gets send as well and shows as on device but, when I look at the object on the Test client the object is empty see image attached.

[Former Member]

Also when I run the Outbound Trigger Retry Utility Program, I get the following Printout

14.12.2017 10:01:39***==>Outbound Trigger Processor Execute Started... 14.12.2017 10:01:39->Info: MOBILE_APP is set to Z_WSEAM_MAINT_WS 14.12.2017 10:01:39->Info: Single Instance Id is set to /SYCLO/CL_CORE_OTRIG_PROCESSOR 14.12.2017 10:01:39->Info: Check whether there is already an instance running. 14.12.2017 10:01:39->Info: Determine outbound triggers to be processed... 14.12.2017 10:01:39->Info: BAdI /SYCLO/CORE_OTRIG_PROC_BADI is enabled. Calling BAdI... 14.12.2017 10:01:39->Info: Number of outbound triggers found after BAdI /SYCLO/CORE_OTRIG_PROC_BADI 6 14.12.2017 10:01:39->Info: Check outbound trigger queue entries against retry setting... 14.12.2017 10:01:39->Error: Invalid OTRIG_ID for outbound message 1EE09A9156041ED7B8948D6E28DA4438 14.12.2017 10:01:39->Error: Invalid OTRIG_ID for outbound message 1EE09A9156041ED7B89496957A390430 14.12.2017 10:01:39->Error: Invalid OTRIG_ID for outbound message 1EE09A9156041ED7B8949C0E5B52042F 14.12.2017 10:01:39->Info: Process outbound triggers... 14.12.2017 10:01:39->Info: Processing Push Outbound Trigger queue entries... 14.12.2017 10:01:39->Info: BAdI is enabled for outbound trigger processing. Calling BAdI... 14.12.2017 10:01:39***==>/SYCLO/CL_CORE_OTRIG_STD_PUSH~EXEC_HTTP_TRIGGER started...

The 1st error is for the Image and the other 2 is for the documents but the documents gets delivered to the device.

Regards,

CJ Bester

[Former Member]

Hello,

Just to clarify, the attached document itself is physically on the client device correct? You can locate it using a file explorer? Regarding the invalid ID, please review the SAP Note -

2013399 - DocumentPushRequest Steplet Invalid Push Scenario ID :

http://service.sap.com/sap/support/notes/2013399

[Former Member]

Hi Cole,

Yes the document is physically in the folder that I have specified and I can open it from within the app or by going to the directory and accessing the document directly. I have also Maintained all the values as requested in the SAP Note but the Error still persist.

Regards,
CJ Bester