Is your feature request related to a problem? Please describe.
ROI cant calculate correctly when there are short running automations.
For example, we have a process to deprovision users. A process is run which leverages RPA to check for open tickets that need to be worked, if none the process completes in a matter of seconds, if there are tickets it works them.
The project record only accounts for total user transaction time, thus when the powerBI calculates it references every "check" and logs the time difference as hours saved. Resulting in thousands of incorrect hours saved.
For example, one of our processes shows as 40.8k hours saved which is not possible.
Describe the solution you'd like
A method to account for short running "checks" processes, or the ability to create projects specifically for these activities that allow 0 ROI basis calculations. Currently the flow will fail if we use $0 values.
Describe alternatives you've considered
We are adding a field for "dispatcher/performer", when the project is considered a Dispatcher we are going to set the power BI to exclude these runs.
We would prefer to set the ROI basis to zero for dispatcher duties since these are commonly api calls that check for processes to work, however, the ROI power automates fail if the basis fields are not a minimum of 1.
Is your feature request related to a problem? Please describe.
ROI cant calculate correctly when there are short running automations.
For example, we have a process to deprovision users. A process is run which leverages RPA to check for open tickets that need to be worked, if none the process completes in a matter of seconds, if there are tickets it works them.
The project record only accounts for total user transaction time, thus when the powerBI calculates it references every "check" and logs the time difference as hours saved. Resulting in thousands of incorrect hours saved.
For example, one of our processes shows as 40.8k hours saved which is not possible.
Describe the solution you'd like
A method to account for short running "checks" processes, or the ability to create projects specifically for these activities that allow 0 ROI basis calculations. Currently the flow will fail if we use $0 values.
Describe alternatives you've considered
We are adding a field for "dispatcher/performer", when the project is considered a Dispatcher we are going to set the power BI to exclude these runs.
We would prefer to set the ROI basis to zero for dispatcher duties since these are commonly api calls that check for processes to work, however, the ROI power automates fail if the basis fields are not a minimum of 1.
Additional context?
AB#534