@aravindS , please log a support ticket with details to sort this out. 

@pratikba , Which organisation are you part of? Is your Org an existing Adobe customer? You cannot simply have a trial version of AEM Forms Cloud Service product. 

@aravindS , You can use these APIs in cloud service as well. The SDK you are using currently is for 6.5 and hence, the issue. Please use the SDK at https://mvnrepository.com/artifact/com.adobe.aem/aem-forms-sdk-api. Use the correct version aligned with the version of Forms present on your cloud inst...

Hi @aravindS ,  What you are using is the AEM Forms SDK version of 6.5 but compiling and using the code on AEM Forms Cloud Service instance. This is incorrect and will never work. Interactive Communications on 6.5 is not available in the same form in AEM Forms CS. We have just released in early acce...

Hi @Yaswanth_ReddyBh ,  What is the software being used for this conversion? Are you using AEM Forms product for this conversion? Or are you using Acrobat PDF Services APIs? Or automation written on top of Acrobat?  My guess is you are using Acrobat PDF Services APIs. You have posted this question o...

Please use following dependency for SDK. You are using aemfd client sdk dependencies from both 6.5 and 6.5 LTS branches which is not correct. If you are on 6.5 SP23, you should use the corresponding SDK.  <dependency> <groupId>com.adobe.aemfd</groupId> <artifactId>aemfd-client-sdk</artifactI...

Hi @aravindS ,  Please follow article in conjuction with article for configuring the post process for an IC and invoke it when Submit button is pressed in agent UI. If you are facing any further issues, please log a support ticket with compelete details

@aravindS ,  Did this resolve your issue?

@aravindS ,  I would request you to share more details or better open a support case with all the details. It is difficult to provide any further inputs without additonal information.  cc: @Khushwant_Singh 

Hi @aravindS ,  Have you filled all the required fields? I hope you have not marked any field editable by agent, then marked it as required and disabled it for editing by agent. In this case, there is a bug where the field's required status is not removed once it is marked non-editable by agent? Als...