Getting Started with Sample Applications

Getting Started with Sample Applications

Document Version 1.2

Date: 28th August, 2012

Page 2

Table of Contents

INTRODUCTION .........................................................................................................................................3
Benefits of ArchestrA Workflow Software ............................................................................................................... 3
INTRODUCTION TO BUSINESS SCENARIOS ....................................................................................4
Escalating an Alarm for High Reactor Level ............................................................................................................ 4
Spillage – Drum Fall Event ....................................................................................................................................... 4
Changing the SetPoint Level Of Batch Concentrate ................................................................................................ 4
Executing Spillage – Drum Fall Event Sample Application using Work Tasks ....................................................... 4
PRE-REQUISITES FOR EXECUTING THE SAMPLE APPLICATIONS ..........................................5
GRAPHICAL REPRESENTATION OF EXECUTING SAMPLE APPLICATIONS ..........................6
IMPORTING REPOSITORY DATABASE AND ARCHESTRA GALAXY.........................................7
Importing Repository Database................................................................................................................................. 8
Importing ArchestrA Galaxy................................................................................................................................... 17
WORK TASKS CONFIGURATION AND INSTALLATION ...............................................................33
Introduction ............................................................................................................................................................. 33
Pre-requisites ........................................................................................................................................................... 34
Steps for Configuring and Installing Work Tasks ................................................................................................... 35
1. Activating Mobile User Pack License .......................................................................... 37
2. Creating Enterprise Console with Anonymous Authentication ....................................... 46
3. Configuring ArchestrA Mobile Notification Service Settings ........................................... 54
4. Add Users with Mobile License ................................................................................. 62
5. Set Delivery Channel in the Workflow ....................................................................... 65
6. Installing and Configuring Work Tasks ...................................................................... 67
Page 3

Introduction
This document provides detailed steps to get started and learn how these sample applications help you to
use the ArchestrA Workflow Software, System Platform and InTouch applications to improve your
business by automating the process of handling critical scenarios.

The robust and complex processes on the plant floor can be managed using ArchestrA Workflow
Software. This embeds the workflow capability into applications that translate real-time business events
into actionable information.

In a plant floor, there may be scenarios leading to critical events like spillage of hazardous material,
change in batch concentrate value, or high reactor level. ArchestrA Workflow Software translates these
events into information which is communicated to the respective personnel for appropriate action to be
taken.

Benefits of ArchestrA Workflow Software

 Ability to span across levels. An event occurring at Level 1 (controls) requires interaction at Level
2 (supervisory) and spans actions at Level 3 (advanced applications).
 Centralized management of processes for enterprises
 Automates the process of handling critical processes
 Reduces human errors
Page 4

Introduction to Business Scenarios

Given below are three typical business scenarios, based on which the sample applications have been
designed. These sample applications are built on the ReactorDemo sample of System Platform.

Escalating an Alarm for High Reactor Level

ArchestrA Workflow Software and InTouch can be integrated to alert the supervisor and obtain required
acknowledgement when the reactor level exceeds a certain limit.

Whenever the reactor level exceeds the set limits, the InTouch application raises an alarm. If the alarm is
not acknowledged within two minutes, a workflow is triggered using the ArchestrA Workflow Software.
This workflow assigns a task to the supervisor for an appropriate action to be taken. The supervisor
acknowledges the task.

Spillage – Drum Fall Event

ArchestrA Workflow Software and InTouch can be integrated to notify the supervisor when the Drum
falls off the conveyer belt.

When the drum falls, a workflow is triggered; this informs the operator that a drum has fallen. The
operator can inspect the situation and capture the observation / reason in the Workflow system. Supervisor
is then notified about drum fall event and the observation made by the operator.

Changing the SetPoint Level Of Batch Concentrate

ArchestrA Workflow Software and InTouch can be integrated to monitor the changes done to the SetPoint
level of Batch Concentrate and obtain required approvals.

