You can create business processes to help automate tasks that need to be performed by application users. A process might include tasks such as reviewing data, approving or rejecting requests, and submitting files.

For example, completing a service or travel request is a process that might have several steps and involve several people. You can create a business process that is automatically initiated when a user submits a travel request in the application. Your process can generate the user tasks, such as getting approvals and submitting documents, and assign them to the appropriate users when they need to be performed. Logged in users might see a list of tasks they need to do or the status of their requests. Employees might see a list of requests that they submitted, and managers might see the requests that they need to approve or reject.

After you create a process in a Process in Oracle Integration application, you can register the process in your visual application and add code to pages in your web (or mobile) application to initiate the process. You can also add process actions to action chains that can be triggered by events in your application.

When adding a business process to an application, you can use business process aliases that are registered on the Process Server.

When you use an alias, the code that you add to the page refers to the alias rather than to a specific version of the process, and you can update the process version without changing the code by updating the alias in the Process Alias editor.

The process must be one that exists on the Processes in Oracle Integration instance.

To add a business process to an application:

1. Open Processes in the Navigator. As soon as you open Processes for the first time, Visual Builder configures a Process Server.

2. Click + Register Deployed Process to open the Register Deployed Process dialog box.

   
   
   
   Description of the illustration process-registration-dialog1.png
   
   

3. Select the process you want to add.

4. Type the alias you want to use for the process, if you want to change it. Click Add.

   
   
   
   Description of the illustration process-registration-dialog-add.png
   
   

5. Repeat steps 2 and 3 to add aliases for more business processes. Click Close when you are finished adding aliases.

The aliases for each of the business processes that you added to your application are listed in the Processes pane. You can select an alias to open it in the editor.

A business process alias points to a revision of a process in a specific Process application registered in a test instance or a production instance.

1. In the Processes pane, open the alias in the Process Alias editor.

   The Process Alias editor's Settings tab contains read-only fields that identify the name of the alias, the Process Application, and the Process Name that the alias points to. The editor's Code Snippets tab shows the code that you will copy into pages in your application.

   
   
   Description of the illustration process-alias-editor.png
   
2. Click the Choose a different process icon () next to the Registered Deployed Process field to select a new process in the Registered Deployed Process dialog box.

   The read-only text field displays the process that the alias points to.

   
   
   Description of the illustration process-alias-editor-detail.png
   

   If you select the Static option when the alias points to a process on a test instance, you will see the following warning: A test instance has been selected. When the application is staged or published, another deployed process will need to be selected. The default is Dynamic.

If you have a configured connection to a Process Server, you can use the Processes menu to navigate directly to your Process instance.

Click the menu and select Design Processes to navigate to the Process Applications tab of Process in Oracle Integration, where you can create, edit, publish, and test processes.

Click the menu and select Manage Processes to navigate to the My Tasks tab of Process in Oracle Integration, where you can complete assigned tasks.

Click the menu and select Test Connection to test the connection to your Process Server.

Description of the illustration process-menu.png

After you create an alias for a business process, you can add the code for the process by copying the process’s HTML and JSON code into the page’s source code in the editor. The Code Snippets tab in the Process Alias editor contains a description and code used for each of the process’s available operations.

1. Open the process you want to add in the Process Alias editor.
2. Click the Code Snippets tab and select the action you want to add.

   When you select an action, the Info tab contains details about the action, including descriptions of objects, and the properties, parameters, and outcomes of actions.

   
   
   Description of the illustration process-alias-code-operations.png
   
3. Click the HTML tab to copy the HTML source for the action.
   
   

   
   Description of the illustration process-alias-code-html.png

   
   
4. Open the page where you want to add the process in the Page Designer.
5. Click Code in the toolbar to open the page’s HTML code in the editor.
6. Paste the HTML code you copied into the page’s HTML editor.

   When you paste the HTML code into the page you might see errors in the editor. The errors should be resolved after you add the JSON metadata.

7. In the Process Alias editor, click the alias' JSON tab to copy the content.
   
   
   Description of the illustration process-alias-code-json.png
   
8. Click the page's JSON tab to edit the page’s JSON file.

   Each page uses a JSON file to describe the page’s metadata, such as the variables and action chains that are defined for the page.

   
   
   Description of the illustration process-alias-paste-json.png
   
9. Paste the JSON metadata for the process into the correct location in the page’s JSON file.

   The JSON metadata for a process might contain definitions for various artifacts, including action chains, variables, and imports. You need to edit the page’s JSON to add the process’s metadata in the correct location. The editor will show warnings and hints in the margins to indicate where there are possible problems with the syntax.

When you are building an action chain in the editor, you can add business process actions to the chain.

