getRunner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2020 06:25 AM
Hi,
Has anyone tried to use the new functionality getRunner.withInputs functionality in the FlowAPI on Paris ?
I get an error like this :
com.glide.plan.runners.FlowObjectAPIException: The inputs provided to the flow: TestFlow_27072020 within application scope: global are incorrect, please refer to the definition
and my code for calling the flow looks like this :
var inputs = {};
inputs['sys_id'] = '123445';
var result = sn_fd.FlowAPI.getRunner()
.flow('global.testflow_27072020')
.inBackground()
.inDomain('global')
.withInputs(inputs)
.run();
Should the input object not be like the one shown above ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2020 07:40 AM
Hi Kim,
is it because your inputs is expecting a 16 digit sysId and instead you are passing in only 6 digits?
The error seems to be referring to the syntax of the input you have provided compared to what the flow/subflow is expecting.
Thanks
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2020 05:50 AM
Hi Sam,
Thanks - I'll try that 🙂
Regards
Kim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2024 05:12 AM
is this issue resolved?, I am facing the same issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2025 06:37 AM - edited 07-11-2025 07:10 AM
The inputs you pass must match with those the flow trigger expects.
See the working example here.
(The question is, how to create a trigger which accepts my desired inputs. More on that perhaps later, if I manage to find out 🙂 )
Update: yes, right,
- different triggers expect different inputs
- you can generate sample script with a call to your flow (... in the top right, then "Create code snippet" <- available only after you activate your flow)
- you can't define your own trigger to ideally match your desired inputs, but you perhaps can misuse available placeholders <- I won't go that far because I found an OOTB trigger which fits well