When changes are done to the SetPoint level of Batch Concentrate and it exceeds the acceptable limit,
appropriate approvals are required. ArchestrA Workflow Software automates this process and the System
Platform triggers the workflow when the SetPoint value is changed and the difference between the new
value and the pre-defined value is greater than or equal to 10. Once the workflow is triggered, further
changes to the SetPoint value cannot be made unless the approval is obtained. ArchestrA workflow
assigns a task to the supervisor intimating the change in value. This can either be approved or rejected by
the supervisor.

Executing Spillage – Drum Fall Event Sample Application using Work Tasks
The Drum Fall Spillage sample application can now also be executed using Work Tasks – the mobile
application for ArchestrA Workflow Software. The operator and supervisor will be able to receive and act
on Drum Spillage notifications while on the move. This would ensure timely approval and action in the
case of hazardous drum spillage event.

For enabling mobile services for ArchestrA Workflow Software and configuring Work Tasks, refer
section Work Tasks Configuration and Installation.
Page 5

Pre-Requisites for Executing the Sample Applications

 ArchestrA Workflow 2012 SP1 needs to be installed.

 System Platform 2012 needs to be installed.

 InTouch 2012, version 10.5 needs to be installed.

 Importing Repository Database (WorkflowExampleDSDB.bak) and ArchestrA Galaxy

(ArchestraWorkflowSoftware.cab)

Note: Upgrading from previous versions of the demo is not supported. The user is advised to
import the repository database into to a new environment.
Page 6

Graphical Representation of Executing Sample Applications

Page 7

Importing Repository Database and ArchestrA Galaxy

The sample applications require a set of initial steps to be performed. These initial steps help you to
restore a predesigned galaxy and repository database which contain configured workflows and workflow
gateway objects.
Page 8

Importing Repository Database

To restore the repository database, you require WorkflowExampleDSDB.bak file. This file is present in
the „ArchestrA Workflow Software Demo and Example Content‟ folder in the installation CD.

Prerequisites to import repository database:

To begin with, restore the repository database in a new environment of the Workflow server. Follow the
steps given below:

a) Go to All programs > Microsoft SQL Server > SQL Server Management Studio and connect
to the Database Engine.

b) In the Object Explorer, go to the Database.

c) Right-click the Database and select Restore Database from the context menu to restore
“WorkflowExampleDSDB.bak” file.

d) In the Restore Database screen, enter „WorkflowExampleDSDB‟ in the „To database‟ field.

e) In the “Source for restore -> From device” section browse for the file
“WorkflowExampleDSDB.bak” available under „ArchestrA Workflow Software Demo and
Example Content‟ folder in the installation CD.

f) Check the „Restore‟ option under „Select the backup sets to restore‟ and click „OK‟.
Page 9
Page 10

Steps to create datasource and repository:

 Creating a Datasource

 Creating a Repository and Configuring the Administrator

 Verifying Workflow List

Page 11

Creating a Datasource

1. Navigate to Skelta Central Configuration and click Datasource Settings.

2. In the Datasource List, click Create Datasource.

Page 12

3. The Manage Datasource screen appears. Enter the information as shown below and click Test
Connection. Ensure that the restored database is selected for the Database value.

 Name: WorkflowExampleDS

 Description: <<Description>>

 Server Name: <<Server Name>>

 Authentication: <<WINDOWS>> OR <<SQL Server>>

 Database: Refresh the database and select the Repository Database

WorkflowExampleDSDB from the drop-down list. User can also add
„WorkflowExampleDSDB‟ manually.
Page 13

4. A message „Test connection succeeded…‟ is displayed when the connection is successful. Click
OK.

A message „Datasource entry created in Skelta Farm ….‟ is displayed and the new data source is
created.
Page 14

Creating a Repository and Configuring the Administrator

1. Navigate to Central Configuration > Repository Settings. The Repository List is displayed.
Click Create Repository.

2. The Manage Repository screen is displayed. Enter the information given below:

 Select the appropriate data source (WorkflowExampleDS) and select the Attach
Datasource check box.

 Enter the Repository Name (Workflow Examples Repository).

 Enter Description.

 Select the server in the Servers Mapped field. The default Enterprise Console link
