Meta data changes causing trouble

Aspose.Words Product Family
1

Hi,

We are using Aspose to deal with the RTF documents in our application. When the user signs off a document, we insert an electronic signature at the bottom of the document. The document is then put into an external system for further processing. However the external system is not able to digest the modified document and is giving errors (boxes at some places). The original and modified documents when opened in MS Word or Word pad, open up fine and no differences are observed. Looks like the changes in metadata are causing the issues. Can somebody look into it and let us know what could be the issue? Your help is greatly appreciated. I have attached the original and modified documents for further exploring. The documents with “_New01” in the file name are the modified ones.

Thanks in Advance,

-Eswar.

2

Hi Eswar,

Thanks for your inquiry. Please note that Aspose.Words mimics the same behavior as MS Word does. The output looks good in MS Word.

It would be great if you please share following detail for investigation purposes.

  • Please

create a standalone/runnable simple Java application*
that demonstrates the code (Aspose.Words code) you used to generate
your output document

  • Please share some detail about external system
  • Please share the steps to reproduce the shared issue (boxes at some places) at our end.

As soon as you get these pieces of information to
us we’ll start our investigation into your issue.

3

Hi Tahir,

Thanks for looking into the issue. The information you have asked for is given below.

  1. We have created a stand alone program to demonstrate the way we use to modify the document in our application. I have attached the program here. The main java file in the program is “SignDocument.java”. Please modify the config.properties file to indicate the location at which you place the original documents. The modified documents will be created in a “modified” folder within the folder you place the original documents.

  2. External system is AllScripts E-H-R (AEHR). Code that imports reports is embedded in AEHR code base and our client has no access to it. The issue is reproduced only on the client end. Unfortunately we don’t have the ability to reproduce the issue at our end.

  3. When we used a different mechanism(Jacob – Java COM Bridge) through a different application to insert the signature line, the external system is not throwing any errors. A technical person on the client side compared the documents and thinks that the change in metadata may be causing the issue.If you need a sample of the document modified through the other system that uses Jacob, I can send you one. Please let me know.

Any help in this regard is highly appreciated.

Thanks,

-Eswar.

4

Hi Eswar,

Thanks for your inquiry. We have generated the document using shared code example. The output looks good in MS Word.

We noticed that you are using older version of Aspose.Words for Java. Please use latest version of Aspose.Words for Java 15.10.0 and let us know how it goes on your side. Hope this helps you.

If you still face problem, please share following detail for our reference.

  • The detail of your external system is not clear enough. Please share some detail about external system
  • Please share the steps to reproduce the shared issue (boxes at some places) at our end.
  • Please share the screenshots of problematic sections of output document
5

Hi Tahir,
Thanks for looking into the issue. Can we just download 15.10.0 and replace the existing jar (14.1) with the latest without any issues. Please note that we have used a trial version for the documents that we have given to you as a sample, but we use licensed version in the application? Do we have any financial incurrence to upgrade to 15.10 or can we just down load and replace the old one? Please advise.
Thanks,
-Eswar.

6

Hi Eswar,

Thanks for your inquiry. Please remove reference to old Aspose.Words for Java 14.1.0 from your project, clean the project (any IDE cache etc) and add reference again in your project to the new ‘aspose-words-15.10.0-jdk16.jar’.

Please check the expiration date of your license file. To check an expiration date of your license, open the license file using notepad. You will see the following tags:

20160818

It means that you can free upgrade to version of Aspose.Words published before 08/18/2016.

If your license does not allow you to upgrade to Aspose.Words for Java 15.10.0, you may ask for temporary license from following link.
Get a Temporary License

7

