Introduction
IBM
Business Process Manager (BPM) updates are now released every quarter to enable
customers to stay current, apply the latest fixes, and take advantage of new
product enhancements sooner. Cumulative Fixes are applied to the latest BPM
release as a simple in-place upgrade. IBM BPM 8.5.7 Cumulative Fix 2016.09 is
now available for you to download and upgrade today.
Highlights
The
following new feature and fixes are included in IBM Business Process Manager
(BPM) V8.5.7 cumulative fix 2016.09. With this update you will be able to…
New features:
v Invoke REST
services directly from your business processes
v Create
custom integrations using new low code web-based service editors to discover
Java and REST based services
v Deploy BPM
Advanced assets and manage the health of your processes using new self service
facilities for BPM on Cloud
v Deactivate
users who are no longer in the user registry and clean up their group
memberships
New supported environments include:
v Microsoft
Edge (for IBM Process Portal & Responsive Coaches)
v Oracle 12c
multi-tenant feature
v Microsoft
SQL Server 2016
v IBM DB2
11.1
Overview
New function in web Process Designer to create
services
Ø Discover
REST services, for example Watson, and Java applications and call them by using
service flows.
Ø Model
services for business processes in the web Process Designer by using service
flows.
Ø Bring
heritage services (that were created in desktop Process Designer) into the web
Process Designer by converting them into service flows.
Deactivate users from your system who are no longer in
the user registry
In typical
organizations, people come and go and take on new roles. However, when users
are known to IBM BPM (meaning they are in the IBM BPM database), they were
available for task assignments and social interactions even after they were
deleted from the user registry. Before this cumulative fix, there was no way to
deactivate users in the database that were no longer available in the user
registry. For more information about user lifecycle, see Runtime user
availability and lifecycle.
Note:
Deactivate users only if you use clients that rely on REST or JavaScript API
calls. If the client uses the web service API, do not deactivate users because
the API does not support user deactivation.
The
following improvements were made for user deactivation:
Ø A new
parameter added to syncExistingUsers admin script helps you sync user availability
between the user registry and the IBM BPM database.
Ø APIs were
adapted so that you can now look up users based on their availability by using
an availability flag.
Ø APIs were
adapted to prevent task assignments and social interaction requests to
deactivated users.
Ø A new
configuration property for the BPMServerSecurityUsers configuration object
helps you define a default task owner to use when all the assigned task owners
are deactivated.
Prevent group membership updates that might cause
inconsistent data
Ø Now IBM BPM
APIs validate group types before applying group membership updates, ensuring
group membership updates that might cause inconsistent data are refused.
Update IBM BPM files at run time
Ø Use the new
BPMUpdateFile command to update the contents of an existing file in your
process application or toolkit. When the command is run, it creates a new
version of the file at the tip of the branch.