appears.

 Click OK.
Page 15

3. The Config Administrator screen is displayed.

 Select “admin [Skelta List]” through the User Lookup. The user admin is configured as
the administrator user for Skelta Enterprise.

 Click OK to complete.

 If the “admin[Skelta List]” option is displayed by default, just click OK.

4. Navigate to Repository List and click on Site Path URL to open the Enterprise Console.
Page 16

Verifying Workflow List

1. In the Enterprise Console, click Skelta List of the Workflow Examples Repository.

2. Login to the repository using these credentials User ID: admin and Password: admin.

3. Navigate to Enterprise Console > Workflows. In the Workflow list, verify if the following
workflows are displayed.

 ReactorHiAlarmWF

 Hazardous Spills Workflow

 SetPoint Change Workflow

By performing the above steps, you will successfully import the repository database.
Page 17

Importing ArchestrA Galaxy

To import the ArchestrA Galaxy, the ArchestraWorkfowSoftware.cab file is required. This file is present
in the „ArchestrA Workflow Software Demo and Example Content‟ folder in the installation CD.

Steps to import ArchestrA Galaxy:

 Creating and Verifying New Galaxy

 Restoring and Undeploying the Galaxy

 Authorizing and Provisioning the Workflow Gateway Object

 Deploying the Workflow Gateway Object

 Verifying the Galaxy User in the Enterprise Console

Page 18

Creating and Verifying New Galaxy

1. Create a new Galaxy using the ArchestrA IDE.

 Click New Galaxy.

 In the New Galaxy popup window, specify the Galaxy Name as

“ArchestraWorkflowSoftware”. (This name should be the same as the Galaxy backup
cab file.)

 Click Create.

2. The Create Galaxy dialog appears. When the Galaxy is successfully created, click Close.

3. Verify if the Galaxy Name is “ArchestraWorkflowSoftware.”

Page 19
Page 20

Restoring and Undeploying the ArchestrA Galaxy

1. Navigate to Start > Run > type aaSMC and click Enter.

2. The ArchestrA System Management Console appears. Expand the Galaxy Database Manager.

3. Select the galaxy and right-click to select the Restore option.

Page 21

4. The Galaxy Database Manager appears. Click Yes to proceed.

5. Navigate to the ArchestraWorkflowSoftware.cab backup file copied from the installation folder
„ArchestrA Workflow Software Demo and Example Content‟ and click Open.
Page 22

6. Close the Galaxy Database Manager after the restore is successful.

7. After restoring successfully, access ArchestrA IDE Login.

 User name: Lenka

 Password: lenka

 Domain: no selection required

 Click OK
Page 23

8. Change the GR_Platform network address to the actual GR address of the environment. Click
Save and close the window.
Page 24

Authorizing and Provisioning of Workflow Gateway Object

1. Open the base Workflow Gateway Object (WGO) Template ($aaRectorDemoWFGateway) to

Authorize and Provision.

 Specify Server Address

 Specify Authentication User Domain

 Specify Authentication User Id

 Specify Authentication User Password

 Click Test Connection

2. When the message Test Connection Successful appears:

 Select Repository Name as “Workflow Examples Repository”

 Specify Workflow Examples Repository Authentication (Provision) Info:

o Providers: Skelta List

o User Name: admin

o Password: admin
Page 25

 Specify Inbound Connection Authentication Info:

o Specify Authentication User Domain

o Specify Authentication User Id

o Specify Authentication User Password

Page 26

3. Click Authorize & Provision. The message “Connector provisioned successfully…” appears.

4. To check-in the Workflow Gateway Object, save and close it.

5. Click Close once the check-in is complete.

Page 27

Deploying the Workflow Gateway Object

1. After re-provisioning the WGO, deploy the entire platform. Right-click the GR_Platform and
Deploy.

2. The Deploy screen is displayed. Click OK without changing the default options.
Page 28

3. Click Close after successful deployment.

