Have you set the generated pdf as output variable?

Check your component.xml file, compare with adobe document for component creation.  You might be missing in the section in which jar need to include in component.xml file   Include the jar in your DSC and reference it in the classpath node in the component.xml file.

So when you are creating the jar file, open the jar file and check if the jar file contains the required jar's needed for your app. As you are saying that, its working in your local system, so the issue is only with the same jar is not getting exported with the jar you are creating for the server or...

Are you parsing the json data received from SOAP UI? It will not be set directly to variable in the workbench. You need to use an Execute Script activity or another supported mechanism to parse the JSON string and set the data to your workbench variable in the process.  

Have a look at this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/get-runmodes-value-in-client-side-js/m-p/326526  

Thanks Rahul, Yes, its a UI issue, by Try clicking on the empty space after "literal value" the options are coming.

When referencing a subprocess from the main process in AEM Workbench, the Input tab in the process properties only shows an option to pass a literal value. The option to pass a variable is not appearing. Has anyone else encountered this issue? Workbench Version: 6.5.0

Try to set the top/bottom margin to 0.   Or the one workaround could be set the bottom border of the cell to "None"

For custom components, you need to write the code in Java and then need to write your class and operation detail in component.xml. Then need to create a jar file and install it on the server,   then you can use that custom component in your process. Search for document service component in Adobe Lc ...

Share your form at vkatoch07@gmail.com, I'll have a look.   One approach is bind the image fields with the images you want and then show/hide the image fields based on your conditions.