1. Open the action chain in the Action Chain editor. Select the component on the canvas.

   Alternatively, you can create a new action chain that is triggered by a component event and add process actions to the chain.

2. Locate the Process category in the Action Chain editor.

   The Process category in the Action Chain editor contains process actions. Each action is described in the Info tab in the Process Alias editor. See Add a Process to a Page.

   
   
   Description of the illustration process-action-chain-editor.png
   
3. Drag the action you want to add onto the Add icon ( ) in the action chain where you want to add the action.
   The following steps apply if you select the Start Process action.
4. Click Select next to Process Interface in the Properties pane.
5. Select the process interface for the business process in the Select Process Interface dialog box. Click Select.

   The Select Process Interface dialog box lets you choose a process alias that you have created or a process definition available on the Process server.

   The business process that you select may have one or more process interfaces. Expand the process node in the dialog box to see the available interfaces.

   
   
   Description of the illustration process-action-chain-select.png
   
6. Specify the interface’s required properties and parameters in the Properties pane.

   Depending on the process interface for the process, you might need to map the interface’s required input parameters to variables.

   
   
   Description of the illustration process-action-chain-properties.png
   

To be able to start a process from Visual Builder, you must configure it in your Process instance to use a Message Start or Form Start event.

You can use the following kinds of start events in Process in Oracle Integration:

• Message Start events with simple type parameters

• Message Start events with complex business type parameters

• Form Start events, which can use a mixture of types as parameters

In Visual Builder, you can map the message parameters to page variables, business objects, or service connection endpoints. You can then set up forms and action chains that execute your processes, and tables or lists that display processes and tasks. An Add Task Actions Quick Start for lists and tables allows you to add components that perform a task.

If you want to display the contents of the message parameters that you specify, you can set up a data association for the message in Process in Oracle Integration and then use it in a description property in the getTask endpoint in Visual Builder.

When developing applications that use business processes, you have considerable flexibility in configuring the settings used to connect to Process Servers and the credentials that are used when communicating with the processes on a Process Server.

Visual Builder automatically sets up a default Process Server configuration when you create an application in Visual Builder. To see the configuration, click the Backends tab in the Navigator's Services tab. In the Backends tab, click Process Applications, then Servers. You'll see a Default Target Server, which in development mode, is configured to point to a test environment on Processes in Oracle Integration instance.

Description of the illustration process-services.png

When a Process-related interaction occurs (say, you clicked Processes in the Navigator and tried to register a process, or used a Process Quick Start), the Tenant settings are overridden and you'll see another target server, the Player Target Server, as shown here:

Description of the illustration process-services-vbs.png

The Player Target Server is useful when you want to "play" the process for testing, without making it live to your users.

The target server is set up in a default Application Profile. For basic information on Application Profiles, see What Are Application Profiles?

When you click the Application Profiles tab under Settings, you can see a base configuration that is set up to use the Player Target Server. This configuration is the default for the publishing, staging, and development phases of application development.

Description of the illustration process-app-prof.png

Once you finish developing your application, you'll want to duplicate the base configuration, rename it, and specify the use of the Default Target Server instead of the Player for the staging and/or publishing phases. To do this:

1. Click the Duplicate button and specify a new Name and ID (for example, Publish).
   
   
   Description of the illustration process-app-prof-dup.png
   
   
2. Click the Publish configuration and select Default Target Server from the drop-down list. By default, an application profile is always connected to the Player Target Server to avoid accidentally kicking off a live process.
3. From the configuration's Options menu (), select Make stage default or Make publish default.
   
   
   Description of the illustration process-app-prof-def.png
   
   

For each Process Server configured, like the Player Target Server and the Default Target Server, you can specify an authentication mechanism.

For example, you may want to specify basic authentication for development and testing, and the user's Oracle Cloud Account for the published app.

To specify authentication:

1. Click the Services tab under Settings (if you aren't already in Settings, select Settings from the top right menu).

2. Click the Edit icon next to the target server you want to edit.

3. In the Edit Server dialog box, select the authentication mechanism you want to use for that server from the Authentication drop-down list. The list has several choices, but for processes only Oracle Cloud Account and Basic are supported.

   
   
   
   Description of the illustration process-auth-edit.png
   
   

4. Click Save.

At any stage of development, a developer can choose to enable Basic Authentication and provide the credentials of a user registered on the Process server. Selecting Basic Authentication enables the developer to log in to the Process server as a different user and access processes that they would not be able to otherwise. When selected, the developer can provide the credentials of different users to access the processes available to that user. These credentials and Basic Authentication are not used when the application is staged or published.

Selecting Test Connection in the options menu for the Processes navigator will by default use Oracle Cloud Account authentication details to test the connection. This means that to test the connection your user credentials must be valid to access the Process Server.