Contains multiple Smart Services and Functions for interacting with PDF Documents.
Smart Services:
Functions:
v2.2.1 Update
Share:
Hello
FillPDF doesnt support Unicode Arabic .
Thanks
Hello,
We received the following error trying to deploy the latest version of PDFTools in Appian 18.2. Any help is appreciated.
12:56:32,037 INFO [stdout] (Appian Plugin Hot Deploy) 2018-08-02 12:56:32,037 [Appian Plugin Hot Deploy] INFO com.appiancorp.process.admin.LoadACSchemas - Attempted to skip registration of [com.appiancorp.ps.pdftools.MergePDF] as it is current [2.1.0], but the ActivityClassSchema was not registered, so re-registering
12:56:32,063 INFO [stdout] (Appian Plugin Hot Deploy) 2018-08-02 12:56:32,063 [Appian Plugin Hot Deploy] INFO com.appiancorp.process.admin.LoadACSchemas - Attempted to skip registration of [com.appiancorp.ps.pdftools.ExtractPDFPages] as it is current [2.1.0], but the ActivityClassSchema was not registered, so re-registering
12:56:32,089 INFO [stdout] (Appian Plugin Hot Deploy) 2018-08-02 12:56:32,089 [Appian Plugin Hot Deploy] ERROR com.atlassian.plugin.manager.DefaultPluginManager - There was an error loading the descriptor 'Fill PDF' of plugin 'pdftools'. Disabling.
12:56:32,093 INFO [stdout] (Appian Plugin Hot Deploy) com.atlassian.plugin.PluginException: com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException: com.appiancorp.process.admin.IncompatibleSmartServiceRegistrationException: The Smart Service Module was invalid: Illegal attempt to change the data type for smart service pdftools.FillPDF, input or output named PdfFields (APNX-1-4104-005)
Hi timothym906 , the issue may be environment-specific. However, please see if this KB article helps: community.appian.com/.../kb-1097-illegal-attempt-to-change-the-data-type-for-smart-service-x-x-x-input-or-output-named-name-error-thrown-during-plugin-deployment.
Additionally, you may want to post in Discussions as your question will have the most visibility there!
Hi , We are facing issue with the plugin after upgrade to 18.3. Is this not supported ?
Hi Team,
We're getting issues with the Plugin. The error is:
bundleName for SmartServiceException, builder.smartServiceClass=class
com.appiancorp.ps.pdftools.AbstractPDFDocumentGeneration
The platform version is 18.2. Let us know what would fix this, coz it's affecting also production apps that uses this.
Hi, we're facing the same error on version 18.3:
bundleName for SmartServiceException, builder.smartServiceClass=class com.appiancorp.ps.pdftools.AbstractPDFDocumentGeneration
Any updates on this yet?
@janv - could you please paste the entire error message and stack trace?
Could you also provide the following information?
- when is the error happening? During deployment of the plugin? During execution?
- what is the language and locale of the appian instance running the plugin?
Error Occuing when converting PDF to JPG in 18.4 Appian - Error as follows:
could you please paste the entire error message and stack trace? It was the entire error message. I don't have access to the stack trace.
- when is the error happening? During deployment of the plugin? During execution? During execution of the merge pdf action.
- what is the language and locale of the appian instance running the plugin? English
@janv - I would like to reproduce this error locally so I can take a deeper look. Is it possible for you to share with me the different PDFs that you are trying to merge together?
You can send them directly to my email address at sylvain.furt@appian.com
Hello Sylvain,
We are facing the same issue in our 18.2 :
Any help would be appreciated.
I also have the same issue in 18.4 when using the Convert PDF to Image smart service.
MatD61 , can you check the application logs and see if there are more details? Also, is the pauseonerror flag set to true or false? If its true can you change it to false and then see if you get more error details either in process or in logs? Like Sylvain Furt asked in earlier comments please share all the details either with me (rahul.patil@appian.com) or with Sylvain, so we can try to reproduce this issue in-house.
I am assuming you are already using the latest version of the plug-in, if not please update the latest and give it a try.