4. Navigate to Galaxy menu > Configuration > Security and verify if the Authentication Mode is
“Galaxy”.

5. Navigate to Users tab and verify the Authorized Galaxy Users as shown in the image given below.
Page 29

6. To verify Workflow association to the event, go to Derivation Tab > ArchestraWorkflowSoftware

> $UserDefined > $UserDefined_P > $ReactorSet.Reactor.

In the Workflows tab, verify the associated workflows of the respective instance.

Note: Reset IIS if the Workflows do not appear.

Page 30

Verifying Galaxy User in Enterprise Console

1. To login as Galaxy User using Enterprise Console site, navigate to Repository List and click the
Site Path URL.

2. The Enterprise Console page is displayed. Ensure that Galaxy User

[ArchestraWorkflowSoftware] links appear as shown below:

3. Click Galaxy User [ArchestraWorkflowSoftware] and login using these credentials User Id:
Lenka and password: lenka. This is to verify if Galaxy users are able to login to Enterprise
Console.
Page 31

4. Navigate to Start > Run > type Services.msc and click the Enter button. Verify if all the
Workflow services are running.
Page 32

Note: Check whether the services are running. If not, then right-click the respective services and
click the Start option.

5. Copy the “Pics” folder from „ArchestrA Workflow Software Demo and Example Content‟ folder
in the installation CD to “..\Program Files\Skelta\BPM.NET\Web\BPMUITemplates\” and
“..\Program Files\Skelta\BPM.NET\Web\BPMUITemplates\Default” folder.

The above steps restore the galaxy successfully. You can now execute the demos listed below:

 Escalating an alarm for High Reactor Level – Reactor Alarm.pdf

 Spillage Drum Fall Event – Spillage Drum Fall Event.pdf

 Changing the SetPoint Level of Batch Concentrate – SetPoint Change.pdf

Page 33

Work Tasks Configuration and Installation

Introduction
This section provides detailed steps to configure and install Work Tasks – the mobile application for
ArchestrA Workflow Software. With Work Tasks, the operator can receive and act on the Drum Spillage
notification from his mobile device. Also, the supervisor will be able to approve or reject the observation
made by the operator on his mobile device.

Work Tasks is designed for professionals who use a mobile phone or a tablet device to access work tasks,
while on the move. It is an easy-to-use application that provides a quality visual experience.

Capabilities:

 View and act on work tasks from the mobile devices

 Fill Form and initiate a process

 Receive notifications when a new work task is assigned

 Search for specific work tasks

 Flag work tasks based on importance

 View work tasks based on categories

 View work tasks even in offline mode

The following sections give a detailed explanation of the various steps involved in the configuration and
installation of Work Tasks.
Page 34

Pre-requisites
Following are the pre-requisites for installing and accessing Work Tasks on your mobile device.

Software Requirements

In order to successfully configure and use Work Tasks, ArchestrA Workflow Software SP1 must be
installed on your system.

Hardware Requirements

Work Tasks application runs on iOS 5.1 operating system. The hardware requirement comprises of an
iPhone or an iPad on which the application can be installed.

Other Requirements

 Core product license key with mobile users or Mobile User Pack license key

 If you wish to receive Push Notification for Work Tasks, you would require Internet Connectivity
to connect to Windows Azure.
Page 35

Steps for Configuring and Installing Work Tasks

Follow the steps given below for enabling mobile services for ArchestrA Workflow Software and
configuring Work Tasks:

1. Activate the Mobile User Pack License if mobile user license is not embedded in core product
license. The Mobile User Pack License can be activated using the following two methods:

 Using Farm Configuration Wizard

 Using Command Prompt

For details, click here.

2. Create an Enterprise Console with anonymous authentication that specifically caters to the mobile
services.

For details, click here.

3. If Push Notification functionality has been enabled for Work Tasks, the user needs to configure
ArchestrA Mobile Notification Service (AMNS) Settings. AMNS can be configured from
ArchestrA Mobile Notification Service option available in the Skelta Farm Configuration Wizard -
> Service Settings -> Services/Global Settings screen.

