Armin Winkler 
Has successfully completed the online course Introduction
Has successfully completed the online course Intermediate (200)
Has successfully completed the online course Advanced (300)
Has successfully completed the online course Basics (100)Hi Robert,
in order for our non-German speaking users to be able to understand, too, I’m going to formulate my reply to your query in English, thank you for your understanding.
If I understand your problem correctly, you have several SQL-based connector calls which provide you with the data to populate the fields inside of a form. Depending on the input of a certain serial number field, you perform a connector call that outputs data which should be saved into a (most likely struct) variable. As soon as you want to run another call which takes the serial number as input to fetch a additional kind of data set which should finally appear in various other form fields, the call is not executed anymore. Is that correct?
While I don’t really understand based on your description, how the following connector calls are not carried out (and I think this circumstance would require a separate, thorough analysis), I would recommend you to restructure your process flow and implement a server-side business object instead of several subsequent connector call activities. Your scenario is a prime example for the usage of a server-side business object indeed, as inside of one of its functions you would be able to combine several connector calls invoked via Javascript (JS) API calls and merge and / or modify the individual results. Finally, you could set your results to predefined output parameters and use them in the output mapping dialog to map values to the existing form fields in your UI. In particular, the problem which you solved via script, which is that SQL connector calls per default output a result set (i.e. an array of objects), can be handled in the JS code of the business object function as well, as you could implement a check on existence of an element inside of the result set of the given connector call (i.e. the array length has to be greater than 0), and then just set the single output element (i.e. index 0 of the array as seems to be the case for your scenario) as value to an output parameter which has a struct data type assigned to it. Please find the documentation for server-sided business objects here. You most likely will need the API documentation as well if you are to execute connectors from inside of your function.
Should you decide to stick with your current process logic implementation which relies on connector call activities solely, please speak with the person responsible for Simplifier in your company and let them create a ticket in our support portal on your behalf asking for further help and error analysis of your application. We would then be able to help you further in the frame of an Enabling session based on a paid contingent from your company.
Good luck adapting your application logic and please let us know whether this helped you.
Kind regards,
Armin
- This reply was modified 3 months ago by Armin Winkler.