Continuing the discussion regarding asking user input for rules, I thought this probably deserves its own feature request.
Currently, asking for user input is only available for button automations. However, as was discussed in the topic, it would be very useful to have available as part of automation rules. There are quite a few instances where this might be useful, for example:
When a new item is created (in a view or inline in rich text fields/documents), there are often some important fields that should be filled in quickly. Being able to ask user input for select fields as part of on creation rule would be a great way of doing this. Currently, you have to click (or Alt+click) to open the full entity view to be able to enter this data. A simple example of this would be when creating a new task during a meeting, you would want to capture things like assignee, due date, priority, etc right away. This is also extremely useful when the name of the entity is formula-based.
As part of a particular workflow, there is often a need to capture bits of information as you go through the workflow. So It would be helpful if you are able to define rules when a particular update to a workflow/single-select field would trigger a rule and ask for particular information to be added or updated. An example of this would be approval process for vacations/purchasing/expenses where in the multi-step process, the individual decisions might need to be captured.
@Oleg identified some challenges with this, in particular since rules can be triggered by a variety of situations where there is no user to ask for input. There were a number of interesting suggestions:
- Setting up default values (which is already possible for drop downs but might be useful for other fields) that would be used when input is not available
- Applying the rule to situations when the action is triggered as part of a user UI action