You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While creating an externalSaas Integration, we had to pass the httpMethod (for eg: GET, POST, PUT, DELETE etc.) and the path (for eg: /v2/tickets) with respect to each action selection from the UI.
We chose to send this from the client side by adding two hidden parameters in the UQI similar to Gsheets plugin but we observed that our current UQI does not support hidden fields.
We need to discuss this within the team, if we should start supporting hidden fields or do this differently.
There are the following known ways of achieving the same.
Keep displaying the fields as it is shown right now but change the UX a bit so it also helps in user understability by looking at the path and method.
Supporting hidden fields in UQI and passing values from there. (If we chose to go with this approach, create a new task)
Add the config httpMethod and path for each function in the actionTemplate collection in cloud services database. Each line item will have a unique function name and the config. The cs before making call to the external provider extracts info from the DB.
The text was updated successfully, but these errors were encountered:
SubTasks
While creating an externalSaas Integration, we had to pass the
httpMethod
(for eg: GET, POST, PUT, DELETE etc.) and thepath
(for eg: /v2/tickets) with respect to each action selection from the UI.We chose to send this from the client side by adding two hidden parameters in the UQI similar to Gsheets plugin but we observed that our current UQI does not support hidden fields.
We need to discuss this within the team, if we should start supporting hidden fields or do this differently.
There are the following known ways of achieving the same.
The text was updated successfully, but these errors were encountered: