Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: Hidden Fields are not supported in the UQI #38466

Open
NilanshBansal opened this issue Jan 3, 2025 · 0 comments
Open

[Task]: Hidden Fields are not supported in the UQI #38466

NilanshBansal opened this issue Jan 3, 2025 · 0 comments
Assignees
Labels
Task A simple Todo

Comments

@NilanshBansal
Copy link
Contributor

SubTasks

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.
SCR-20250103-o17-2

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.

  1. 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.
  2. Supporting hidden fields in UQI and passing values from there. (If we chose to go with this approach, create a new task)
  3. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task A simple Todo
Projects
None yet
Development

No branches or pull requests

4 participants