abas Software AG

Release notes

18.June 2020 - 1.1.1 (On-Premises)

General information

IMPORTANT! abas BPM requires the official licensing mechanism. Before you update to this version, please make sure, your abas BPM installation is licensed/activated through us (abas Software GmbH). .. You can check and ensure this through your VAR. A new color management feature and a new notification system has been built into abas BPM.

Workflow Administration

  • You have to read and accept the license terms (PDF), in order to be able to use any abas BPM application. If not accepted, the user will see a message dialog.

  • Creating notification templates is possible, which can be used in the Workflow Designer.

  • According to your requirements, you can define colors, which can be used in the design process for the BPMN elements

Workflow Designer

  • For a process and for each task, you can select a notification template. This will make sure, an email will be sent to the affected user(s), depending on the process actions.

  • For each BPMN element, you can select a color. This way, your processes can be more colorful. Coloring process elements is NOT recommended though when used in production. The reasons for this is the human nature, as colors bring a level of interpretation into the process. While your intention was to make the process look good, a user might interpret meaning into it. An element red might make the user assume, this task is critical or late or has a high priority, etc.

  • abas ERP task: You can map as many ERP fields as you need. Before, we had a limitation.

  • In the task description, you can use new lines to provide a simple formatting

  • A new service task allows you to load any field of any object (identified by it’s unique object id). This way you can update the data in a workflow instance from abas ERP objects at any time.

  • Every service task has the abas ERP var mapping, so that you can provide updated data into workflow after the execution for the service task.

Workflow Task Overview

  • User settings for e-mail notifications: A user can define settings, if she wants to get notified, when the state in the process changes. This can be overridden by the administrator.

  • Your task description is not only a one-line text. It can contain multi-line text and spacing for better readability.

