Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# TIBCO iProcess® Workspace

TIBCO iProcess Workspace contains the following components that allow users to initiate and interact with business processes that have been deployed to iProcess Engine for execution:

| • | TIBCO iProcess® Workspace (Windows)

| • | TIBCO iProcess® Workspace (Browser)

| • | TIBCO iProcess® Workspace Lite

| • | TIBCO iProcess® Server Objects (for Java and .Net)

| • | TIBCO® Multilingual User Interface (MUI)

Each user has a named user license to iProcess Workspace and is entitled to any number of its constituent components. This will enable the user to participate in the business process executed by iProcess Engine.

For example, a user can use either the Windows or the Browser client of TIBCO iProcess Workspace to achieve the same result. Depending on the end-user environment, you can use iProcess Workspace (Windows) in main office and iProcess Workspace (Browser) when working remotely. The examples provide an overview of how some of the different iProcess Workspace components can be used by users.

## TIBCO iProcess Workspace (Windows)

The following image represents how users connect to iProcess Engine using iProcess Workspace (Windows). The users can access iProcess Workspace (Windows) locally on their computer using the unique iProcess user ID and password assigned to them.

## TIBCO iProcess Workspace (Browser)

The following image represents how users connect to iProcess Engine using iProcess Workspace (Browser). This depends on how the solution designers and developers have designed the framework for iProcess. The following examples illustrate different ways in which iProcess Workspace can be used.

In this example, iProcess Workspace (Browser) is used unmodified.

## Example 1 - Custom UI for iProcess Workspace (Browser)

In this example, the solution designers and developers replace the iProcess Workspace (Browser) user interface with a custom application developed by them. Nevertheless, the Action Processor API provided as part of iProcess Workspace (Browser) is still used. See the following diagrammatic illustration:

## Example 2 - Custom Client using iProcess Server Objects

As the title suggests, the solution designers and developers replace iProcess Workspace (Browser) with a custom application that uses iProcess Server Objects to access the BPM functionality provided by iProcess. See the image:

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.