Dynamic Document Generator

Hi Ilan,

Would like to mention that we have encountered the below error while re-deploying the plugin to version 1.7.5 in one of the environments.

We had saved XSLParameter CDT initially. Then to upgrade the plugin, i tried to redeploy the same but got the error as mentioned below.

Hence, have deleted the CDT from Appian Designer and tried to redeploy the plugin. It seems like the old version of CDT still exists in the environment and is not allowing to deploy the plugin.

Please let us know if you have the resolution.

2019-12-01 15:22:01,697 [ajp-nio-8009-exec-4] INFO  com.appiancorp.plugins.AppianPluginManager - Updating plugin 'DynamicDocumentGen:1.7.5 There was a problem loading the module descriptor: TextDocFromXslt.<br/>com.appiancorp.suiteapi.type.exceptions.InvalidTypeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: Unsupported type [Lcom.appiancorp.ps.xmlfo.types.XslParameter; (APNX-1-4047-000)' to 'DynamicDocumentGen'
2019-12-01 15:22:01,902 [ajp-nio-8009-exec-4] ERROR com.appiancorp.type.config.plugin.PojoDatatypesConfig - The data type [uuid={urn:appian:ps:dynamicdocgen}XslParameter] in plug-in [key=DynamicDocumentGen, module=XslParameter] was not imported because it or another data type in the plug-in module was already present on the system with a different structure, and the version number of this plug-in is not greater than the deployed plug-in that last updated this data type. You must increment the plug-in version number in the appian-plugin.xml file and deploy this plug-in again. If the problem persists after incrementing the version number, check that all data type precedents of the data type are declared in the same plug-in module or are listed before this data type in the appian-plug.xml. (APNX-1-4165-004)
2019-12-01 15:22:01,922 [ajp-nio-8009-exec-4] INFO  com.appiancorp.process.admin.LoadACSchemas - Attempted to skip registration of [com.appiancorp.ps.xmlfo.ss.PdfFromDocx3] as it is current [1.7.5], but the ActivityClassSchema was not registered, so re-registering
2019-12-01 15:22:01,958 [ajp-nio-8009-exec-4] INFO  com.appiancorp.process.admin.LoadACSchemas - Attempted to skip registration of [com.appiancorp.ps.xmlfo.ss.DocxFromXhtmlWithStyling] as it is current [1.7.5], but the ActivityClassSchema was not registered, so re-registering
2019-12-01 15:22:01,987 [ajp-nio-8009-exec-4] INFO  com.appiancorp.process.admin.LoadACSchemas - Attempted to skip registration of [com.appiancorp.ps.xmlfo.ss.DocxMergeWithSeparator] as it is current [1.7.5], but the ActivityClassSchema was not registered, so re-registering
2019-12-01 15:22:02,016 [ajp-nio-8009-exec-4] ERROR com.atlassian.plugin.manager.DefaultPluginManager - There was an error loading the descriptor 'TextDocFromXslt' of plugin 'DynamicDocumentGen'. Disabling.
com.atlassian.plugin.PluginException: com.appiancorp.suiteapi.type.exceptions.InvalidTypeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: Unsupported type [Lcom.appiancorp.ps.xmlfo.types.XslParameter; (APNX-1-4047-000)

Hey Illan, your post was probably the most helpful among anything else I found on the web. So thanks for that! I do have one question though: Do you know a way to insert a page break into docx so that the first element on the new page is a Heading1 element? The problems I've encountered so far is that if I wrap a page break around <p> tags, the first line of the new page is empty. And if I put in multiple classes inside a <p> tag, only the first class renders. Let me know if you know of any workarounds!

Sorry - Community apparently doesn't auto-notify about replies here, so I never saw your followup questions

The plugin does not do anything special to handle fonts. It uses the Apache FOP classes to initiate the parsing and transformation. Please look at the class XmlFoConverter inside the plugin for more details. 

I would suggest to do some research on how to handle fonts with Apache FOP transformation and either update the XSLT stylesheet or update the plugin code.

It appears that it was an issue with the plugin framework, not the plugin itself. Our engineering department released a hotfix to address this.

Please create a support case to request the latest hotfix to be installed.

 .... any suggestions? 

Cloud vs On-premise?

Dev/Test/Production?

Version of the plugin?