Difference between revisions of "Auto Tasks"
Jump to navigation
Jump to search
| (20 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{bluebanner|[[Main Page|Home]] > [[Integration]] > [[Business Process Automation & Orchestration]] > Auto Tasks|[[:Category:Integration|Index]]}} | |
| − | |||
| − | |||
{|style="width: 100%" | {|style="width: 100%" | ||
|- valign="top" | |- valign="top" | ||
|style="width:73%"| | |style="width:73%"| | ||
==Introduction== | ==Introduction== | ||
| − | Auto Tasks provide the | + | Auto Tasks provide the ability to execute automation from [[Custom Buttons]] on different entity views in apps on the Hornbill platform. Auto tasks are similar to business processes, however differ in that they do not contain stages, don't use tasks or approvals, and can't be suspended. When executed, the Auto Task will simply start > Execute > End. An Auto Task can contain many nodes and therefore execute multiple actions triggered from a single custom button. Auto Tasks can be configured using the [[Auto Task Designer]] |
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 21: | Line 19: | ||
==Configuration== | ==Configuration== | ||
| + | {{#ev:youtube|878alZjEWLA|350|right}} | ||
* 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 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 against different entities in each different app. Ensure you choose the appropriate entity you wish to create the Auto Task process against from the drop down. |
* Auto Tasks can be configured to be invoked from [[Custom Buttons]] on entity views in the different line of business applications. | * Auto Tasks can be configured to be invoked from [[Custom Buttons]] on entity views in the different line of business applications. | ||
| − | :* Auto | + | :* Auto Tasks will only be visible to invoke if the process is validated and marked as active. |
| + | :* Auto Tasks will only be visible to invoke if the process is created for the relevant entity (see "Apps & Entities" section). | ||
| + | |||
| + | |||
==Roles== | ==Roles== | ||
| Line 33: | Line 35: | ||
* '''Business Process Manager''' - This role will enable a user to configure Auto Tasks against entities in an application from the admin console. | * '''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. | * '''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. | + | :* Visibility of the custom buttons, from which an Auto Task process can be invoked is configurable per custom button on each entity view. Read more [https://wiki.hornbill.com/index.php?title=Custom_Buttons '''here'''] |
==Apps & Entities== | ==Apps & Entities== | ||
| − | Auto | + | Auto Tasks can be configured and invoked via custom buttons on the following apps and entity views. |
* Service Manager | * Service Manager | ||
| Line 46: | Line 48: | ||
:* Documents | :* Documents | ||
| + | '''Note:''' on creation, the default entity for an Auto Task process is set to "Global". This value needs to be changed to a relevant entity for the process to be available for selection when designing custom buttons. | ||
| + | [[Category:Integration]][[Category:Videos]][[Category:HDOC]] | ||
| − | + | <!-- http://localhost:3001/bpm-workflow/auto-tasks --> | |
Revision as of 20:02, 26 July 2023
| Home > Integration > Business Process Automation & Orchestration > Auto Tasks | Index |
IntroductionAuto Tasks provide the ability to execute automation from Custom Buttons on different entity views in apps on the Hornbill platform. Auto tasks are similar to business processes, however differ in that they do not contain stages, don't use tasks or approvals, and can't be suspended. When executed, the Auto Task will simply start > Execute > End. An Auto Task can contain many nodes and therefore execute multiple actions triggered from a single custom button. Auto Tasks can be configured using the Auto Task Designer |
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. Ensure you choose the appropriate entity you wish to create the Auto Task process against from the drop down.
- Auto Tasks can be configured to be invoked from Custom Buttons on entity views in the different line of business applications.
- Auto Tasks will only be visible to invoke if the process is validated and marked as active.
- Auto Tasks will only be visible to invoke if the process is created for the relevant entity (see "Apps & Entities" section).
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. Read more here
Apps & Entities
Auto Tasks can be configured and invoked via custom buttons on the following apps and entity views.
- Service Manager
- Requests
- Assets
- Document Manager
- Documents
Note: on creation, the default entity for an Auto Task process is set to "Global". This value needs to be changed to a relevant entity for the process to be available for selection when designing custom buttons.