Machine Learning

Watson Studio

Knowledge Studio

Watson Assistant

Using the command oc logs WORKFLOW_pod_name enable

In the custom resource configuration

In the 100Custom.xmlfile

Using WebSphere Integrated Solution Console under logs and tracing setting

Decentralizing the compliance process at the document level

Connecting to a built-in compliance database for content management function

Automating the burden of paperwork and regulatory compliance by digitizing and managing documentation

Utilizing Robotic Process Automation task bots to query government compliance endpoints

Administer global teams for Cloud Pak components

Certificate management

SAML token generation

Provide centralized user registry (LDAP)

There are no custom security settings on exposing the Web services, they inherit the Process Agp_ security.

The web services follow their own security model, they do not relate to the Process Ap_p_ security.

There are no security capability features when exposing the BAW capabilities, they should be covered by another secured layer.

Custom security can be set on the webservice and must also comply with the Process Application security.

Roles and teams are two distinct concepts, the same users must be put in Roles and Teams for the behavior to be unified.

A corresponding Group must be created in LDAP that can be used by manually creating a team in the Process Designer application.

A corresponding Team and Group will be automatically created in the local application visible in Process Designer, this Team should then be used in the BPMN flows.

Using the same name for the Role as an existing team in Process designer will automatically map the two entities.

Decision

Rules

Server Script

Gateway