Abbyy Service Task
Introduction
The ABBYY Service Tasks allows to execute an ABBYY skill within the context of a Flowable case.
Properties
General
Common
Attribute | Type | Description | Category |
---|---|---|---|
Model Id | Text | Model Id identifies the element within the process model. | |
Name | Text | The name of the element. This is the name displayed in the diagram. | |
Documentation | Multiline Text | The documentation attribute additionally adds a description to the component. | |
Input documents | Text | Content Items which need to be sent to ABBYY | |
Skill ID | Selection with dynamic elements | The Abby Skill you want to apply | |
Output variable name | Text | The variable name that stores the result of executing this service task. | |
Field mappings | List | ||
Save output variables as transient variable | Boolean | Stores all variables created by invoking this service task as transient. |
Form
Attribute | Type | Description | Category |
---|---|---|---|
Manual review form | Reference | The form used if your ABBYY transaction requires a manual review |
Assignment
Attribute | Type | Description | Category |
---|---|---|---|
Assignee | User Selection | User ID of the task's assignee. The assignee can see and complete a task and is usually the person responsible for it. | |
Owner | User Selection | The owner of a task can see a task and is able to delegate it to another user. This user then becomes the assignee and can resolve the task. A resolved task will then be reassigned to the owner who can then complete the task. | |
Candidate users | User Selection | By selecting one or more candidate users, the task might be taken by one of those users. If the task is not specifically assigned to one of the users directly, it will show up in all of the selected candidate users tasks list until assigned directly. | |
Candidate groups | Group Selection | By selecting one or more groups as the candidate groups, shares the task with all users belonging to at least one of the groups. If there is no specific assignee specified but the task has candidate groups, the task will show up in all users task list belonging to at least one of the groups until the task is assigned to a specific user. |
Control
Attribute | Type | Description | Category |
---|---|---|---|
Required | Boolean | Select this option to mark the element as required (exclamation mark decorator). Required plan items must be either in the status COMPLETED, TERMINATED, or DISABLED in order for their parent stage to complete. | |
Completion neutral | Boolean | Completion neutral influences the plan item's parent stage completes. Plan items in the state AVAILABLE may prevent the parent stage (or case) from automatically completing. By checking this property, the plan item will behave neutral with respect to the completion of the parent container. | |
Manual activation | Boolean | Select this option to mark the element to have Manual activation (right arrow 'play' decorator). Plan items with Manual activation move from state AVAILABLE to state ENABLED once they trigger. A plan item in state ENABLED exposes an action button that allows the user to manually start the plan item. | |
Manual activation name | Text | Define the name to be used for the manual activation trigger. | |
Manual activation icon | Icon | Define the icon to be used for the manual activation trigger. | |
Manual activation priority | Integer | The priority for the Manual activation action | |
Manual activation permission groups | Group Selection | Define the groups which have access to the manual activation trigger. | |
Manual activation permission users | User Selection | Define the users which have access to the manual activation trigger. | |
Manual activation channels | Text | Define a list of channels to expose the manual activation action. | |
Start form | Reference | An optional form shown when the event listener is manually activated. | |
In same deployment | Boolean | Set it to true if the referenced definition should be referenced from within the same app deployment. Set it to false to always use the newest definition. | |
Validate start form fields (server-side) | Boolean | If the start form is submitted and validate form fields expression evaluates to true, form fields are validated on the BE side according to the form model restrictions. |
Repetition
Attribute | Type | Description | Category |
---|---|---|---|
Repetition | Boolean | Select this option to mark the element as repeatable (fencemark decorator). Repeatable plan items may exist more than once at run-time, each having their own life-cycle. | |
Repetition counter variable | Text | Name of the repetition counter variable. | |
Don't create repetition counter variable | Boolean | Enable this flag to prevent the creation of the repetition counter variable. When a variable aggregation is defined, this flag will be ignored and a repetition counter variable will be created. | |
Max instance count | Selection:
| Defines the maximum number of instances for repetition. Note that this does not mean there can be only one instance ever in the lifetime of a case instance, this will limit the instances each time when the repetition is evaluated (for example when an entry sentry evaluates to true to re-enter a stage or plan item). | |
Collection variable | Text | Variable to be used as the collection for the repetition. | |
Element variable | Text | Variable that will be used to store the current item value for the repetition. | |
Element index variable | Text | Variable that will be used to store the current index value for the repetition. | |
Variable Aggregations | List |
Advanced Form
Attribute | Type | Description | Category |
---|---|---|---|
Validate form fields (server-side) | Boolean | If the start form is submitted and validate form fields expression evaluates to true, form fields are validated on the BE side according to the form model restrictions. |
Advanced
Execution
Attribute | Type | Description | Category |
---|---|---|---|
Impact on parent completion | Selection:
| Defines how the plan item is used when the parent completion evaluation is executed. | |
Asynchronous | Boolean | When enabled, the behavior of the plan item will be executed as an asynchronous job. This will happen when the plan item transitions to the ACTIVE state. During the execution of the behavior, the plan item will be set to an intermediate ASYNC_ACTIVE state. Please refer to the documentation for more details. | |
Exclusive | Boolean | Determines whether the plan item is run as an exclusive job. An exclusive job makes sure that no other asynchronous exclusive plan items within the same case instance are performed at the same time. This helps to prevent failing jobs in concurrent scenarios. | |
Leave asynchronously | Boolean | When enabled, the leaving of the plan item will be executed as an asynchronous job. This will happen when the plan item transitions moved out of the ACTIVE state. During the execution of the behavior, the plan item will be set to an intermediate ASYNC_ACTIVE_LEAVE state. Please refer to the documentation for more details. | |
Leave exclusive | Boolean | Determines whether the activity should leave as an exclusive job. An exclusive job makes sure that no other asynchronous exclusive activities within the same process are performed at the same time. This helps to prevent failing jobs in concurrent scenarios. | |
Job Category | Text | When set, the underlying generated job will have a Job Category, which will be executed only by Application Servers, where the Case Engine has enabledJobCategories set to this category. | |
Include in history | Boolean | When the history level is set to "instance" or "task" level with this property it can be configured if this plan item instance should be included in the historic plan item instance data. |
Listeners
Attribute | Type | Description | Category |
---|---|---|---|
Lifecycle listeners | List | Allows you to define lifecycle listeners for a plan item. Lifecycle listeners allow you to execute an expression, a delegate expression or a class when a plan item transitions from one state to another. |
Reactivation
Attribute | Type | Description | Category |
---|---|---|---|
Direct activation condition | Boolean | Condition that expresses if the plan item should be directly activated when a case instance is reactivated. | |
Ignore condition | Boolean | Condition that expresses if the plan item should be ignored when a case instance is reactivated. | |
Default condition | Boolean | Condition that expresses if the plan item should trigger when a case instance is reactivated. |
Visual
Attribute | Type | Description | Category |
---|---|---|---|
Font size | Selection:
| The font size of the element in the diagram. | |
Font weight | Selection:
| The font weight of the element in the diagram. | |
Font style | Selection:
| The font style of the element in the diagram. | |
Font color | Color | The font color of the element in the diagram. | |
Background color | Color | The background color of the element in the diagram. | |
Border color | Color | The border color of the element in the diagram. |
List Attribute Details
Field mappings
Attribute | Type | Description |
---|---|---|
Allowed skill field | Selection with dynamic elements | |
Mapping name | Text |
Variable Aggregations
Attribute | Type | Description |
---|---|---|
Target (Variable / Expression) | Text | The name of the target variable or an expression that gives the variable name |
Type | Selection:
| The audit log type. |
Delegate Expression | Text | Delegate Expression to be executed when the task is activated. A delegate expression must resolve to a Java object, for instance a Spring bean. The object's class must implement either PlanItemJavaDelegate or CmmnActivityBehavior. |
Class | String | Fully qualified classname of a class to be invoked when executing the task. The class must implement either PlanItemJavaDelegate or CmmnActivityBehavior. |
Target variable creation | Selection:
| |
Variable Definitions | BasicFormList |
Variable Definitions
Attribute | Type | Description |
---|---|---|
Source (Variable / Expression) | Text | The name of the source variable or an expression that provides the value |
Target (Variable / Expression) | Text | The name of the target variable or an expression that gives the variable name |
Lifecycle listeners
Attribute | Type | Description |
---|---|---|
Source state | Selection:
| |
Target state | Selection:
| |
Class | Text | Fully qualified classname of a class to be invoked when executing the task. The class must implement either PlanItemJavaDelegate or CmmnActivityBehavior. |
Expression | Text | JUEL Expression to be executed when the task is started. Expressions allow you to interact with the backend by calling services, making calculations etc. You can find more information about expressions in the documentation. |
Delegate expression | Text |