Differences between on-cloud and on-prem capabilities

General differences

• To connect Business Automation Workflow on Cloud to on-prem backend systems that are not already exposed to the internet, work with IBM® Support to get a VPN set up.
• You cannot use the WebSphere® Application Server administrative console or the wsadmin commands for administrative actions on the cloud platform, such as importing certificates or managing data sources. Instead, account administrators and operators use the functionality available from the Admin menu in the cloud portal. For more information see Managing access and Operating cloud environments. REST APIs are available for other administrative actions, see Operations REST APIs reference in the Business Automation Workflow on-prem documentation. If you require a configuration or administrative change that doesn't have an equivalent REST API, open a case through the IBM Support site.
• You cannot configure Business Automation Workflow on Cloud to directly connect to your on-prem user registry. To allow automatic synchronization between the on-prem and on-cloud user registries, use the User Management and Group Management APIs. See the API reference for more information. If you are migrating from on-prem Business Automation Workflow to the on-cloud offering, update the staff assignments in your process models to use the definitions in the on-cloud user registry.
• The following case tools are not available in the on-cloud offering: Case Analyzer, Mobile Client for Case, and FileNet® eForms.
• The Case configuration tool is used by IBM Support to set up your cloud subscription; it is not generally available to customers.

Release-specific differences

Business Automation Workflow 20.0.0.1 and later

• Business Automation Workflow on Cloud supports only the features and functions available in traditional runtime environments. To take advantage of features that are available only in container environments, such as low-code designers for building workflows as reusable automation services, consider moving to the business automations capabilities. See Moving to business automations capabilities.
• The Intelligent Task Prioritization function, which is required for task prioritization, isn't available in Process Portal.

Business Automation Workflow 19.0.0.2

Content object support is not enabled. When business objects, roles, properties, and choice lists are defined in Case Builder, the corresponding artifacts aren't automatically created in Process Designer.