Can anyone share how the input and output are used in UiPath Apps, I have build a very simple workflow that works when debugging, and after deployment to the Orchestrator folder, but the input and output arguements are empty when adding the process to UiPath Apps.
The arguements are correct when testet in the Orchestrator.
Please advice on next steps.
Hi @Michaeljep
you must bind the workflow arguments to app variables. Inputs should be connected to app variables or UI controls, and outputs should be mapped back to app variables. Without this binding, the arguments will remain empty even if they work correctly in Orchestrator.
If helpful, mark as solution. Happy automation with UiPath
The issue is that the mapping doesn’t seem to work in Apps, I can’t assign anything to or from the process?
Ok i think it usually points to a compatibility issue. apps only supports simple argument types (String, Boolean, Number, DataTable, etc.). Complex types, generic objects, or custom classes won’t show up for binding.
Just try to simplify your workflow arguments to supported types, republish the process, then refresh in Apps
Happy Automation
It sounds plausible, but I don’t see many ways of changing it.
This is the setup from the Studio Cloud
In the deployment pane in Orchestrator I can se the in argument, but the out is still empty.
I think the issue is at the outputs definition: At line 2 you set - “type”: “object” , but UiPath apps only supports simple types like string. You need to change that line to - “type”: “string” so the output argument - outIframeurl is exposed correctly in orchestrator and can be mapped in apps.
Now I’ve had the time to look at the setup and do the changes, and it doesn’t matter if it’s object or string. Neither of them are shown when linked to UiPath Apps.
When starting the process in Orchestrator folder, I have these two
Which indicates that the input and output arguements are strings as expected, but in UiPath Apps I see these settings
I would expect something like this
So to me it seems like input/output and the usage of api workflows is not fully compatible with UiPath Apps.