For details, click here.

4. Manage Mobile Users and Licenses

 Add mobile users using the View/Manage Mobile Users and Licenses option in the Skelta
Central Configuration screen.

For details, click here.

5. Set Delivery Channel

 Enable the MobileWorkList option in the Delivery Channels of the Human Activities, so
that the workflow delivers the work item to the mobile device.

For details, click here.

6. Configure the settings for Work Tasks in your mobile device

Page 36

 Enter the Enterprise Console URL, Repository Name, Provider Name, User Name and
Password. Click Save. This would download the work items assigned to the user in the
mobile Inbox.

For details, click here

Page 37

1. Activating Mobile User Pack License

A mobile license is mandatory for the user to connect to the workflow repositories through Work
Tasks. When the mobile user license is embedded with the core product license, it does not require
separate activation as it gets activated along with the core product.

However, if mobile user pack license has been bought explicitly, it needs to be activated. The
mobile user pack license can be activated using the following two methods:

Using Farm Configuration Wizard

This topic provides steps to activate Mobile User Pack license using Farm Configuration Wizard.

Note: Users should ensure the Mobile User Pack license is activated on the engine server as well
as Advanced server.

a. Open the Skelta Farm Configuration wizard.

b. Click the Next button to go to the Edit Skelta Farm Settings screen.

c. In this screen, click the Activate Skelta Keys link.

Page 38

The Activate Skelta Keys screen appears.

d. In the Activate Skelta Keys screen, select the Skelta BPM.NET - Mobile User Pack option
from the Key Type drop-down list.
Page 39

e. Type in the license key in the Key fields.

f. Click the Activate button.

Page 40

g. Click the Activate Now button.

Page 41

h. Close the screen to complete the activation steps.

Page 42

Note: Multiple Mobile User Pack Licenses can be activated. Even for multiple activations, the
user must select the Skelta BPM.NET - Mobile User Pack key type. However, individual
activations will be incremented with a sequential number and will be listed in the drop-down list
of the Key Type field. Refer to the image given below:

Using Command Prompt

This topic provides steps to activate the Mobile User Pack license using the command prompt.

a. Open the command prompt and go to <Skelta_Installed_Path>\BIN folder.

Page 43

Skelta_Installed_Path is the path where Skelta BPM.NET is installed on your system.

b. Type LicenseManager.NET2 /serial:<serial key> /app:U2 and press Enter.

c. Type LicenseManager.NET2 and press Enter to execute the command.

d. Click the Activate Now button to activate the license. Wait till you get a message confirming
successful activation.
Page 44

e. Close the screen to complete the activation steps by clicking the Close button.
Page 45
Page 46

2. Creating Enterprise Console with Anonymous Authentication

In order to successfully configure and use Work Tasks, it is recommended to create a new
Enterprise Console (EC) site that specifically caters to the mobile services. This EC must be of
anonymous authentication type and should not be localized as Work Tasks supports only English.

The Skelta Farm Configuration Wizard allows you to create a new Enterprise Console site.

a. Click Start.

b. Point to Programs > Skelta > Skelta BPM.NET.

c. Click Skelta Farm Configuration Wizard. The Welcome to the Skelta Configuration Wizard
appears.
Page 47

d. Click Next. The Edit Skelta Farm Settings window is displayed.

Page 48

e. Select Service Settings.

f. Click Next. The Services/Global Settings page is displayed.

Page 49

g. Click against Enterprise Console option. The Enterprise Console Settings page is
displayed. Click New EC.
Page 50

h. In the New Website text box, enter a name for the Enterprise Console. For example, enter
name as 'MobileEC'.
Page 51

i. The mapped repositories are displayed in the Repositories. Select the repository(s) to map to
this created site as shown below. You can select multiple repositories by using Ctrl or Shift
keys.

j. Select the required authentication type as Anonymous in the Authentication Type drop down
field.
Page 52

k. Click Save. The created Enterprise Console site is displayed in the Existing Enterprise
Consoles section. Click OK.
Page 53