Hi Tahir,
We tried to get some information from the AEHR that the client is using to export our modified documents. They have compared the documents and observed some differences in the meta data between successful and failed documents. Given below are their observations.

  1. TOC Heading;}}{*\datastore … then <13> <28><13> , the bad message has only TOC Heading;}}}|<13> <28><13> , missing the entire datastore section
  2. They find some difference in the OBX5 section as below.
    Error Message:
    {\rtf1\ansi\ansicpg1252\uc0\stshfdbch7\stshfloch7\stshfhich7\stshfbi0\deff7\adeff0

Successful Message:
{\rtf1\adeflang1025\ansi\ansicpg1252\uc1\adeff0\deff0\stshfdbch0\stshfloch31506\stshfhich31506\stshfbi31506\deflang1033\deflangfe1033\themelang1033\themelangfe0\themelangcs0
‘the OBX5 section in the message throwing the error looks suspect. Using an HL7 view, it is very different from the messages that do not have a problem. It’s as though the OBX5 section is being broken apart even further’
Please let me know if the above information from them is helpful. Please advise how we can resolve the issue.
Thanks,
-Eswar.

8

Hi Eswar,

Thanks for sharing the detail. Unfortunately, this does not help us to find the issue which you are facing in your external system. We have tested the scenario using latest version of Aspose.Words for Java 15.12.0 with following code example. We have attached the input and output documents with this post for your kind reference.

Please pass this Out.rtf to your external system and share following detail for our reference.

  • Please share the screenshot of problematic sections (boxes at some places) when you pass output to your external system.
  • Please share the differences in the meta data between attached input and output (Out.rtf) documents.
int paraalign = ParagraphAlignment.RIGHT;
Document signDoc = new Document(MyDir + "124851_TEST_20150302091615810_1.rtf");
DocumentBuilder docBuilder = new DocumentBuilder(signDoc);
docBuilder.moveToDocumentEnd();
Paragraph para = docBuilder.insertParagraph();
para.getParagraphFormat().setAlignment(paraalign);
docBuilder.insertBreak(BreakType.LINE_BREAK);
writeSignName(docBuilder, signDoc, para);
System.out.println("File has been modified");
RtfSaveOptions rtf = new RtfSaveOptions();
rtf.setExportCompactSize(true);
rtf.setExportImagesForOldReaders(false);
signDoc.getRange().replace(ControlChar.NON_BREAKING_SPACE, " ",
false, false);
signDoc.save(MyDir + "Out.rtf", rtf);
9

Hi Tahir,
We tried testing the file in the external system. When they are trying to open the file in the external system, they are getting an “Unexpected end of file” message box and when they say “OK” to that, the file is opening up. They tried to find the differences and they feel that there is some difference in the closing tag that is giving this error. Please see attachments for the error message and difference between a passed and failed closing tags. Please see if this can help in resolving the issue.
Thanks,
-Eswar.

10

Hi Eswar,

Thanks for sharing the detail. We need some more detail for the analysis of this issue.

  1. Please open your input Rtf in MS Word and insert same text with same font formatting at the end of document.
  2. Save the Rtf
  3. Open the Rtf in notepad and remove {*\datastore …} from it.
  4. Pass this modified document to your external system.

Please share your findings from your external system. If you do not face the same issue, please let us know. We will then provide you more information on this. Thanks for your cooperation.

11

Hi Tahir,
Thanks for your reply. We have done as per your suggestion and the RTF file with the {*\datastore …} removed, gives the same error in the external system. It gives an unexpected end of file error and once the “OK” button on it is clicked, it opens in the external system. Looks like the removal “datastore” is the problem here. The “datastore” is not removed when we use “Jacob” jar in a different application and the document modified with that passes successfully through the external system. Is there a way to stop the removal of this “datastore”? Please advise.
Thanks,
-Eswar.

12

Hi Tahir,
Good Morning. Do you have any solution to this issue? Please let us know.
Thanks,
-Eswar.

13

Hi Eswar,

Thanks for your feedback. We have logged a ticket as WORDSNET-13324 in our issue tracking system to preserve {*\datastore …} from input document to output document. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

14

Hi Tahir,
Have you logged the ticket for resolving the above issue? When can we expect a fix? Please let us know.
Thanks,
-Eswar.

15

Hi Eswar,

Thanks for your inquiry. Currently, your issue is pending for analysis. Once our product team completes the analysis of your issue, we will then be able to provide you the ETA of this issue. Our product team will check either this is an issue or not. Once there is any update available on this issue, we will inform you via this forum thread.

Please let us know if you have any more queries.

16

Hi Tahir,
Good Morning. How are you? Do you have any resolution for this issue? Can we have an ETA?
Please advise.

Thanks,
-Eswar.

17

Hi Eswar,

Thanks for your inquiry. We have asked from our product team about the ETA of WORDSNET-13324. As soon as any information is shared by them, we will be more than happy to share that with you.

Thanks for your patience and understanding.

18

Hi Tahir,
Thanks for your reply. I believe the process of fixing an issue is taking too long going through the support forums. Is there a paid support that can be bought to prioritize the issues/requests so that it can be fixed quickly? Please advise. Note that we are licensed users and have recently renewed the license.

Thanks,
-Eswar.

19

Hi Eswar,

Thanks for your inquiry. We understand that this issue is important to you; normally when an issue is reported by a customer via our regular product forums, it is added to the pool of current issues being worked on by our product teams. Our product teams work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers. However, due to the nature of some bugs and the number of features we are working on, this doesn’t always mean we can fix every bug within a short time after it’s reported.

That being said, we fully understand that you are keen to get a fix to your particular issue, please have a look at enhanced support options - e.g. purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of these issues directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.

20

Hi Tahir,
Do we have any resolution to the above issue? Is there any ETL for this? Please note that we may have to look for alternatives in case this doesn’t workout as our vice president is pressing for a resolution. Please advise.
Thanks,
-Eswar.