Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

TABLE OF CONTENTS

Install Client on Windows Form Based Application

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 01, 2024
  • 2 minute read

Client Installation on Windows

You can install the client and enable AVEVA Work Tasks functionality on a Windows Form-based application.

In a typical Server and Client installation, the Server Controls are used from the Enterprise Console Web Site. These Server Controls are by default implemented within the Enterprise Console Web site. For more information about the Server Controls, see Architecture.

Windows Form-based applications run on standalone systems and do not require Web browsers. In a Windows Form-based environment, AVEVA Work Tasks functionality can be implemented using two approaches.

The first approach is to embed the Server Controls through a browser control within the Windows form. This is similar to using a Web application in which AVEVA Work Tasks is implemented. The alternative approach is to use AVEVA Work Tasks run-time functionality using AVEVA Work Tasks APIs. However, the APIs can be used only with run-time functionalities. The design time functionalities such as defining a Queue, a Calendar and designing the process using process designer will not be possible with the APIs. The run-time APIs include:

  • Getting information of a task or a work item getting assigned to a user, based on the defined process

  • Taking action on a task or a work item. For example, approving or rejecting a task.

The following scenarios describe two distinct ways of integrating Windows form-based clients using AVEVA Work Tasks run-time API.

Scenario 1

In this scenario, the Client is installed on the same machine where the Windows form-based client is running. The number of the Client installation required will be equal to the number of Windows form-based applications. The Windows form-based applications make use of AVEVA Work Tasks run-time APIs to communicate with the Client.

Example

A machine with 10 windows form-based applications will require 10 Client installations.

Scenario 2

In this scenario, Windows form-based application will interact or communicate with a single Client using Web service calls. The AVEVA Work Tasks run-time APIs will be implemented within this Web service calls. This Web service is not a part of the Client installation. This is the most preferred approach as the the Client is installed only on one machine.

Example

A machine with 10 windows form-based applications will require a single Client installation.