Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Auto Tasks

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 workflows, 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

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 workflow 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 workflow is validated and marked as active.
  • Auto Tasks will only be visible to invoke if the workflow is created for the relevant entity (see “Apps & Entities” section).

Roles

Name Description
Workflow 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 workflow can be invoked is configurable per custom button on each entity view.

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 workflow is set to “Global”. This value needs to be changed to a relevant entity for the workflows to be available for selection when designing custom buttons.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document