Skip to Content
avatar image
Former Member

Attached documents on SMP 3.0/WM 8.0

Document download is not working. We are following the approach explained below:

·        A java Iostream class copies the Attachment to the SMP server from a repository. This part is working fine.

·        A file system management step copies the document from SMP server to device. This part failed. We have verified that the command is running,(the file is getting copied from a location to another on the same server) but not copying the file to the path set in the “File locations” tab of external data property. This failed both from ATE and device. We tested with Windows, iphone and android platforms. Both the above java and agentry steplets are placed inside a transaction.

If any of you worked on this, please help. Screenshots of agentry definitions are attached.

attachment.png (52.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jan 15, 2016 at 01:36 PM

    Hi Anurag,

    Under Windows 9.x/NT/2000/XP section, try using Base Path as C:\Agentry\Attachments\ in place of C:\Agentry\Attachments\test.pdf


    What is target device's Operating System?


    Regards,

    Sahil Dudeja

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 15, 2016 at 02:21 PM

    Anurag,

    As Sahil indicates, the Base Path is the directory / folder location where the attachments will be stored and should not end in a file name.

    Here is how I have my steps configured.

    Object

    Step

    Also, you mentioned that you are trying to do this as part of a transaction.  Normally documents would be downloaded as part of a fetch in the server exchange steps or more likely as an object read step. 

    --Bill

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Bill Froelich

      We had tried both ways: placing it in Work order's read step, and child objects read step. On both occasions the step was running and the command also. But the part of the step that has to copy the document from SMP server to device is failing.

  • Jan 15, 2016 at 03:28 PM

    Anurag,

    Hi. In addition to our community member suggestion above (Thanks Bill and Sahil - we agree to their statement that you need not to put the actual file name), we see an SAP Incident ticket on this currently in our support system. As far as we know, the attach document in Work Manager 8.0 is based on custom (consulting driven design) based on Agentry's File System capability.

    With this said, Work Manager 8.0 does not have attach document out of the box. This may mean that your project already had it pre-designed before by a consulting team (theory). So when you use the File System of Agentry (As defined in the agentry.ini), there is a chance that the Agentry.ini that you are using is an older version and may not be compatible with the SMP 3.0 version. Suggestion here is to recompile the agentry.ini using the newer editor to make sure that the FileSystem connection type is still valid. The guess here is that you may have errors showing up in the logs.

    Again the theory we have here is:

    You are using older Agentry.ini (published in older Eclipse Agentry - designed in pre-SMP 3.0 environment) and using it in SMP 3.0. 

    Another thing we have to say is please communicate with your AE on anything Attach Document with respect to WM 8.0 or higher. This way they can request a feature to be added to the product for your company. This is the best route to get it out of the box.

    Regards,

    SAP Mobile Support Team

    Add comment
    10|10000 characters needed characters exceeded