PDF Tools

I am getting the following error when trying to import PDF Tools in our environment: 

HTTP Code: 500
APNX-1-4198-019

An Error Has Occurred
Expression evaluation error [evaluation ID = BO9U41F6] : An error occurred while executing a save: java.util.UnknownFormatConversionException: Conversion = 'D'

When we look into the stdout.log file, the following additional information is available:

2021-02-22 03:41:31,222 [ajp-nio-0.0.0.0-8009-exec-1130] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to enable Plug-in 'PDF Tools' (pdftools) version 2.2.10: 'The Function Module com.appiancorp.ps.pdftools.PDFToolsFunctions could not be installed due to invalid type: Invalid Type: Unsupported type com.appiancorp.ps.pdftools.types.PdfMetadata. Use the @Type annotation to indicate the type of a function parameter. The deprecated ’type’ attribute for the @Parameter annotation has been removed. (APNX-1-4104-008)'

Any idea what this issue is referring to?  Thanks.

Hi.

I am trying to use Create PDF Smart service and need help with filling PDFContent data, 

Is there an example that I can follow?

Thank you.

Hi, i'm using the following code while using this service but it's giving me this error in the process model node Create PDF

ERROR DETAILS: An error occurred in executing an Activity Class.

please note that the expression is working fine in the expression rules

{
  'type!{urn:appian:ps:pdftools}PdfContent'(
    page: 1,
    xPercent: 10,
    yPercent: 10,
    angle: 0,
    sections: {
      'type!{urn:appian:ps:pdftools}PdfSection'(
        style: null,
        components: {
          'type!{urn:appian:ps:pdftools}PdfText'(
            value: "Some"
          ),
          'type!{urn:appian:ps:pdftools}PdfText'(
            value: "text"
          )
        }
      )
    }
  )
}

Hi Joe,

Having the same issue on 20.4, no previous versions of the plugin were installed before.

Thanks for the help!

Failed to enable Plug-in 'PDF Tools' (pdftools) version 2.2.10: 'There was a problem loading the module descriptor: Fill PDF.<br/>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.FillPDFPauseOnError, input or output named PdfFields (APNX-1-4104-005)'

We are using the Smart Service "PDF from HTML" and facing issue in one of the environment stating:

bundleName for SmartServiceException, builder.smartServiceClass=class com.appiancorp.ps.xmlfo.ss.AbstractDocumentGeneration

It is not happening in lower environment (Dev). Need help

Hey Arun,

The v2.2.10 development was for an unrelated manner, but I'll take a look at this and see if we can publish a new version with a fix for your issue.

Hi Druva Kota /

We are still facing this issue in our environment, Is there any fix recommended?

• Added bookmark extraction, refactored to gradle

Hi Druva Kota,

Yes, the plugin was already available in the environments and we also have working processes using these smart services. We already tried deleting the cdt and the related smart services from the environment, but still we were not able to deploy this plugin. 

We have also raised a support ticket for this issue and they asked us to update the cdt version in the plugin jar file. We tried to update the cdt version as suggested by this KB article, but we were not able to find the @Type annotation in the plugin code also we were unable to find the current version of the CDT.

Would you be able to help us resolve this issue? Please feel free to send us an email if you need any more clarifications.

cc:

Pratiksha, was this plugin previously deployed in your environment? If so, was the cdt "PdfField" every manually modified via XML?

There seems to be a conflict in the cdt version defined in the plugin and in your environment. I would recommend deleting that cdt from your environment, then re-deploying the plugin. See the bullet in the Edit section of the Data Type Plugin documentation, removing the conflicting cdt should allow the plugin to manually recreate a fresh cdt.