Backend

  • You can send emails, when your SMTP server is behind a proxy server

  • The communication with abas ERP for Service tasks have advanced configuration options (timeout, license allocation, advanced logging

Problems

  • Trigger is not triggered correctly
    The problem occurs when a person has an ERP task and at the same time a trigger is to be triggered. Then an error message is displayed.
    The workaround would no longer be to use the "Assignee" field, but "Candidate Users" or "Candidate Groups". Only if the user then wants to edit the task, he has to press "Claim" and then edit the task immediately. Once the task is assigned to itself, there will be problems with triggering.

  • Chain conditions in the evaluation script
    When using a chained logical condition, only the first condition is evaluated.
    if(empty(bpmEditor.totalNetAmt) && bpmEditor.calcGrossAmt){throw new RuntimeException("Set field!");}
    The workaround would be to define another variable and write the condition into this variable.
    def ok = !empty(bpmEditor.totalNetAmt) && bpmEditor.calcGrossAmt if(!ok){throw new RuntimeException("Set field!");}`

27.February 2020 - 1.1.1 (Hybrid-Cloud)

Backend

Fix some notification issues

12.February 2020 - 1.1.0 (Hybrid-Cloud)

General information

IMPORTANT! abas BPM requires the official licensing mechanism. Before you update to this version, please make sure, your abas BPM installation is licensed/activated through us (abas Software GmbH). .. You can check and ensure this through your VAR. A new color management feature and a new notification system has been built into abas BPM.

Workflow Administration

  • You have to read and accept the license terms (PDF), in order to be able to use any abas BPM application. If not accepted, the user will see a message dialog.

  • Creating notification templates is possible, which can be used in the Workflow Designer.

  • According to your requirements, you can define colors, which can be used in the design process for the BPMN elements

Workflow Designer

  • For a process and for each task, you can select a notification template. This will make sure, an email will be sent to the affected user(s), depending on the process actions.

  • For each BPMN element, you can select a color. This way, your processes can be more colorful. Coloring process elements is NOT recommended though when used in production. The reasons for this is the human nature, as colors bring a level of interpretation into the process. While your intention was to make the process look good, a user might interpret meaning into it. An element red might make the user assume, this task is critical or late or has a high priority, etc.

  • abas ERP task: You can map as many ERP fields as you need. Before, we had a limitation.

  • In the task description, you can use new lines to provide a simple formatting

  • A new service task allows you to load any field of any object (identified by it’s unique object id). This way you can update the data in a workflow instance from abas ERP objects at any time.

  • Every service task has the abas ERP var mapping, so that you can provide updated data into workflow after the execution for the service task.

Workflow Task Overview

  • User settings for e-mail notifications: A user can define settings, if she wants to get notified, when the state in the process changes. This can be overridden by the administrator.

  • Your task description is not only a one-line text. It can contain multi-line text and spacing for better readability.

Backend

  • You can send emails, when your SMTP server is behind a proxy server

  • The communication with abas ERP for Service tasks have advanced configuration options (timeout, license allocation, advanced logging

Problems

  • Trigger is not triggered correctly
    The problem occurs when a person has an ERP task and at the same time a trigger is to be triggered. Then an error message is displayed.
    The workaround would no longer be to use the "Assignee" field, but "Candidate Users" or "Candidate Groups". Only if the user then wants to edit the task, he has to press "Claim" and then edit the task immediately. Once the task is assigned to itself, there will be problems with triggering.

  • Chain conditions in the evaluation script
    When using a chained logical condition, only the first condition is evaluated.
    if(empty(bpmEditor.totalNetAmt) && bpmEditor.calcGrossAmt){throw new RuntimeException("Set field!");}
    The workaround would be to define another variable and write the condition into this variable.
    def ok = !empty(bpmEditor.totalNetAmt) && bpmEditor.calcGrossAmt if(!ok){throw new RuntimeException("Set field!");}`

31.March 2019 - 1.0.0

General information:

  • abas BPM and all its components and dependencies will be installed and configured with a new installation process. During this process a new product "abas Installer" will be used.

  • A new authentification mechanism has been created and will be release for the On-Premises model. An open-source identity and access management solution "Keycloak" (https://www.keycloak.org/) is used.

  • abas BPM components have been renamed: Workflow Designer, Workflow Viewer, Workflow Task Overview und Administration Overview.

Workflow Designer:

  • The search terms can be resetted when opening workflows

  • More simple entry of candidate users and candidate groups. These can also be defined using dynamic values

  • Dynamic forms: Form fields can be sorted/moved

  • Dynamic forms: Form fields can be defined as read-only fields. This way, data from previous forms or data sources (for example, abas ERP) can be displayed.

  • Dynamic forms: New form field for providing key-value pairs. This way the data that is being shown and the actual value can be different.

  • Dynamic forms: New form field for numbers, which can be used for calculations. The previous number field, which in fact was a text value, remains.

Task Overview:

  • Dynamic forms: The date format uses the language format defined by the web browser

  • Dynamic forms: Read-only fields are displayed

  • The language "HU" (Hungarian) is supported.

Workflow Viewer:

  • The language "FR" (French) is supported.

  • The language "HU" (Hungarian) is supported.

  • The legend and the table can be hidden and made visible.

abas-essentials-app:

  • Update to abas installer 0.12.0 (Warning: You have to update your fop.txt)

Process Engine:

  • The latest process engine version is used (Upgrade from Camunda 7.7 to Camunda 7.10)

11.December 2018 - 0.74.1

abas-bpm-ui (0.74.1)

  • [Fix] admindashboard, userdashboard, designer and viewer are now working with the latest demosystem

03.December 2018 - 0.74.0 & 0.304.0

abas-bpm-ui (0.74.0)

  • [New] Viewer: The Viewer is displayed in the following languages: german, bulgarian, polish, france, turkish and english

  • [Fix] User dashboard: Perform task in User dashboard will always get the correct Task ID with Native UI or EKS option

  • [Fix] User dashboard: With Native UI new blank will not be opened when performing the task

  • [Fix] User dashboard: Specical characters like quote or backslach in input will not cause error on dynamic forms

  • [Fix] User dashboard: Fix claim und unclaim buttons for group tasks

  • [Fix] User dashboard: Fix the required fields on dynamic forms

  • [New] User dashboard: Any attachment/link will be openend in a new

  • [New] Userdashboard: In the integrated GUI (EKS Option), any Action that performed something opens a new blank browser window

  • [Fix] Designer: The process selection dialog is shown correctly in the foreground

  • [Fix] Designer: Ordering the not executable workflows by date is working

  • [New] Every time you get an information when you open an erp object which is already used in a task. You are able to decide to not start this task

abas-essentials-app (0.304.0):

  • [New] Add polish and turkish text for error messages

abas-bpm-camunda (0.304.0):

  • [New] When creating an abas ERP object with service task, the table fields from ERP are readable in var mapping

18.October 2018 - 0.73.0 & 0.303.0

abas-bpm-ui (0.73.0)

  • [New] Designer: Open workflows view with search and filtering

  • [New] User Dashboard: Integrate redux state management in userdashboard

  • [New] User Dashboard: Upgrade userdashboard to polymer 3

abas-essentials-app (0.303.0-r117):

  • [Fix] Task is locked by…​ is not shown anymore

  • [Fix] User defined message in evaluation script is not shown anymore

abas-bpm-camunda (0.303.0-r117):

  • [Fix] Sending emails with empty spaces

  • [Fix] API Key user check is case sensitive

07.September 18 - 0.72.0 & 0.303.0

abas-bpm-ui (0.72.0)

  • [New] Designer: Service Task Element Template "Run abas ERP Infosystem" added

  • [New] Designer: Configure the client for the dynamic forms

  • [New] Designer: Deploying and loading workflows that are not executable

  • [New] Designer: Improve error messages

  • [Fix] Designer: Switching task types will reset the element template correct now

  • [Fix] "Best viewed with chrome" popup is not shown anymore when you use BPM embedded in the windows client

abas-essentials-app (0.303.0-r104):

  • [Fix] Change the resource.language files of infosystem to german

  • [Fix] Show/hide the perform and finish buttons correctly in infosystem processcenter

22.August 2018 - 0.71.0 & 0.302.0

abas-bpm-ui (0.71.0)

  • [New] Designer: Modeler is now able to work with camunda standard tasks

  • [New] Designer: Element template "abas standard task" added

  • [New] Userdashboard: User are able to work with standard tasks

abas-essentials-app (0.302.0-r77):

  • [New] Standard tasks are now visible in processcenter

08.August 2018 - 0.70.6

abas-bpm-ui (0.70.6)

  • [New] Add dialog that bpm works best with chrome if "non chrome" browser is used

  • [New] A new info icon in the header opens a dialog which included the version number

  • [New] Viewer: Improve legend and font

  • [Fix] Viewer: The scrollbar-height is displayed correct

  • [New] Designer: A new icon in the footer provides an opportunity to reset zoom

  • [Fix] Userdashboard: After clicking on the share-viewer-icon the toast message would be shown correct

  • [Fix] Admindashboard: After creating a new user the user will automatically added to the group "erp-_user"

27.July 2018 - 0.70.4 & 0.301.0

abas-bpm-ui (0.70.4)

  • [New] Viewer: Show the detailed information for a running workflow

  • [New] Designer: Use the JIRA issue collector for getting user feedback

  • [New] Designer: Providing links to the documents and detailed information for a user task

  • [New] Designer: Providing opportunity to access a specific field value from a specific table row from the table of an object, that it can be used in workflows

  • [New] Userdashboard: Accessing links to documents and detailed information in a user task

  • [New] Userdashboard: Use the JIRA issue collector for getting user feedback

  • [New] Userdashboard: A new share icon on the open task and finished task that copy the link to the abas BPM Viewer

  • [New] Userdashboard: A new viewer icon on the finished task that you open the abas BPM Viewer

  • [Fix] Userdashboard: Fix the search input in the list of the opentasks

  • [Fix] Userdashboard: Fix the size of the date field in the dialog of the dynamicform tasks

  • [Fix] Userdashboard: Fix the dynamic form dialog that is uses the correct data

  • [Fix] Admindashboard: Show the warning box in the Triggers and Api Key tabs if the current user is not admin user

  • [Fix] Admindashboard: Show the warning box in the Triggers and Api Key tabs if the abas-bpm-camunda version is older than 0.300.0

abas-essentials-app (0.301.0-r53):

  • [New] Synchronizing version numbers with abas-bpm-camunda

  • [New] Access the complete table in the varMapping of an abas User Task

abas-bpm-camunda (0.301.0-r53):

  • [New] Synchronizing version numbers with abas-essentials-app

  • [New] Add backend logic to provide public endpoint showing the abas-bpm-backend version

  • [New] Add backend logic to provide endpoint showing if the current authenticated user is admin user or not

28.June 2018 - 0.70.1 & 0.300.0

abas-bpm-ui (0.70.1)

  • [New] Admindashboard: Add trigger view to manage triggers

  • [New] Admindashboard: Add api key view to create api keys

  • [New] Viewer: User is able to logout now

abas-bpm-essentials-app (0.300.0):

  • [New] Show "Choose Dialog" if a user might trigger more than one task

  • [Delete] Remove additional table triggers

  • [Delete] Remove additional table configuration

  • [New] Improve performance if you got a lot running tasks

abas-bpm-camunda (0.300.0):

  • [New] Add new endpoints (for triggers, api-key and tasks)

13.June 2018 - 0.203.0

abas-bpm-camunda (0.203.0):

  • [New] Mandatory configuration options: ABAS_TENANT and ABAS_DOMAIN

  • [New] Set configuration option CONFIGURATION_JSON_URL as optional entry

22. May 2018 - 0.61.0 & 0.202.0

abas-bpm-ui (0.61.0):

  • [New] Designer: Dynamic forms: new type "list" is avaliable

  • [New] Userdashboard: Dynamic forms: new type "list" is avaliable

  • [New] Userdashboard: New languages: polish and bulgarien

  • [New] Viewer: New languages: polish and bulgarien

abas-essentials-app (0.202.0):

  • [New] Deliver ESDK App for 2018, 2017 & 2016

25.April 2018 - 0.60.1 & 0.202.0

abas-bpm-ui (0.60.1):

  • [New] Designer: Element-templates support for abas bpm extensions

  • [New] Userdashboard: Perform UIs are now configurable

  • [New] Userdashboard: Adding date fields in dynamic forms

  • [Fix] Userdashboard: Fix papercard date visualization

abas-essentials-app (0.201.3):

  • [New] Change jar file name in preperation of 2018 support

  • [Fix] Open tasks can be edited again

abas-bpm-camunda (0.202.0):

  • [New] Add element-templates backend logic to abas-bpm-extensions

Older releases