Feature Requests

I'm talking about whether input candidates can be prepared from the results of calling another action beforehand when inputting parameters on the form on the execution screen. For example, when changing a billing plan, I want to set an action to call the billing plan master first, and then use the results to display a selection column to select the billing plan after the change.

I want to be able to maintain the display order when the display order of the action list is changed

I want the executed and approved colors to be different. Or I want it to be able to be specified.

I feel that the editor is narrow and difficult to edit. I felt that it would be easier to use if the height direction was filled up or the preview could be temporarily closed. Thank you so much for your consideration.

Currently, it is possible to specify non-essential parameters for form-data fields, but if you try to execute without inputting non-essential parameters, an error called `parameters [1] .value cannot be null. I want the entire field to not be sent when it is not entered so that it works properly.

For example, if multiple IDs are passed and repeated processing can be executed, processing is performed for each ID, the same action does not need to be executed by hand over and over again, so the intention is to reduce the number of work steps. If you execute an SQL SELECT statement, you can retrieve data all at once by embedding an IN clause, for example. However, for example, when updating data via the REST API, if an update endpoint has only been created for a single data, there is no reason to establish a new endpoint that accepts multiple IDs, but if anything, I want to keep throwing different values to the same endpoint over and over again.

I'm worried about suddenly executing processing for the production environment, so I want to perform actions in the verification environment. At this time, it feels quite tedious to create separate actions with the same settings for each environment and customized settings for results, so I'm happy that actions can be executed by switching between multiple environments from the viewpoint of preventing setting mistakes and from the viewpoint of omitting trouble.

If it's an action list or action group list, a screen that assumes a transition from another action or group is mixed, and a screen that opens as the first step to perform work first is mixed. Like a common sidebar on a management screen, it would be nice if there were pages where only the actions and groups you want to open are first grouped together as the first level, and then used as a starting point for screen transitions. Also, since actions often used by individuals and actions often used by the team as a whole are different, I don't know if we should simply put the conductors together.