• 0 Vote(s) - 0 Average
  • 5
  • 4
  • 3
  • 2
  • 1
Thread Modes

Questionnaire answers splitted into variables
#1
Hello
We want to improve some automations starting from Easyvista service request and then call scripts on Ansible. So,I'm looking for some method for capturing data from questionnaires and use each answer as parameters for external web services or scripts..
As I see, there is not any "tag" for naming each question result as workflow variable..
I've tryed one workflow with one conditional step for each question and capture into one variable every @RESULT... So, I need one conditional step for every question result. When I've 20 or more questions  the workflow is endless, with a lot of conditional chained..

So, there is another way to capture this data and define these "variable" tags for use them as parameters, into notifications, ...?
I'm trying some loop to read the question_result table but I don't see way to define tags

thank you

#2
(12-09-2019, 03:27 AM)egomez Wrote: Hello
We want to improve some automations starting from Easyvista service request and then call scripts on Ansible. So,I'm looking for some method for capturing data from questionnaires and use each answer as parameters for external web services or scripts..
As I see, there is not any "tag" for naming each question result as workflow variable..
I've tryed one workflow with one conditional step for each question and capture into one variable every @RESULT... So, I need one conditional step for every question result. When I've 20 or more questions  the workflow is endless, with a lot of conditional chained..

So, there is another way to capture this data and define these "variable" tags for use them as parameters, into notifications, ...?
I'm trying some loop to read the question_result table but I don't see way to define tags

thank you

Hello,
The simplest solution is to create a SQL View with all question result (and request_id) that you connect to a new parent request. Then you have all field to use with webservice (needed for json).

P.ABBE
ABBE Philippe, proud to be a member of EV CONNECT FORUM since Nov 2015.

#3
Ok.... I'm on, not exactly with your solution but you gave me the point...
I started creating one function (not view) with the request_id as parameter. Also, I'm using the function with select from function with "for Json" option (I didn't know this, new for me), so I get result formatted as JSON and not html table. This format can be read by the external webservice and not need (now) split parameters...

Thank you!






Users browsing this thread: 1 Guest(s)