l. Before you click Finish, it is recommended to restart all services using the icon in the
Services/Global Settings screen of the Skelta Farm Configuration Wizard screen. A pop-
up message “Successfully restarted services” appears.

m. Click Finish in the Skelta Farm Configuration Wizard screen.

Page 54

3. Configuring ArchestrA Mobile Notification Service Settings

This service handles registrations to ArchestrA Mobile Notification Service and also ensures
reliable delivery of notification to Work Tasks.

Note: This configuration is required only when the Push Notification functionality is enabled for
Work Tasks.

Follow the steps given below:

a. Open Skelta Farm Configuration Wizard. Click Next.

b. Select the Service Settings to open the Services/Global Settings screen. Click Next.

c. Click against ArchestrA Mobile Notification Service to configure the service to open
the ArchestrA Mobile Notification Service Settings screen.
Page 55

d. Configuration Settings of ArchestrA Mobile Notification Service:

The ArchestrA Mobile Notification Service Settings dialog has two tabs which enables you
to register and configure this service. The section below gives you detailed explanation on
the configuration settings.

Register

Configuration in this tab manages the registration to ArchestrA Mobile Notification

Service. On registering to this service, notifications are sent to the mobile device. User can
also re-register to ArchestrA Mobile Notification Service when the client id/machine id has
been changed.
Page 56

Field Name Description

Client Id This is a read-only field that is auto-populated with the product key used
while installing the core BPM.NET product.

Machine Id This is a read-only field that is auto-populated with the Machine ID on

which the product is installed.
Page 57

How to Register to ArchestrA Mobile Notification Service?

a. Access Skelta Farm Configuration Wizard.

b. Navigate to ArchestrA Mobile Notification Service Settings > Register tab.

c. The fields Client Id and Machine Id are auto-populated. Click Register.

A message registration successful appears.

d. Click OK. The Registration Details are auto-populated as shown in the image below:
Page 58

Notification Delivery

Configuration in this tab ensures reliable delivery of notifications to Work Tasks, even when there is a
connectivity failure in the Enterprise Console on which the workflow was triggered.
Page 59

Field Name Description

Message Life Time

Retry Count Number of re-tries that needs to be attempted to send the

notification.

If the Retry Count value is set as 0, the failed notifications

will not be resent.

Scheduling Period

Enter polling cycle Based on the time specified here the ArchestrA Mobile
Page 60

Notification Service will look for an entry in the

SKNotificationMessage table. If an entry is found in the table
then a notification will be sent to the mobile device.

The time entered should be in days.hr:min:sec format only.

The maximum limit is 10 mins.

Advanced Server Settings

This tab is enabled only in advanced server mode. Configuration in this tab manages the load balance on
the Server and Client.
Page 61

Field Name Description

ArchestrA Mobile Notification Service Settings

Load Balanced This field is used to set load balancing for BPM.NET. This field is enabled
only for BPM.NET Advanced Server Edition installation.

To enable load balancing set the Load Balanced value to True.

Load Balanced This field allows you to enter the port number for the Load Balanced
Server Port Server.

This field is disabled if Load Balanced is set to False.

Load Balanced This field is used to enter the port number for the Load Balanced Client.
Client Port
Page 62

4. Add Users with Mobile License

This topic gives detailed steps to add new mobile users Kevin (operator) and Michelle (supervisor):

a. Click View/Manage Mobile Users and Licenses in the Skelta Central Configuration screen.

b. Click the link Activate/Deactivate Mobile Users under Activate/Deactivate Mobile Users for
Repositories.

c. Select the Workflow Example Repository from the drop-down list in the Repository Name
field.

d. Select the Add User(s) action type and click Go. The Add/Activate Users for Mobile section
appears.
Page 63

e. In this section, click the user lookup icon . Select Galaxy

User[ArchestrAWorkflowSoftware] in the User-based Advanced Search in provider drop-
down.

f. Search for user Kevin. The user Kevin appears in the Available Resources field. Click icon
to move Kevin to the Selected Resources field.

