Hello All,
We have developed a custom application on agentry and running on SMP 2.3.
We are using session.getSessionData().getBytes() to recieve the External Data type field value passed in the transaction as shown below.
session.getSessionData().getBytes("transaction.Body.Data");
http://help.sap.com/saphelp_smp305sdk/helpdata/en/3a/74a0f56de3101489a092e765c09ffa/content.htm?
frameset=/en/3a/74db566de3101499f5b7884d2c59f2/frameset.htm¤t_toc=/en/7c/01cda6700610149b10c2f2a86d335b/plain.htm&node_id=4711
Surprisingly with agentry jar bundled with SMP 3 this value is coming empty.
The encodeImage method does some encoding and compression as required in the backend.
On migrating/implementing the same to SMP 3.0 based agentry application with new agentryv-5.jar, it was observed that it is returning null in the above call.
At the same type we are able to read the data using the getString()method.
http://help.sap.com/saphelp_smp305sdk/helpdata/en/3a/74c5e16de3101481c9d154700e9f67/content.htm?
frameset=/en/3a/74a0f56de3101489a092e765c09ffa/frameset.htm¤t_toc=/en/7c/01cda6700610149b10c2f2a86d335b/plain.htm&node_id=4717
Problem is that earlier with getBytes we were getting image/externalData as array of bytes and formatted or saved. With the string received using getString we are not able to save them, as it is throwing error saying that it is not a valid image.
This is preventing the implementation of attachment functionality of the application. Can you please let us know the modifications done in the library for the picking the attachment values from the transaction.
Please provide a new solution.
Thanks.