Difference between revisions of "Auto Tasks"
Jump to navigation
Jump to search
(→Roles) |
|||
Line 36: | Line 36: | ||
==Apps & Entities== | ==Apps & Entities== | ||
+ | |||
+ | Auto Task processes can be configured, and invoked via custom buttons on the following apps and entity views. | ||
* Service Manager | * Service Manager |
Revision as of 14:08, 7 April 2020
Home > Integration > Business Process Automation & Orchestration > Auto Tasks
IntroductionAuto Tasks provide the capability to execute a process from custom buttons on different entity views in line of business apps on the Hornbill platform. Auto tasks are similar to business processes, however differ in that they do not contain stages, can't be paused, don't use tasks or approvals, and when executed will simple start > Run > End. An Auto Task process can contain many process nodes and can execute many actions from a single custom button. |
Related Articles |
Configuration
- Auto Tasks if enabled by an app on the Hornbill platform, will be accessible to configure via the admin console > Applications > [App] > Auto Tasks.
- Auto Tasks can be configured against different entities in each different app.
- Auto Tasks can be configured to be invoked from Custom Buttons on entity views in the different line of business applications.
- Auto Task processes will only be visible to invoke if the process is validated and marked as active.
Roles
- Business Process Manager - This role will enable a user to configure Auto Tasks against entities in an application from the admin console.
- Form Designer - This role will enable a user to configure a custom button to invoke an Auto Task from a custom button on an entity view.
- Visibility of the custom buttons, from which an Auto Task process can be invoked is configurable per custom button on each entity view.
Apps & Entities
Auto Task processes can be configured, and invoked via custom buttons on the following apps and entity views.
- Service Manager
- Requests
- Assets
- Document Manager
- Documents