L3 - Default User Story (Required on creation):
Different RPA Tasks can have different allowed timeouts in which they need to have been successfully executed before an incident is raised.
Functional Requirements (Required before implementation):
I can define a timeout per RPA Task that is taken into consideration before it is marked as failed.
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (optional):
For UiPath, this might make more sense in combination with a Queue Item approach instead of a Job approach as defined in CAM-12194.
This is the controller panel for Smart Panels app
I can define an allowed wait time for an RPA Task
User Story (Required on creation):
Different RPA Tasks can have different allowed timeouts in which they need to have been successfully executed before an incident is raised.
Functional Requirements (Required before implementation):
I can define a timeout per RPA Task that is taken into consideration before it is marked as failed.
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (optional):
For UiPath, this might make more sense in combination with a Queue Item approach instead of a Job approach as defined in CAM-12194.
This is the controller panel for Smart Panels app
-
Unassigned
-
Tobias Metzke-Bernstein
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: