Deprecated and removed features of IBM Business Automation Workflow 23.0.1 and 23.0.2
The deprecations and removals that are made in IBM Business Automation Workflow 23.0.1 and 23.0.2 are summarized in the following sections.
Deprecated features
If a feature is listed as deprecated, or certain system requirements are indicated as deprecated on the Software Product Compatibility Reports website, IBM might remove this capability or support in a subsequent release of the product to focus on follow-on technologies or the strategic feature that is listed under Action. Typically, a feature is not deprecated unless an equivalent alternative is provided or available. A feature is not removed for at least two releases after the deprecation of the feature is declared. In rare cases, it might be necessary to remove features sooner; such cases are indicated in the descriptions of these removed features.
The following features from previous releases are deprecated in IBM Business Automation Workflow versions 23.0.1 and 23.0.2.
| Deprecated features | Description | Action |
|---|---|---|
| 23.0.2 Solution Document Generator (Docgen) utility | The Solution Document Generator (Docgen) utility that generated a solution description document for a set of cases is deprecated in this release. | This utility does not contain any of the new Business Automation Workflow integration data. View the solution details by opening the solution in Business Automation Studio or Workflow Center. |
| 23.0.1 BPM content store | The BPM content store supports a subset of the inbound content event types that are supported by external ECM systems. |
Use the BPM document store, which is the default CMIS-enabled document repository for content management in processes. Processes can also integrate with external CMIS-enabled document repositories such as IBM FileNet® Content Manager, IBM Content Manager, Alfresco Community server, or Microsoft SharePoint. |
| 23.0.1 Collaboration mode in Process Designer | The collaboration-mode configuration setting determines how changes in the editor are saved in the Process Designer. | Use hybrid mode for every type of configuration. |
| 23.0.1 Local operating system registry, stand-alone Lightweight Directory Access Protocol (LDAP) registry, and stand-alone custom registry | These user registries are deprecated. | Use federated repositories when you do a fresh install. |
Removed features
The following features from previous releases are removed in IBM Business Automation Workflow 23.0.1 and 23.0.2.
| Removed features | Description | Action |
|---|---|---|
23.0.2 Configuration flag use-jaxws |
Use of the configuration flag use-jaxws is removed in Business Automation Workflow. |
In your configuration files, for example 100Custom.xml, remove the
<use-jaxws> configuration flag to leverage the more modern web services
implementation. |
| 23.0.2 Robot tasks | A robot task is a task performed by a robot that is implemented in IBM Robotic Process Automation with Automation Anywhere or in other robotic process automation tools. Each robot task has a specific interface that is implicitly defined by the data that is exposed to it. | Create and use inline user tasks instead. |
| 23.0.2 Upgrading from Business Automation Workflow 18.0.0.x, 19.0.0.1, or 19.0.0.2 | Upgrading from 18.0.0.x, 19.0.0.1, or 19.0.0.2 to 23.0.2 is not supported. | Upgrade to 23.0.1 and then upgrade to 23.0.2. |
| 23.0.2 Decision Recommendation and Workforce Insights services | These services are removed. | Use of these Machine Learning Server services is no longer supported. |
| 23.0.1 ECM adapter | Adapter connecting to Enterprise Content Management Systems | Use of the WebSphere adapter for Enterprise Content Management is removed. |
| 23.0.1 Lotus® Domino® adapter | Adapter for connecting to Lotus Notes Mail Server | If you used the Lotus Domino adapter for email, use the WebSphere Adapter for email instead. |
| 23.0.1 iSeries adapter | Adapter for connecting to iSeries Operating System | Use standard bindings like JMS and Web Service instead. |
| 23.0.1 Business Automation Workflow on containers Web Service APIs | The web API allows handling of process instances and tasks from an external web service client. The web API is still available on traditional Business Automation Workflow. | Use the Business Automation Workflow REST runtime API. |