It would be great if Parameters for a Process could be passed by the Trigger that is kicking it off rather than being limited to what is set in the Process. This would allow the same bot to be used for multiple applications by passing different Parameters to work on differing data via the trigger. It could be set by time, bot or other option. Currently it can only work on what is set in the Process which does not allow for a change in an automated process.
As an example - We have a bot that uses an SQL query to pull the data to work on. The data to use is fed from many process across the company, but all result in a similar action that can be handled by a single bot. This results in a large number of records to processes that is divided across multiple bots. By changing the query used to pull the data, we can control what is processed by source, spread the load and order the priority as needed.
If adding to the trigger is not an option, changing the Parameters should allow for saving as a new Process. This would allow the same package to be selected for multiple Process each using a unique Parameter. This would not be as clean as the having in the Trigger but would allow for multiple process using the same Package/code.
Without one of these capabilities, the only option seems to be to add the query to the code and then uploaded as a new package. This would work but requires the maintenance of multiple code lines for a single variable, which is messy and difficult to mange. Passing the variable via Orchestrator makes sense and the function is almost there.