@DavidZhang  You need to make sure all related artifacts are pushed to the production set-up including the custom fonts (if used) or any custom components used in dev.  Error logs may also indicate the missing artifacts.

@g12  RTE feature is provided by default for the RTE enabled form fields and provides a basic set of features provided as default at [0] so don't think there is emoji support in RTE with AEM Forms OOTB. However with AEM core components, RTE functionalities are made available via a series of plug-ins...

@scottpico  Please raise a ticket with support for further investigation.

@UserSD  Don't recall if this feature used to work with JEE as well but we can make changes to a Designer template from Workbench application. You need to make the changes in the template and upload the updated one on the OSGi instance.

@shirshak  Any recent changes on the system? Is this LC designer or the latest AEM Forms Designer? Please share any error msg or log except.  If this issue is specific to the forms webservices call and NOT an issue with WSDLConnection soapAddress(?) then you can check the network logs?

@aemuser001  I have reviewed the logs shared and could see the posted error msgs[0]. These two tables: DATASTORE_DATA and DATASTORE_META contains information for a blobId reference so you can restore the database state to check if the issue is resolved.    I recall now, we have had a similar discuss...

@Kasen23 @Arthur-Nicholas  Please check the Acrobat Pro version users have on their system? We have recently got reports of this issue from multiple customers and found that they were using an older version of the software while the same form worked at our end with the latest. Please DM the link to ...

@JiriLio  You can save output task attachments using a path relative to the payload or in a variable of an array of document data types. More info - https://experienceleague.adobe.com/docs/experience-manager-65/forms/workflows/aem-forms-workflow-step-reference.html?lang=en#assign-task-step    What v...

@aemuser001  Thanks for sharing the ticket#. I will review the error logs shared.

Haven't tried deploying the configuration changes as such, but it seems the properties were present in the repo but not published for this fragment.  BTW, how are you making the configuration changes to a fragment?