Discover the options available for integration between K2 and Blue Prism, for both inbound and outbound communication that allows you to make calls from K2 (via SmartObjects) to start processes in Blue Prism and how make calls from Blue Prism interact with K2 forms and workflows.
K2 requirements include:
Blue Prism requirements include:
In addition to the above requirements, you must have a basic understanding of SOAP and REST-based web services.
Use the following diagram for understanding how K2 and Blue Prism communicate with each other.
Use the following scenarios for the type of integration you need between K2 and Blue Prism.
Scenario 1: Use the Endpoint Web Service to Call Blue Prism Processes and Objects
Enable the SOAP-based Blue Prism web services, and then create a K2 service instance and SmartObjects that interact with the Blue Prism services. Use these SmartObjects in a SmartForm or workflow to make calls from K2 to Blue Prism.
Scenario 2: Use the Workflow REST API to make calls from Blue Prism to K2
Use Blue Prism VBOs to call the K2 Workflow REST API to start or action K2 workflows from Blue Prism.
Scenario 3: Use K2 SmartForms and SmartObjects as a Replacement or Extension of Blue Prism
Use the Blue Prism Application Modeler to start and interact with K2 workflows and SmartObjects through a form.
You can interact with Blue Prism through SOAP-based web services by first enabling them in Blue Prism and then creating a service instance and SmartObjects in K2.
Test the service you created in Step 1 by following these steps.
Use the Endpoints WebService service type to create a service instance that connects to Blue Prism using SmartObjects.
Blue Prism communicates with REST APIs using Virtual Business Objects (VBOs). Native support for REST APIs is not included in Blue Prism at the time of this article's publication. Talk with a Blue Prism subject matter expert with experience in authoring VBOs to help you set up this scenario.
There are many out-of-the-box examples with Blue Prism, including one that uses REST.
You must enable the K2 REST API before configuring Blue Prism.
For more information about working with the Workflow REST API, see the K2 Cloud and K2 Five Developer Reference content.
In Blue Prism, create a VBO that calls the K2 REST API. (The example shown below is available to download, see the links on the right-hand side of this page).
Another option for working with K2 from Blue Prism is using K2 forms to control a Blue Prism robot. Blue Prism enables interacting with forms and programs as part of their Application Modeler functionality.
Using Application Modeler, you could configure Blue Prism to start and interact with K2 workflows and SmartObjects through a form. In this way, the VBOs that you create could be leveraged by more people developing solutions with K2.
The integration path that you choose to integrate K2 and Blue Prism depends on the needs of your solution. While the VBO path provides the potential for a more generic, reusable integration that can be created with a certain amount of resilience built in, using a K2 form can be a viable option for scenarios where project scope or resource availability require a different approach.