The selected user appears in the Selected Resources field. Click Update.

g. Click Add to add the new mobile user. The confirmation message appears as shown below:

h. Click OK. Repeat steps d-g to add and activate another mobile user Michelle.
Page 64

i. The new mobile users Kevin and Michelle are added to the list of active mobile users as shown
below:
Page 65

5. Set Delivery Channel in the Workflow

The Delivery Channel property in Human Activities has to be set to send the tasks to the recipient
through different modes of delivery like mail, web, and mobile. In order to send the tasks to the
mobile device, the MobileWorkList option in the Delivery Channel property needs to be selected.
This allows mobile users to view and act upon the tasks from Work Tasks. This option is available in
three of the Human activities - Approval, Information, and Invoke Form.

This topic describes the steps required to configure the MobileWorkList option in the Delivery
Channel property of the human activities.

Configuring 'MobileWorkList' option in the Delivery Channels Property:

a. Login as Lenka (User Id: Lenka and Password: lenka) in Skelta Enterprise Console using Galaxy
User link.

b. From the Enterprise Console pull down menu select Workflows. The Workflows list appears.

c. Right click Hazardous Spills Workflow and select Unpublish.

d. The Workflow Process Designer screen appears.

e. The workflow gets unpublished. Click Edit in the ribbon bar to open the workflow in the Process
Designer.

f. In the Process Designer, perform the steps given below for SendFormToOperator,
EscalateToSupervisor, SendFormToSupervisor, InformOperatorOfReject, and
SetSupervisorFeedback human activities:

i. Right-click the activity and the properties pane appears on the right side of the design area.

ii. In the Activity Properties pane, expand the Configuration node and select the Delivery
Channels property.

iii. In the Delivery Channels window, select the MobileWorkList check box in the Channels
section.
Page 66

iv. Click Save Channels.

v. Right-click and Publish the workflow.

This enables the activities to deliver the task to the Inbox in the mobile devices.
Page 67

6. Installing and Configuring Work Tasks

This topic gives you step by step instructions to install and configure Work Tasks.

Steps to Install Work Tasks

a. Download Work Tasks from App Store. You can see the Work Tasks icon on your device
screen.

Note: While downloading, you might receive an alert asking you to enable the Push
Notification on your mobile device. Enable these settings to receive notifications about the
work tasks on your mobile devices. If this is not enabled at this stage of installation, you may
not be able to receive any notifications even if the notification settings are configured. You
might have to reinstall the application to enable the Push Notification.

b. Before viewing the Work Tasks Inbox, you need to configure the settings for this
application. These settings are required to establish a connection with the Enterprise
Console, Repository, and Provider etc., to fetch the work items from the Skelta workflow.
Given below are the steps to configure the settings:

Steps to Configure Work Tasks

a. Launch Work Tasks on your device. You can click the Settings icon given in the
footer of this application to go to the Settings screen.
Page 68

 Connection

Name: Enter a name for the connection, say Sample Application

Description: Enter a suitable description for the connection.

 Server Details:
Page 69

URL: Enter the Enterprise Console intranet URL created with Anonymous Authentication in
URL field of Work Tasks. Refer section 2. Creating Enterprise Console with Anonymous
Authentication for more details.

Repository: Select Workflow Examples Repository from the drop-down list.

Provider Name: Select Provider Name as Galaxy Users[ArchestraWorkflowSoftware]

If the user is logging in as operator, then
User Id: Kevin
Password: kevin
If the user is logging in as supervisor, then
User Id: Michelle
Password: michelle

 Storage Details:

No. of Items: Select the number of items to be stored in the Inbox. Select the number of items
to be stored in the Inbox. The minimum number of items to be specified is 20. The Inbox can
store a maximum of 99 work items for a given connection.

 Save: Once you specify all the details in the Settings Configuration page, click the Save
button to save the configuration.

b. Upon saving the configuration, the Inbox screen with all the assigned work items appears on your
mobile device. Click on the task to open the details page and act on it.
Page 70