@Eshwarign  Are you facing issues reading from the excel file or posting the data in the backend servlet? If you could elaborate on the use case. Could you share the error msg that you're seeing?

@crich2784  A specific set of properties can be set as custom properties [0], and I see that you've already set the property to "string." Also, these properties need to be prefixed with workflow.var.* or param.* depending on the use case and should have a default value (if you see an undefined value...

@CR17506599 Thanks for confirming! I see that the fix to the issue is already part of SP13, so seems to be an issue specific to this set-up. Hope /v2 is appended at the end of the OAuth URL. Could you raise a support ticket for further discussion over a call?

@aemuser001 Thanks for getting back. Checking this one further.

@CR17506599  What patch version of AEM Forms you've tested Sign integration with? A similar issue[0] was resolved with AEM Forms 6.5 SP11, so you upgrade the set-up.   [0] - value of access_token_uri is set to nulloauth/refresh and the value of refresh_token_uri is set to nulloauth/token in crx.

@aemuser001  I can replicate the issue in-house. The HTTP button is visible in the output PDF with Forms service invocation irrespective of the presence set for the button while we see the expected output PDF with the Output service. To unblock your work, you can hide or show the button by changing...

@Artem_89  I don't see the forms add-on in the list of installed packages, so did you install the forms add-on earlier(SP9)? You can find the latest forms add-on packages here- https://experienceleague.adobe.com/docs/experience-manager-release-information/aem-release-updates/forms-updates/aem-forms...

@StrawHatM23 The steps provided in the introduction article[0] are short and crisp, so may seem confusing. You can refer to the other help docs on the left panel under "AEM Forms and Adobe Campaign Standard." Also, another article[1] elaborates the steps to integrate AEM with ACS, so you can follow ...

@StrawHatM23 You can get the error logs for the attempt under crx-quickstart\logs\

@StrawHatM23 This is a server-side exception during submission; that's why you see the message “Encountered an internal error while submitting the form” on the browser side. Could you share the detailed error logs to identify the root cause?