somewhere in the client lib the javascript code is giving you the error. The best way is to comment few lines of code at a time and load the rule editor till you narrow down the culprit line in the javascript

which clientlib are you using?

looks like this has to do with the client library associated with StoreAndFetch use case. The javascript code in the client library could be missing a semi colon. For the StoreAndFetch use case, you do not need to use the rule editor.

I typically recreate the datasource with the same name in the configMgr on the other instance, and from my author instance create a package to include the AF, FDM, and the  data source under /conf/global/settings/cloudconfigs/fdm and then deploy the package on the instance you want to

I think you should be able to upload xdp files having spaces in their names into AEM. Then render these XDP in HTML5 formatI just tried with a "test space in name.xdp" 

I have had the same issue when I  was submitting to the REST endpoint on my tomcat server.Please follow this document which tells you how to enable submission of attachments enable multipart form data submission to tomcat, please add the following attribute to the context element of the <tomcatInsta...

I do not think you can do that. if you want to merge  Adaptive Form data with your existing xdp template you can do one of the two thingsCreate your Adaptive Form and base it on your XDP template(depending on the size of your xdp template this could cause performance issues)Create XSD schema use it ...

have you looked at the link provided by Kosta?

 

So if you are having a problem in 6.4 version, Please log a support ticket. The following code is working fine in 6.5 environmentfunction getUserMetaData() {//Commented lines below provide an overview on how to set user metadata in map and return it.var payloadPath = workItem.getWorkflowData().getPa...