How to get Workbench response in Adaptive Forms | Community
Skip to main content
S
srujan1981
March 1, 2021
Solved

How to get Workbench response in Adaptive Forms

  • March 1, 2021
  • 2 replies
  • 1140 views

Hello - is there any way to get AEM Forms workbench response in Adaptive Forms? I can able to invoke the workbench SOAP service but not sure how to catch the response in Adaptive Forms?

 

Please help me on this.

 

Regards,

Srujan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kosta_Prokopiu1

Workbench is a Java based (Eclipse) development tool. You cannot integrate this with adaptive forms. The SOAP communication is between the server and the client to upload,version and deploy assets and processes. I have never seen someone to attempt that. The SOAP communication is not documented. 

2 replies

Kosta_Prokopiu1
Adobe Employee
Kosta_Prokopiu1Adobe EmployeeAccepted solution
Adobe Employee
March 2, 2021

Workbench is a Java based (Eclipse) development tool. You cannot integrate this with adaptive forms. The SOAP communication is between the server and the client to upload,version and deploy assets and processes. I have never seen someone to attempt that. The SOAP communication is not documented. 

    F
    FrustratedFootballer
    September 29, 2022

    Our adaptive forms consume REST endpoints to interact with the Workbench processes. It works, but I think we can do better.

      W
      Adobe Employee
      workflowuserAdobe Employee
      Adobe Employee
      September 29, 2022

      What is the use case?

        F
        FrustratedFootballer
        September 29, 2022

        We have an Adaptive Forms application that consumes REST endpoints exposed by workbench processes to perform CRUD operations on a SQL Server database via Workbench processes. This endpoint consumption is triggered by javascript code in the out-of-the-box adaptive form action listeners that make the call via XMLHttpRequest, so user interaction is required. What we would like is a more seamless interaction.

          Terms & ConditionsAccessibility statement

          Loading footer...