Skip to Content

Agentry Work Manager - Add Signature as DMS attachment

Hi,

Agentry Work Manager standard is already able to capture a signature but it's stored in a property type "Signature" and then processes in Java, as I could see this field has some metadata and the Java gets the actual signature string by adding ".bmp" to the end of the string to access a property, something like .transaction.signatureField.bmp

But I would like to skip all this and store the signature directly as a new DMS/BDS attachment in the work orders attachment list with the MIME type BMP.

Is this possible? How can I get the data from the Signature type field into a External Data field? Or how can I make that instead of opening a picture/document stored in iPad, the attach document process allows me to enter a signature?

Regards,

Marçal Oliveras

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 16, 2017 at 04:57 AM

    The easiest thing to do would be to modify the java associated with your transaction where you capture the signature to either save it out as a .bmp first and then attach as a new DMS/BDS attachment. Alternatively you can also convert the bmp to a jpg, or other format, and then attach depending on your requirements.

    On the client you do not have access to the signature directly in order to manipulate it before it goes to the server. If you wanted to capture a signature to a file for attaching on the client you will need to create an Open UI control.

    --Bill

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Bill,

      I already thought about modifying the Java, but I would like to have "Inbound Transaction Queue" to be able to ensure that the signature was successfully stored. I see it can become quite complex if I do it at signature level while DMS attachments already have it active for WM 6.4.

      But anyway it may be the only option possible for me since I may not be allowed to use OpenUI since there is not custom client created yet for some internal policy.