+ All Categories
Home > Documents > IBM OpenPages GRC Version 7.3.0: Workflow Author's...

IBM OpenPages GRC Version 7.3.0: Workflow Author's...

Date post: 20-Jan-2021
Category:
Upload: others
View: 16 times
Download: 0 times
Share this document with a friend
75
IBM OpenPages GRC Version 7.3.0 Workflow Author's Guide IBM
Transcript
Page 1: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

IBM OpenPages GRCVersion 7.3.0

Workflow Author's Guide

IBM

Page 2: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

NoteBefore using this information and the product it supports, read the information in “Notices” on page 53.

Product Information

This document applies to IBM OpenPages GRC Version 7.3.0 and may also apply to subsequent releases.

Licensed Materials - Property of IBM Corporation.

© Copyright IBM Corporation, 2003, 2016.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Page 3: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vThe Interstage BPM application and IBM OpenPages GRC Platform . . . . . . . . . . . . . . . . . v

Interstage BPM Studio features not supported in OpenPages GRC Platform . . . . . . . . . . . . . viInterstage BPM Studio online help . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTerms you should know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiProcess definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiOnline and offline editing modes . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWorkflowAdministrators group . . . . . . . . . . . . . . . . . . . . . . . . . . . . xWorkflow life cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Getting started with Interstage BPM Studio . . . . . . . . . . . . . . . . . . . . . . . . . xStarting the Interstage BPM application . . . . . . . . . . . . . . . . . . . . . . . . . xiInterstage BPM Studio workbench window . . . . . . . . . . . . . . . . . . . . . . . . xiProcess definition elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiInterstage BPM Studio features supported in IBM OpenPages GRC Platform . . . . . . . . . . . . xv

Chapter 1. Authoring workflows . . . . . . . . . . . . . . . . . . . . . . . . . 1Creating a process definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Creating an application project and process definition name . . . . . . . . . . . . . . . . . . 1Creating a server project for the process definition. . . . . . . . . . . . . . . . . . . . . . 2Building the process definition and adding properties . . . . . . . . . . . . . . . . . . . . 3

Uploading a process definition to IBM OpenPages GRC Platform workflow server . . . . . . . . . . . . 5About draft version numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Connecting to the OpenPages GRC Platform server . . . . . . . . . . . . . . . . . . . . . . 5Associating a process definition with an object type . . . . . . . . . . . . . . . . . . . . . . 6Adding Java actions to a process definition . . . . . . . . . . . . . . . . . . . . . . . . . 8Publishing the process definition to OpenPages GRC Platform. . . . . . . . . . . . . . . . . . . 9Editing published process definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Copying and deleting application projects and process definitions . . . . . . . . . . . . . . . . . 11

Copying an application project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Copying a process definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Deleting a project or process definition . . . . . . . . . . . . . . . . . . . . . . . . . 12

Importing and exporting process definitions . . . . . . . . . . . . . . . . . . . . . . . . 13Importing a process definition Into Interstage BPM Studio. . . . . . . . . . . . . . . . . . . 13Exporting a process definition from Interstage BPM Studio . . . . . . . . . . . . . . . . . . 14

Configuring job behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Specifying user-defined attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Enabling signatures for jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Using reports in workflow tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting up hierarchical jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Using filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring timers and due dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Defining due dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Defining timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Time and day codes for advanced due date and timer settings . . . . . . . . . . . . . . . . . 22Creating your own business calendars . . . . . . . . . . . . . . . . . . . . . . . . . 24Business calendar file parameters and format . . . . . . . . . . . . . . . . . . . . . . . 25Assigning business calendars to process definitions . . . . . . . . . . . . . . . . . . . . . 28Assigning business calendars to due dates or timers . . . . . . . . . . . . . . . . . . . . . 28

Using Java action sets with workflows . . . . . . . . . . . . . . . . . . . . . . . . . . 29Assigning Java actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Editing Java actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Copying Java actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Removing Java actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Available Java actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iii

Page 4: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Accessing computed fields from workflows. . . . . . . . . . . . . . . . . . . . . . . . . 43Configuring a computed field subprocess node . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 2. Workflow JavaScript functions . . . . . . . . . . . . . . . . . . . . 47Functions for Java actions and complex conditional nodes . . . . . . . . . . . . . . . . . . . . 47

string DateAdd(String Date, Int Offset, String field) . . . . . . . . . . . . . . . . . . . . . 47boolean DateCompare(String Date1, String Operator, String Date2) . . . . . . . . . . . . . . . . 47integer DateDiff(String Date1, String Date2, String field) . . . . . . . . . . . . . . . . . . . 48boolean toBoolean(String or Integer value) . . . . . . . . . . . . . . . . . . . . . . . . 48

Functions for Java actions only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48boolean addAttachment(String attachmentName, String attachmentPath) . . . . . . . . . . . . . . 48boolean deleteAttachment(String attachmentName) . . . . . . . . . . . . . . . . . . . . . 48string getActivityActor() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48string getActivityAssignees() . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48string getActivityName() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49array getAllAttachmentNames() . . . . . . . . . . . . . . . . . . . . . . . . . . . 49string getAttachment(String AttachmentName) . . . . . . . . . . . . . . . . . . . . . . 49string getGroupMembers(String groupName) . . . . . . . . . . . . . . . . . . . . . . . 49string getInitiator() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49string getMembers(String groupName) . . . . . . . . . . . . . . . . . . . . . . . . . 49string getOwners() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49string getProcessAttribute(String name) . . . . . . . . . . . . . . . . . . . . . . . . . 49int getProcessAttributeStringType(String name) . . . . . . . . . . . . . . . . . . . . . . 50string getProcessDescription() . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50string getProcessInitiator() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50int getProcessInstanceId() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50string getProcessName() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50string getProcessOwners() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50int getProcessPriority() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50string getProcessTitle(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51boolean setActivityAssignees(String assignees). . . . . . . . . . . . . . . . . . . . . . . 51boolean setOwners(String owners) . . . . . . . . . . . . . . . . . . . . . . . . . . . 51boolean setProcessAttribute(String name, String value) . . . . . . . . . . . . . . . . . . . . 51boolean setProcessDescription(String description). . . . . . . . . . . . . . . . . . . . . . 51boolean setProcessName(String name) . . . . . . . . . . . . . . . . . . . . . . . . . 51boolean setProcessOwners(String owners) . . . . . . . . . . . . . . . . . . . . . . . . 51boolean setProcessPriority(int priority) . . . . . . . . . . . . . . . . . . . . . . . . . 51boolean setProcessTitle(String title) . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

iv IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 5: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Introduction

IBM® OpenPages® GRC Platform - Workflow Studio is a standalone applicationthat can be used on a local computer by workflow authors.

Audience

The IBM® OpenPages® GRC Platform - Workflow Author's Guide is intended for userswho need to use OpenPages GRC Platform - Workflow Studio to create workflows.

Please read the following important information regarding IBMOpenPages GRC documentation

IBM maintains one set of documentation serving both cloud and on premise IBMOpenPages GRC deployments. The IBM OpenPages documentation describescertain features and functions which may not be available in OpenPages GRC onCloud. For example, OpenPages GRC on Cloud does not include integration withIBM Business Process Manager and certain administrative functions.

If you have any questions about the functionality available in the product versionthat you are using, please contact IBM OpenPages Support via the IBM SupportPortal (http://www.ibm.com/support).

Finding information

To find product documentation on the web, including all translateddocumentation, access IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

Accessibility features

Accessibility features help users who have a physical disability, such as restrictedmobility or limited vision, to use information technology products. OpenPagesGRC Platform - Workflow Studio documentation has accessibility features. PDFdocuments are supplemental and include no added accessibility features.

Forward-looking statements

This documentation describes the current functionality of the product. Referencesto items that are not currently available may be included. No implication of anyfuture availability should be inferred. Any such references are not a commitment,promise, or legal obligation to deliver any material, code, or functionality. Thedevelopment, release, and timing of features or functionality remain at the solediscretion of IBM.

The Interstage BPM application and IBM OpenPages GRC PlatformInterstage Business Process Manager 10.1 (referred to as Interstage BPM in thisguide) is a third-party application used to develop, manage, and remediateworkflow processes within the IBM OpenPages GRC Platform applicationenvironment.

The Interstage BPM application is composed of the following components:

v

Page 6: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

v Interstage BPM Studio - A Windows-based standalone tool used to design andintegrate workflow processes for use within the IBM OpenPages GRC Platformapplication.

v Interstage BPM Console - A browser-based tool used to remediate runningworkflow process instances (jobs).

v Interstage BPM Server - The run-time environment workflow engine (referred toas the IBM OpenPages GRC Platform workflow server).

Interstage BPM Studio features not supported in OpenPagesGRC Platform

Some Interstage BPM Studio features are not supported by the IBM OpenPagesGRC Platform application, and some features are also not visible in the InterstageBPM Studio user interface.

The following Interstage BPM Studio features are not supported by the IBMOpenPages GRC Platform application:v Creating and associating forms with nodes and process definitionsv Style sheet editor (used for forms function)v Creating projects and scenarios for simulating processesv Importing application projects into Interstage BPM Studio from a .bar file. A

.bar file packages all the components in an application project into a singlecontainer.

v Exporting application projects from Interstage BPM Studio to a .bar file.v Uploading/downloading entire workflow application projects to/from the

workflow serverv Defining WorkList or XML UDAsv BigDecimal and Date data types in UDAsv Out-of-the-box Java™ Actions that are used to read XML content or perform

operations on XML UDAsv Triggers in response to external data that cause a job to start or a choice to be

made on a running jobv Java Agents

The following Interstage BPM Studio features are not supported by the IBMOpenPages GRC Platform application and are also not visible in the InterstageBPM Studio user interface:v Custom DB nodesv Custom Web Service nodesv Remote subprocess nodes (which start a job on a remote workflow server)v Invoking business rules on external Blaze Advisor or ILOG® JRules rules enginesv Database Java Actions (which execute SQL commands on an external database)v Java Actions that invoke web services to retrieve and store data in UDAsv Java Action that executes commands on a remote computer, such as batch

commands on a remote Windows systemv Java Action that invokes a rule in a Decision Tablev Custom Trigger nodes

Note: IBM OpenPages GRC Platform Reporting Fragment fields are not supportedin Interstage BPM Studio. The values of Reporting Fragment fields in mappedUDAs will always display as blank.

vi IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 7: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Interstage BPM Studio online helpFor more detailed information on Interstage BPM Studio-specific functions (exceptfor the IBM OpenPages GRC Platform menu options), refer to the Interstage BPMStudio help system. Stand-alone and dynamic (context-sensitive) help is available,as well as text-search capability.

To access help, click the appropriate help option on the Interstage BPM Workbenchwindow Help menu. Alternatively, you can click the ? toolbar button.

WorkflowsA workflow automates a repeatable sequence of operations that is used to achievea result, such as certifying that a control is effective in mitigating a risk, or signingoff on the entire quarterly GRCM effort. Workflows are implemented through thecreation of process definitions (also called job types) and jobs.

IBM OpenPages GRC Platform enables you to create reusable process definitions inInterstage BPM Studio that allow complex, yet easily manageable projects. Theresulting jobs are flexible enough to handle the inevitable changes that may needto occur, yet maintain the efficiency of a managed, controllable process. Successfulbusiness practices demand repeatable processes that follow rigid, predeterminedpaths. Good processes maximize efficiency while minimizing confusion.

Terms you should knowThis table lists terms used throughout this chapter that are specific to workflows.

Table 1. Workflow Terminology

Term Description

project A container within the Interstage BPM Studio application used toorganize process definitions. At the file system level, a projectcorresponds to a folder.

IBM OpenPages GRC Platform supports the following projecttypes:

Application projectUsed to create, design and edit process definitions onyour local computer.

Server projectUsed to create, design and edit process definitionsstored on the workflow server.

process definition

- or -

job type

The terms process definition and job type are interchangeable.

Process definitions are reusable job templates. They define theentire structure of a job, but they themselves are not active. Theyare static entities that determine the behavior and properties ofthe jobs created from them, including task type and order.

Individual process definitions can be created offline (as part of alocal application project) or online (as part of a server project)using the Interstage BPM Studio application.

node A node consists of a graphical symbol that represents a task oractivity within a process definition, and arrows that connectnodes and guide the workflow process from one node to thenext.

Introduction vii

Page 8: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 1. Workflow Terminology (continued)

Term Description

job A job is an ordered sequence of tasks with a distinct startingpoint and an ending point. Jobs are individual instances of aprocess definition.

Active jobs can be edited by the user who started the job. In jobedit mode, you can modify the structure and logic in the job as ifit were a process definition.

For example, if you have an active job that is in an error state,you can reactivate the job. None of these changes are applied tothe original process definition from which the job was firstcreated.

task A task is an individual component of a job. When a job is createdand started, the first task in the job appears as an active task inthe My Tasks list of its assignees. An example of a task might beto review or complete a loss event.

Process definitionsProcess definitions are templates that can be used to create individual jobs.

Process definitions are built in Interstage BPM Studio by combining nodes andconnecting arrows. Each node represents a task that is part of the workflow, andthe arrows represent actions or decisions which result in the next task becomingactive. In addition, each node and arrow has certain properties associated with itthat provide information or directions that are used by IBM OpenPages GRCPlatform.

For example, a basic process definition might consist of two tasks that result in anew document. This kind of process definition might consist of the following steps:1. A manager requests a new document.2. A writer creates the document.3. The writer sends the new document to the manager for review.4. The manager reviews and approves the document.

This process definition is shown in the following flowchart:

Figure 1. Process definition flowchart

viii IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 9: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

The first node is called the Start node and indicates the start of the job. The arrowconnecting the Start node to the second node represents the order of the nextsequence in the job.

The second node, represented by the first rectangle, is called a Task node, anddenotes the writer’s task to create the document. When the writing task iscompleted by the writer, the job automatically sends the document to the managerfor review as the second task. This is represented by the arrow connecting thewriting Task node to the approval Task node.

The third task node represents the manager’s review and approval of thedocument. When the manager has reviewed and approved the document, therebycompleting the task, the job sequence follows the direction of the connecting arrowto the final node.

The final node is called the Exit node, which indicates the end of the job.

Although this is a very simple example of a process definition, Interstage BPMStudio enables you to create complex and robust process definitions that enablemultiple options, concurrent tasks, and assignments to multiple users.

While individual jobs can be started, stopped, and managed through the IBMOpenPages GRC Platform application user interface, you use the Interstage BPMStudio application to build and maintain process definitions to create those jobs.

Online and offline editing modesYou can use Interstage BPM Studio to edit your workflow projects and processdefinitions in online mode, offline mode, or a combination of both modes.

In offline mode, you build, edit, and save a process definition on your localcomputer, independent of any workflow server connection. Once you have createdthe process definition locally, however, you must switch to online mode to uploadthe process definition to the workflow server, associate the process definition withan IBM OpenPages GRC Platform object type, add Java Actions, and publish thefinalized process definition to the IBM OpenPages GRC Platform web application.

In online mode, you are continuously connected to and perform all functionsdirectly on the server including process definition authoring, IBM OpenPages GRCPlatform object association, and publishing to the IBM OpenPages GRC Platformweb application. There is no need to upload your process definitions to the serverbecause you create and save them directly on the server.

In general, the choice between offline and online mode is dictated primarily bywhere you want to create your process definitions. For example, it may be easier todesign very complex process definitions offline and then upload them to theserver. In some organizations, one individual may be assigned to model the

Figure 2. Process definition flowchart example

Introduction ix

Page 10: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

process definition offline and others are responsible for IBM OpenPages GRCPlatform integration and publishing on the server side.

The examples in this chapter assume that you are modeling your processdefinitions offline and then uploading them to the workflow server for integrationwith the IBM OpenPages GRC Platform application.

WorkflowAdministrators groupYou must be a member of the WorkflowAdministrators group to create, edit, ordelete projects and process definitions, perform object type associations, andpublish to IBM OpenPages GRC Platform. If you have administrative privilegesbut are not part of that group, you will still be able to create and maintain processdefinitions, but will not be able to associate object types or publish processdefinitions to IBM OpenPages GRC Platform.

Additionally, any user who needs to view all jobs in the IBM OpenPages GRCPlatform application must be added to the WorkflowAdministrators group.

Workflow life cycleCreating process definitions and publishing them to IBM OpenPages GRC Platformis just one part of an overall process for creating, managing, and remediatingworkflows.

Table 2 summarizes the major phases of the workflow life cycle and providesreferences on where to find more information for each stage of the process.

Table 2. Workflow Life Cycle

Task Description For more information, refer to

1 Use Interstage BPM Studio to completethe following tasks.

1. Create a process definition(workflow).

2. Associate it with an IBM OpenPagesGRC Platform GRC object type.

3. Publish it to the IBM OpenPagesGRC Platform application, where itcan be submitted as a job.

The IBM OpenPages GRCPlatform Workflow Author'sGuide (this guide).

2 Use the IBM OpenPages GRC Platformweb application to submit the job andwork on the tasks associated with thejob.

The IBM OpenPages GRCPlatform application Helpsystem.

3 Use Interstage BPM Console to managejobs that are in an error state.

The Managing Workflowstopic in the IBM OpenPagesGRC Platform Administrator'sGuide.

Getting started with Interstage BPM StudioThis section describes how to start the Interstage BPM Studio application andprovides a brief overview of the major user interface elements in the InterstageBPM Studio Workbench window.

x IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 11: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Starting the Interstage BPM applicationThis section describes how to start Interstage BPM Studio for the first time fromWindows.

Procedure1. Click the Windows Start button.2. Point to All Programs, point to Interstage Business Process Manager Studio,

then click Studio. Alternatively, you can create a shortcut to Studio on yourWindows desktop. A window opens.

3. The application stores your process definitions and other components of aproject in the default workspace folder. You can use the Browse button tospecify a different location, and select an alternative workspace folder from alist in subsequent sessions.

Note: To set a workspace location as the default and suppress display of thiswindow in future sessions, select the Use this as the default and do not askagain check box.

4. Click OK. The Interstage BPM Workbench window opens.

Interstage BPM Studio workbench windowThe Interstage BPM Studio Workbench window contains the following mainelements:v Menu barv Toolbarv Navigator panev Overview panev Outline panev Process Definition Editor pane and palettev Properties pane

Menu bar and toolbarThe menu bar and toolbar are located in the Workbench window. The menu barcontains menus and menu options that you use to access Interstage BPM Studioand IBM OpenPages GRC Platform integration functions, as well as online help.

The toolbar contains buttons to invoke frequently used functions, such as theCreate a Bend Arrow tool and the Select tool.

Navigator paneThe Navigator pane lists your workflow application and server projects, and thenames of the process definitions within those projects. Use this view to manageyour projects and process definitions. For example, you can open processdefinitions for editing or select them for copying, renaming, exporting, and so on.

Overview paneThe Overview pane is useful for displaying large process definitions. It provides anoverview of the entire process definition and allows you to quickly navigate to thearea you want to work on.

If a process definition is too large to be displayed as a whole in the ProcessDefinition editor, the Overview pane highlights the area that is currently visible. Tonavigate to another part, move the highlighted area.

Introduction xi

Page 12: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Outline paneThe Outline pane displays a hierarchical view of all of the nodes in the activeprocess definition. Nodes are represented by an icon and the node name.

Using the Outline pane, you can quickly navigate to specific nodes in large processdefinitions. You can also use this pane for node operations such as cutting,copying, and pasting, and for defining node properties.

Note: That any annotations to actions or nodes are not visible in the Outline pane.

Process Definition Editor pane and paletteThe Process Definition Editor pane is the main work area for process modelingoperations. Use the editor to add and edit any elements in your process definition.Note that you can press Ctrl-Z at any time to undo the most recent action that youperformed in the Process Definition Editor pane, such as adding a Task node.

When you open a process definition, the Process Definition Editor pane isautomatically opened. You can open multiple process definitions at once.

Each process definition is displayed in a separate tab. Depending on yourpreferences settings, the tab shows the complete file name or name of the processdefinition; an asterisk (*) next to the name indicates that there are unsavedchanges.

The Process Definition Editor pane has a palette with buttons for adding nodes,swimlanes or groups, and annotations. See “Process definition elements” for moreinformation on elements available in the palette.v To temporarily open the palette, place the cursor over the collapsed palette. The

palette quickly expands.v To open the palette and keep it open, click the Show Palette button (<) on the

palette.v To collapse the palette, click the Hide Palette button (>) on the palette.

When you open a process definition that is read-only, the palette is not displayed.The status bar indicates that the file is read-only. You can change your preferencessettings to modify the default location and behavior of the palette.

Properties paneThe Properties pane displays general property names and values for a selecteditem in either the Navigator pane or the Process Definition Editor pane.

When you click the empty space in the Process Definition Editor pane, theProperties view displays the general properties of the process definition, such as itsname and description. When you select an element of a process definition, such asa Task node, the properties of that specific element display.

To display a window that allows you to view or edit advanced properties forprocess definitions or selected elements, in the Properties pane, select theProperties row under the Advanced category and click the ellipsis (...) button.

Process definition elementsThe following table illustrates the different nodes and other elements you can addto a process definition. These elements specify the tasks and other events thatdefine the jobs created from the process definition. All elements except arrows andStart nodes can be accessed from the palette.

xii IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 13: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 3. Process Definition Elements

Element Description

Start node The Start node identifies the beginning of the job. Every job must haveone and only one Start node. This node is automatically added to theProcess Definition Editor pane when you start to create a new processdefinition. It is not available on the palette.

Arrow

Arrows define the order and represent the actions that take place withinthe job. Arrows can be used to connect one node to another, one node tomultiple nodes, or multiple nodes to one node. The name of the arrowdefines the available buttons the user will see when completing a task.You can access the arrow tools from the Workbench window toolbar.Note: Arrow names can include any characters except the following:backslash (\), left curly brace ({), and right curly brace (}).

Exit node The Exit node identifies the end of the job. Every job must have at leastone Exit node attached to the end of the final task or tasks.

AND node AND nodes initiate the next task or tasks when of all the previous tasksconnected to it are completed.

You can use this node to synchronize two threads in a job. For example,if you have two series of ongoing tasks that will result in a single task,you can use an AND node to effectively hold the final task until all theprevious connecting tasks are complete.

OR node

OR nodes initiate the next task or tasks based on the completion of anyof a series of previous tasks connected to it. When a task is completedthat is connected by any incoming arrow, outgoing arrows convey anevent to their target nodes, all of which are activated simultaneously.

Delay node Delay nodes pause the workflow for a certain length of time defined bya timer (measurable in days, hours, and minutes) after the node isactivated. Once the timer has counted down, subsequent nodes areactivated simultaneously, or a Java Action is activated.

Subprocess node A Subprocess node (also known as a Child Job node) activates anotherjob and put the current (parent) job into a waiting state. The parent jobwill pause until the Subprocess job completes and returns its values tothe parent job.

When the Subprocess job completes, the parent job is reactivated and allnodes connected to the Subprocess node are activated simultaneously.Subprocess nodes are used to break tasks into a hierarchy ofeasier-to-handle units.Note:

v If you click the + sign on the node, an image of the Subprocessdefinition will be displayed.

v If you double-click the + sign, the Subprocess definition will beopened in a separate Process Definition Editor pane.

Chained-Process

node

Chained-Process nodes activate another job while allowing the parentjob to continue. The child job does not return any values to the parentjob.Note:

v If you click the + sign on the node, an image of the Chained-Processdefinition will be displayed.

v If you double-click the + sign, the Chained-Process definition will beopened in a separate Process Definition Editor pane.

Introduction xiii

Page 14: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 3. Process Definition Elements (continued)

Element Description

Conditional

node

Conditional nodes allow the workflow creator to specify a property, andthen route the workflow based on the value of the property. When theworkflow reaches this node, the process continues along the arrowwhich satisfies the condition specified in the node's Properties window.

When setting up the conditions for this node, you must specify a defaultarrow that will be chosen when no defined value is satisfied.

ComplexConditional

node

A Complex Conditional node is similar to a Conditional node. The onlydifference is the criteria that are specified to direct process flow. For aConditional node, a value is compared to another value. For a ComplexConditional node,

advanced criteria can be specified using a JavaScript expression.

Task node A Task node identifies a task within a job. When the job sequencereaches this node, the user (or users) is notified that they have a task toaccomplish.

Each Task node includes default properties that indicate to whom thetask is assigned and the description (name) of the task itself. Whencreating a process definition or editing a job, you can edit theseproperties by right-clicking on the node and selecting the appropriatetab from the Properties window.

Voting Tasknode

A Voting Task node uses voting rules to determine which outgoingarrow will be activated. In a normal Task node, the first assignee thatcompletes a task would make a choice to determine which path will beactivated.

A Voting Task node allows multiple assignees to each make a choice ofthe possible paths and then polls the results. As soon as one of thevoting rules is fulfilled, the resulting path is activated and the next nodein the job becomes the active one.

Email node The email node allows workflow designers to send predefined emails todesignated recipients anywhere in the workflow, and not just in theprologue or epilogue actions of a node. After the emails are sent, theemail node activates all subsequent nodes connected to itsimultaneously.

Spawn Jobs

node

The Spawn Jobs node will spawn child jobs for the IBM OpenPagesGRC Platform object type specified in the node properties. The objecttype can be filtered on a set of object properties, so that jobs are onlyspawned for objects that meet the criteria.

Annotation An annotation is a text box that you can add to make comments andexplain important aspects of your process design. You can add multipleannotations to the process definition.

Swimlane Swimlanes are used to organize tasks and other process definitionelements into visual categories. These visual categories illustratedifferent functional capabilities or responsibilities. You can useswimlanes to visually group activities performed by the same role.These groups are purely visual; nodes placed on swimlanes or in groupsare not processed in a special way.

Group Groups are similar in function to swimlanes. The only difference is thatwith Groups you can visually categorize tasks and other elementsirrespective of the role.

xiv IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 15: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Interstage BPM Studio features supported in IBM OpenPagesGRC Platform

The following table describes the Interstage BPM Studio features that aresupported by the IBM OpenPages GRC Platform application.

Table 4. IBM OpenPages GRC Platform Supported Features in Interstage BPM Studio

With this feature... You can...

Offline editing v Create or modify a local application project.

v Create, design, and edit process definitions onyour local computer.

v Upload a local process definition to the workflowserver for deployment in the IBM OpenPagesGRC Platform application.

v Download projects from the server to your localcomputer.

Process definitions that are created offline arestored on the local computer.

Online editing v Create or modify a server project by connectingdirectly to a workflow server.

v Create, design, and edit a process definition onthe server.

Process definitions that are created online arestored on the workflow server.

Swimlanes and Groups Visually organize tasks or activities withoutaffecting the sequence of tasks or activities in theworkflow.

Toolbar (with the exception offorms-related features)

Execute commands such as Save, Print, Undo,Redo, Node Alignment, Zoom in, Zoom out, andSearch.

Annotations Add comments or labels to a process definition.

Copy and rename process definitions

(local workflow application projectsonly)

Duplicate or rename process definitions that arepart of a local workflow application project.

Cut, Copy, and Paste nodes Remove or duplicate nodes within a processdefinition or between process definitions.

Business calendar Create custom business calendars for use withtimers or due dates.

Import and export in XPDL format Import or export a process definition in XMLProcess Definition Language (XPDL) format.

Error Actions Define actions to be performed on a processdefinition, node, or another Java Action, when anerror occurs during execution of a Java Action.

Compensation Actions Define actions to be performed for another JavaAction that accesses a system outside of InterstageBPM, such as an IBM OpenPages GRC Platformdatabase. Compensation actions are used to ensurea consistent state of all systems involved in atransaction for cleaning up and rolling backtransactions (for example, to delete a newly addedrow in the IBM OpenPages GRC Platformdatabase).

Introduction xv

Page 16: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 4. IBM OpenPages GRC Platform Supported Features in Interstage BPMStudio (continued)

With this feature... You can...

State Change Actions Define actions to be performed on a processdefinition or node, when an administrator aborts,suspends, and resumes processing of a job.

Out-of-the-box server Java Actions Use certain built-in Java Actions on the workflowserver to manipulate workflow data. For example,you can use a Java Action to assign a Task node toa specific user or to assign the name of a usercompleting a task to a user-defined attribute (UDA).Note: Does not include XML or Rules JavaActions, which are not supported.

No-Operation Java Action Use this Java Action to ignore any error orexception thrown by another Java Action. Thisprevents the workflow from entering an error state.

xvi IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 17: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Chapter 1. Authoring workflows

This chapter describes how to use Interstage BPM Studio to create processdefinitions and publish them for use in workflows in the IBM OpenPages GRCPlatform application.

Note: For more detail on Interstage BPM Studio-specific functionality, refer to thehelp system (see “Interstage BPM Studio online help” on page vii for moreinformation on how to access help).

Creating a process definitionSome tasks are required to create a process definition.

The following tasks are required to create a process definition:v “Creating an application project and process definition name”v “Creating a server project for the process definition” on page 2v “Building the process definition and adding properties” on page 3

In the following example, the user creates a workflow application project offlinecontaining a new process definition for Remediation Control that consists of onetask.

It is important to note that you can also create and build a new process definitionin online mode, as part of a server project. You do not need to create anapplication project nor do you need to upload the process definition to the server,since you are modeling the process definition directly on the server. For moredetail on how to model process definitions on the server, refer to the InterstageBPM Studio help system.

Note: You must be a member of the WorkflowAdministrators group to create, edit,or delete projects and process definitions, perform object type associations, andpublish to IBM OpenPages GRC Platform. If you have administrative privilegesbut are not part of that group, you will still be able to create and maintain processdefinitions, but will not be able to associate object types or publish processdefinitions to IBM OpenPages GRC Platform.

Creating an application project and process definition nameYou first need to create a container for the process definition. When you create theprocess definition on your local computer, this container is known as anapplication project. Once you have created the application project, you can add anew process definition to the project.

Procedure1. On the File menu, point to New, point to Project, and then click Application.2. In the window, type a name for the new application project (my-local-project,

in this example).

Note: Project names and process definition names can include any charactersexcept the following: backslash (\), pipe (|), forward slash (/), colon (:),asterisk (*), left angle bracket (<), right angle bracket (>), question mark (?), and

1

Page 18: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

double quote ("). A period character (.) cannot be used either alone or at theend of a name; it can be used anywhere else in a multi-character name,including the starting character.

3. Click Next to continue.4. In the Project window, complete the following steps.

a. Optionally, type a description of the project in the Description field.b. Leave the Owner field blank (not used).c. To create the application project, click Finish. The application project name

is added to the Navigator pane.5. In the Navigator pane, right-click the application project name, point to New,

and then click Process Definition.6. Type a name (Control Rem in this example) and an optional description for the

new process definition. Process definition names cannot exceed 64 characters.

Note: The application project name you created earlier is already entered inthe window. Also, the Owner field is not used.

7. To create the new process definition, click Finish. In the Navigator pane, Theprocess definition name is added to the Process Definition folder under theapplication project.

Creating a server project for the process definitionBefore you can upload the process definition that you created locally within theapplication project to the workflow server, you need to create a server project onthe workflow server. You must also create a server project for any processdefinitions that you plan to create in online mode. The server project serves as acontainer for the process definitions and specifies the connection parameters thatare required to access the workflow server.

About this task

If you want to upload multiple process definitions to the same workflow server,you need to create only one server project.

Procedure1. On the File menu, point to New, point to Project, and then click Server.2. In the window, type a name for the new server project (my-server-project, in

this example).3. Click Next to continue.4. In the Server Info window, enter the information required to access the IBM

OpenPages GRC Platform workflow server.v If SSL is not configured, click Default, and enter the workflow server host

name and port number.The default port number is 20108.

v If SSL is configured, click Custom, and enter following URL in the Wf-XMLRegistry URL field:https://host_name:workflow_ssl_port/ibpmconsole/System/ServReg.jsp

The default SSL port number is 20111.5. Enter the User ID and Password.

Note: To save the login information so that you do not have to enter the username or password for future sessions, select the Save Password check box.

2 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 19: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

6. To create the server project, click Finish. The server project name is added tothe Navigator pane.

Results

You can double-click the server project name in the Navigator pane to show allprocess definitions that were previously uploaded to, or created on, this workflowserver.

Building the process definition and adding propertiesOnce you have created an application project and process definition name, theProcess Definition Editor pane displays and you can begin to build your processdefinition.

About this task

The file name of your process definition, Control Rem.xpdl, displays in a tab in theProcess Definition Editor pane. XPDL is the native file format for processdefinitions.

Note: If you were creating a process definition directly in online mode, youwould create a new process definition name within the server project and buildthat process definition in online mode.

Every process definition must begin with a Start node and end with an Exit node.Note that the Process Definition Editor adds a Start node automatically. All nodesmust be connected, either directly or via other nodes, to the Exit node; nostandalone or orphan nodes are allowed.

The following example illustrates how to add a Task node and an Exit node to theControl Rem process definition.

Procedure1. In the Process Definition Editor pane, click the arrow next to the Palette pane to

display the palette. The palette provides a list of nodes and objects that you canselect and then drop into the work area.

2. To add the nodes to the process definition, complete the following steps.a. In the Customized folder on the Palette pane, click Task Node. Move the

mouse to the location in the Process Definition Editor pane where you wantto position the Task node and click the mouse to drop the node intoposition.

Note:

v To add additional nodes or objects of the same type to the work area, youmust always click the node or object in the palette first to select it beforedropping the node or object into position. You cannot simply click themouse in the work area to add more copies of the same node type.

v It is possible to copy and paste the same node in the work area, using theCopy and Paste functions in the Edit menu, to create additional instancesof that node. However, in the case of named nodes such as Task nodes,each pasted node will have the same name and you will need to assign aunique name to each node.

Chapter 1. Authoring workflows 3

Page 20: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

v For readability, it is recommended (although not required) to place anysequential Task nodes after the Start node, and then place the Exit nodeafter any Task nodes.

b. In the Event folder on the Palette pane, click Exit.c. Move the Exit node after the Task node and click the mouse to drop the

node into position.3. Right-click the Task node and click Properties.4. In the Properties window, select the General tab. This tab allows you to modify

general information about the Task node, such as a meaningful task name anddescription. In this example, the task is to remediate a control that managementhas determined is ineffective. Complete the following steps.a. In the Name field, enter Remediate Control.b. In the Description field, enter Remediate the attached ineffective control.c. To save the changes, click OK. The new name of the Task node now

displays in the Process Definition Editor pane.5. To connect the nodes with arrows, which define the flow and sequence of tasks,

complete the following steps.a. In the Interstage BPM Studio toolbar, click the Create a Bend Arrow tool.b. Point to the Start node. The cursor shape changes, indicating where you can

start drawing the arrow on the node.c. Click the Start node and drag the mouse to the Task node that you added.d. Release the mouse button and a line with an arrow now connects the two

nodes. The arrow path bends automatically at a 90 degree angle to joinnodes that are not aligned horizontally or vertically.

Note: Alternatively, you can use the Create a Diagonal Arrow tool to drawa straight-line arrow between nodes with no bends.

e. Repeat this process to connect the Task node to the Exit node.6. When you add an arrow, a default name for the action associated with the

arrow is automatically assigned. To change the name to indicate an action ordecision which results in the next task becoming active, complete the followingsteps.a. In the Interstage BPM Studio toolbar, click the Select tool.

Note: You can also press the Esc key to switch from the Create a BendArrow tool to the Select tool.

b. Click the arrow name between the Start node and the Task node. The arrowname is selected. Note that you may need to click the name twice to selectit.

c. Rename the arrow to Start.d. Click the arrow name between the Task node and the Exit node, and

rename it to Complete.

Note: Arrow labels can be up to 64 characters in length and can includeany characters except the following: backslash (\), opening braces ({), andclosing braces (}).

7. To save the process definition, in the Interstage BPM Studio toolbar, click theSave button.

8. To localize application text for objects in workflows published to IBMOpenPages GRC Platform, refer to the Localizing Application Text topic in theIBM OpenPages GRC Platform Administrator's Guide.

4 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 21: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Results

You have just built a simple process definition called Control Rem in themy-local-project application project that contains one Task node, a Start and Exitnode, and named connections that define the task flow. For a description of how toupload the process definition to the workflow server, see “Uploading a processdefinition to IBM OpenPages GRC Platform workflow server.”

Uploading a process definition to IBM OpenPages GRC Platformworkflow server

You now need to upload the process definition created offline as part of anapplication project to the workflow server where it will become part of a serverproject.

About this task

The server project also contains the connection and login parameters needed toaccess the workflow server.

Note: This task is only required for process definitions created in offline mode asdescribed in this example. Process definitions you create in online mode arealready part of the server project and reside on the workflow server.

Procedure1. In the Navigator pane, open the Process Definitions folder, right-click the

process definition (Control Rem in this example), and then click Send to Server.A window displays.

2. Select the server project name that corresponds to the workflow server whereyou are uploading the process definition.

3. If you are not currently logged into the workflow server, you may be promptedfor a workflow server password. Enter the password.

4. To complete the upload to the workflow server, click OK.

Results

In the Navigator pane, the new process definition you just uploaded (Control Rem)now displays under the server project directory as Control Rem (Version 1). Thestatus of the process definition is Draft.

About draft version numberingA server project uses incremental version numbering to track successive revisionsof a process definition in Draft status. For example, if Control Rem (Version 1)already existed in this server project, when you upload Control Rem to theworkflow server, the server project directory in the Navigator pane wouldincrement the uploaded process definition to Control Rem (Version 2). There canbe multiple numbered Draft versions of a process definition on the server.

Connecting to the OpenPages GRC Platform serverTo connect to the IBM OpenPages GRC Platform application server, use thefollowing instructions.

Chapter 1. Authoring workflows 5

Page 22: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

About this task

You must be logged on to the OpenPages GRC Platform application server toperform any of the following workflow tasks:v Associate a process definition to an object typev Publish a process definition to the OpenPages GRC Platform applicationv Save properties and configurations that you add to a Task Node, Voting Task

Node, and/or Spawn Jobs Node

Procedure1. From the menu bar, select OpenPages and click Login to OpenPages.2. In the OpenPages Login box, enter the following information to access the

OpenPages application server:a. In the Host field, type the name of the OpenPages GRC Platform

application server.b. In the Port field, type the application server port number. If you specify an

SSL port, also select the Use SSL check box. The following ports are thedefault application server ports:

Non-SSL port10108

SSL port10111

c. In the Username field, type a logon user name.d. In the Password field, type the password that corresponds to this user

account.

Note: To save the user name and connection information so that you donot have to enter it for future sessions, select the Save Login Info checkbox. However, you must always enter the password when logging into theOpenPages application server.

3. When you are finished, click OK to log on to the application server.A message box indicates that you are logged on. To dismiss the window, clickOK.

Associating a process definition with an object typeOnce you have uploaded the process definition to the workflow server, you needto associate the process definition with an IBM OpenPages GRC Platform objecttype.

About this task

When you associate a process definition with an object type (such as Controls),users with the correct privileges can start jobs based on the process definition fromany object of the associated object type.

For example, if you assign the process definition to the object type Controls(SOXControl), a user with Start Jobs permission can start a job that uses the processdefinition template from any Control detail page in the OpenPages GRC Platformapplication. The nodes within the process definition will be able to display, modify,and use the various properties associated with the SOXControl object.

6 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 23: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Procedure1. In the appropriate server project directory in the Navigator pane, double-click

the process definition (Control Rem (Version 1), in this example).The Process Definition Editor pane displays the same process definition nodesand other elements that you created offline earlier. The name of the processdefinition, Control Rem (Version 1), displays in a tab in the Process DefinitionEditor pane.

2. From the menu bar, select OpenPages GRC Platform and click Associate toOpenPages Object Type.

Note: If the link is disabled, then you must log on to the OpenPagesapplication server first. For details, see “Connecting to the OpenPages GRCPlatform server” on page 5.

3. In the Associate to OpenPages Object Type window, complete the followingsteps.a. Click the Process Definition arrow and select the process definition name

(Control Rem (Version 1) in this example) that you want to associate withan OpenPages object.

Note: All process definitions on the server are listed by default in theProcess Definition list.

b. Click the Object Type arrow and select the object type (SOXControl in thisexample) to be associated with the selected process definition.

Note: You can also search for process definitions and object types by nameor partial name. Search terms are not case sensitive and wildcard characterssuch as asterisk (*) are not supported. To search, enter the name in theappropriate Filter field and click Search. The process definition or objectdisplays in the appropriate list.

c. When finished, click Associate to associate the process definition with theobject type.A message box displays, indicating that the association succeeded. Todismiss the window, click OK.

4. To view the UDA properties that were added as a result of the association,complete the following steps.a. In the Process Definition Editor pane, close the process definition tab.b. In the appropriate server project directory in the Navigator pane, right-click

the process definition and then click Refresh.c. In the Navigator pane, double-click the process definition to re-display it in

the Process Definition Editor pane with the latest properties.d. Right-click an empty area in the process definition in the Process Definition

Editor pane and then click Properties.e. In the Properties window, select the User Defined Attributes tab. This tab

lists the UDAs that are associated with the process definition.f. To dismiss the window, click OK.

Results

The association of the SOXControl object type with Control Rem (Version 1) addsthe following UDAs:v System UDAs, such as job_name, job_id, and __secv An object type association UDA (op_prop_SOXControl in this example)

Chapter 1. Authoring workflows 7

Page 24: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

v Mapped UDAs for each field that is associated with the SOXControl object type(for example, SOXControl!OpenPagesStandardControl!Owner,SOXControl!OpenPagesStandardControl!Status, and many others)

Note: You can continue to edit a process definition, even after associating it withan object type.

Adding Java actions to a process definitionAfter a process definition is associated with an IBM OpenPages GRC Platformobject (such as SOXControl), you can use Java Actions to customize the execution ofyour process definition.

About this task

Attention: Add new user-defined attributes (UDAs) or custom Java actions onlyafter you associate a process definition to an OpenPages object type. If you addnew UDAs or custom Java actions before associating the process definition to theOpenPages object type, the new UDAs or custom Java actions will be erasedduring the Associate to Object Type operation.

You can invoke Java Actions at the following times:v Before the job starts (Prologue Java Actions and Role Java Actions).v At job completion (Epilogue Java Actions).v When a timer expires (set by a Timer Java Action).v Before a control reaches a node (Prologue Java Action).v After a control leaves a node (dynamic task assignment, using a Role Java

Action for a task node).

In the following example, you add a Role Java Action called Assign Task to Userto the selected node. This Java Action assigns the Remediate Control taskrepresented by the node to the owner of the control for which the job is started inthe IBM OpenPages GRC Platform web application. That owner is determined bythe value of the control's Owner field at job runtime.

Note: Every Task node in a process definition must have an assignee or theprocess definition will not be valid.

For more information on Java Actions, see “Using Java action sets with workflows”on page 29.

Procedure1. Before adding a Java Action to assign the Remediate Control Task node to a

specific user, you must apply a property to the Task node to assign a defaultuser to the task (in this example, the IBM OpenPages GRC Platform superadministrator). Complete the following steps.a. Click the Remediate Control Task node to select it.b. Right-click the Task node and click Properties.c. In the Task Node Properties window, select the Assignee tab.d. In the Role field, select User.e. In the Assignee field, select OpenPagesAdministrator.

2. To add the Role Java Action to the Task node, complete the following steps.a. Select the Action Set tab.

8 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 25: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Note: Action sets are categories of related Java Actions.b. Make sure the Role Actions tab is selected and then click the Add button.

A window displays folders with different categories of Java Actions.c. In the Server Actions folder, select Assign Task To User.d. Click Create to display a window that allows you to configure this Java

Action.e. In the Assignment Selection tab in the Assign Task to window, select the

Use Workflow Variable check box. A text field appears with a redExpression Mode buttons.

f. Click the red Expression Mode button repeatedly until the V value displays.This indicates that you are adding a variable to the Java Action. The list ispopulated with the UDAs that were added when you associated the processdefinition with the SOXControl object type.

g. Select the SOXControl!OpenPagesStandardControl!Owner mapped UDA.This variable assumes the value of the control owner when the job is run inIBM OpenPages GRC Platform.

h. Click OK. The saved Java Action configuration now appears in the RoleActions tab as Assign Task To:SOXControl!OpenPagesStandardControl!Owner.

3. To save the changes you made to all of the Task node properties described inthis procedure, click OK. Note that, in the Process Definition Editor pane, theTask node now lists OpenPagesAdministrator as the default owner of the task.

Note: If you open the Properties window for a Task node to simply view theproperties and then click Cancel to dismiss the Properties window, the ProcessDefinition Editor pane will add an asterisk to the process definition indicatingthat it has been modified, even though you have not changed anything. Toremove the asterisk and the modified state, press Ctrl-Z (Undo function) afteryou dismiss the Properties window.

4. To save the latest changes to the process definition, in the Interstage BPMStudio toolbar, click the Save button.

Publishing the process definition to OpenPages GRC PlatformWhen the process definition is associated with an object type and you added oneor more Java Actions to the process definition, you can make the process definitionavailable to the IBM OpenPages GRC Platform web application as an executablejob.

About this task

When you publish the process definition to OpenPages GRC Platform, thefollowing Java Actions are automatically added to the process definition:v An Init Action Set is set up for the process definition with the appropriate Java

Actions. This action initializes UDA data before the job is performed.v A Commit Action Set is set up for the process definition with the appropriate

Java Actions. These Java Actions are used on upon completion of the job to cleanup or analyze the data.

v A RefreshPropertiesAction Java Action is set up for the Task node in the processdefinition. If you right-click the Task node, click Properties to display thewindow, select the Action Set tab, and select the Prologue Actions tab, this JavaAction is listed as a Prologue Action.

Chapter 1. Authoring workflows 9

Page 26: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

v An OPSyncAttachmentsFromChild Java Action is added as an Epilogue Actionfor any subprocess node. This action is used internally by the OpenPages GRCPlatform application to synchronize data between parent and child workflows.

Note: Do not delete any Java Actions that are automatically added to the processdefinition when it is published to OpenPages GRC Platform.

To publish a process definition to the OpenPages application, use the followinginstructions.

Procedure1. From the menu bar, select OpenPages GRC Platform and click Publish to

OpenPages.

Note: If the link is disabled, then you must log on to the OpenPagesapplication server first. For details, see “Connecting to the OpenPages GRCPlatform server” on page 5.

2. In the Publish to OpenPages window, complete the following steps.a. Click the Process Definition arrow and select the process definition name

(Control Rem (Version 1) in this example) that you want to publish to theOpenPages GRC Platform web application.

Note: All process definitions on the server with a status of Draft are listedby default in the Process Definition list.

b. In the Filter Process Owner by field, select either Users or Groups to limitdisplay in the Process Owner list to the selected owner type on the server(Groups in this example).The Process Owner list now displays the groups that currently exist on theserver. Select the group that owns the published process definition(WorkflowJobOwners in this example).

Note:

v Due to a third-party software limitation, user or group names thatinclude a comma (,) character is not available for selection from theProcess Owner list. Try to avoid commas in any user or group name thatyou want to assign as owner of the process definition.

v You can also search for process definitions and users/groups by name orpartial name. Search terms are not case-sensitive and wildcard characterssuch as asterisk (*) are not supported. To search, enter the name in theappropriate Filter field and click Search. The process definition oruser/group displays in the list.

c. In the Process Owner listing box, select one or more owners for the processdefinition that you are publishing to the OpenPages GRC Platform webapplication. The owner of a process definition, whether a user or a user thatis part of a selected group, is able to submit a job based on that processdefinition in the IBM OpenPages application.

3. When you are finished, click Publish to publish the process definition to theOpenPages application. A message box indicates that the process definition wassuccessfully published. To dismiss the window, click OK.

Results

A new copy of the process definition now displays in the Process Definition Editorand Navigator panes and the version number is incremented by 1. The status of

10 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 27: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

the process definition changes from Draft to Published.

Editing published process definitionsYou can modify process definitions that you have already published in the IBMOpenPages GRC Platform web application and republish them in IBM OpenPagesGRC Platform.

Procedure1. In the server project directory in the Navigator pane, right-click the process

definition and select the Open With Version option to select the publishedversion. The selected process definition opens in the Process Definition Editorpane, its version number is incremented by 1, and its status changes to Draft. Aseparate copy of the original published version is retained.

2. In the Process Definition Editor pane, make your changes to the processdefinition and save it. Because the process definition is now in a Draft state, theversion number is not incremented when the file is saved. This process is thesame as that described in “Building the process definition and addingproperties” on page 3.

3. Associate the process definition with a new object type, if necessary, asdescribed in “Associating a process definition with an object type” on page 6.

4. Change or add any properties or Java Actions to nodes, as described in“Adding Java actions to a process definition” on page 8.

5. Publish the modified process definition to IBM OpenPages GRC Platform, asdescribed in “Publishing the process definition to OpenPages GRC Platform”on page 9.

Results

When you republish the modified process definition, the original published versionis rendered obsolete by the system.

Copying and deleting application projects and process definitionsThis section describes how to make a copy of or delete a project or processdefinition.

Copying an application projectWhen you make a copy of an application project, a copy is also made of all processdefinitions and other items contained within the project.

Procedure1. In the Navigator pane, right-click the application project and click Copy.

Note: You can also copy several application projects at once. Hold down theShift or Ctrl key while clicking the mouse to select multiple applicationprojects.

2. Right-click the application project again (or any one of the projects for amultiple copy operation) and click Paste.

3. In the Copy Project window, for each new copy, complete the following steps.a. Type a name for the new copy.b. By default, the application project is stored in your workspace directory. If

you want to change the location, complete the following steps.

Chapter 1. Authoring workflows 11

Page 28: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

1) Clear the Use default location check box.2) Click Browse.3) Select an existing folder or create a new one.4) Click OK.

Results

The new copy or copies are now listed in the Navigator pane.

Copying a process definitionYou can only copy process definitions within an application project or betweendifferent application projects. You cannot copy process definitions in serverprojects.

Procedure1. In the Navigator pane, complete the following steps.

a. Within the application project, open the Process Definitions foldercontaining the process definitions that you want to copy.

b. Right-click the process definition and click Copy.

Note: You can also copy several process definitions at once. Hold downthe Shift or Ctrl key while clicking the mouse to select multiple processdefinitions.

2. In the application project where you want to insert the copy or copies of theprocess definition, right-click the Process Definitions folder and click Paste.

3. If you are copying within the same application project and a process definitionusing the same file name already exists, a window displays asking you for afile name. Type the new file name and click OK.

4. If you are copying between different application projects and a processdefinition using the same file name already exists, a window opens.v To overwrite the existing process definition, click Yes.v To keep the existing process definition, click No.

Results

The new copy or copies are now listed in the Process Definitions folder in theappropriate application project folder.

Deleting a project or process definitionYou can delete some types of projects and process definitions.

About this task

The following projects and process definitions can be deleted:v Application projectsv Individual process definitions within application projectsv Server projects (only the server configuration and connection parameters stored

locally are deleted, not the process definitions on the server). You cannot deleteany process definitions within server projects.

12 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 29: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

A non-administrative user can only delete or edit his or her projects. Anadministrator can delete or edit anyone’s projects.

Note: When you delete an application project, all process definitions and otheritems contained within the project are also deleted.

Procedure1. In the Navigator pane, right-click the application project, the process definition

within the Process Definitions folder in that project, or the server project thatyou want to remove.

Note: You can also delete several projects or process definitions at once. Holddown the Shift or Ctrl key while clicking the mouse to select multiple items.

2. Click Delete.3. In the window, click Yes to confirm.

Importing and exporting process definitionsThis section describes how to import process definitions created in XPDL formatfrom external applications into Interstage BPM Studio. It also describes how toexport process definitions created in Interstage BPM Studio to XPDL format.

Note: You cannot use Interstage BPM Studio’s import and export function toimport or export process definitions that are already associated with an IBMOpenPages GRC Platform object type or have previously been published to theIBM OpenPages GRC Platform application. In these cases, you must use theObjectManager tool to import or export the process definition, as described inUsing the ObjectManager Tool in the IBM OpenPages GRC Administrator's Guide.

Importing a process definition Into Interstage BPM StudioYou can import a process definition created externally in XPDL format intoInterstage BPM Studio.

Before you begin

Before importing a process definition, you must create the application project intowhich you will import the file.

Procedure1. In the Navigator pane, right-click the Process Definitions folder of the

application project where you want to import the process definition and clickImport.

2. In the Import Process Definition window, navigate to the location where theprocess definition is currently stored.

3. Select the process definition and click Open.4. If a process definition with the same name already exists in the application

project in Interstage BPM Studio, enter a new file name and click OK.

Results

The imported process definition is now listed in the Process Definitions folder ofthe application project.

Chapter 1. Authoring workflows 13

Page 30: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Exporting a process definition from Interstage BPM StudioYou can export process definitions from Interstage BPM Studio to a file in XPDL1.0, 2.0, or 2.1 format. The process definition can be in either an application projector a server project.

About this task

Exporting is generally used when you want to complete one of the following tasks:v Make a specific XPDL version of a process definition file available to an external

applicationv Make a copy of an incomplete draft version of process definition on the server

available for another individual to finish locally in Interstage BPM Studio, andthen upload back to the server

Procedure1. In the Navigator pane, right-click the process definition, point to Export, and

click the desired XPDL format version number.

Note: If you have made unsaved changes to the process definition, you areprompted to save those changes before continuing.

2. In the Export Process Definition window, navigate to the location where youwant to store the exported process definition.

3. Click Save.

Configuring job behaviorWhen you create jobs and associate them with IBM OpenPages GRC Platformobjects, there are certain characteristics you can modify to add additionalfunctionality to the workflow capabilities of the IBM OpenPages GRC Platformapplication.

This section describes some of the modifications you can make to IBM OpenPagesGRC Platform jobs and tasks.

Specifying user-defined attributesUser-defined attributes (UDAs) are global variables that are defined on the processdefinition level so that all nodes within a job can access all UDAs. Using UDAs,you can specify the behavior of nodes and store data for process execution.

About this task

UDAs hold values in a running job. Job participants provide the values throughJavaScripts or Java Actions. UDAs consist of a name and an identifier (ID). Bothvalues are stored in the database. By default, UDA identifiers are automatically setby the system. However, you can also specify your own identifiers. For every userinteraction, the UDA name is used. Whenever necessary, the name is automaticallymapped to the UDA identifier.

Procedure1. Open the Properties window for the process definition.2. Select the User Defined Attributes tab.3. Click Add. A row with placeholder values is added. Specify the following

parameters for the row.

14 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 31: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Name Name of the UDA can be up to 64 characters, including specialcharacters. The name must not start with two underscores (__) becausetwo underscores are used as a prefix for UDAs created and maintainedby the system.

IdentifierIdentifies a UDA by providing a unique name. By default, UDAidentifiers are system-generated. However, you can also specify yourown IDs. UDA identifiers can contain up to 32 characters. Identifiersmust not contain any special characters (anything other than a - z, A -Z, or 0 - 9). The Identifier field is displayed only if you select theDisplay Identifier check box in the Properties window.

Type The following data types are supported:v BOOLEANv FLOATv INTEGERv LONGv STRING

Initial ValueInitial value of the UDA

4. To save the changes, click OK.

Results

You can remove a previously specified UDA from the properties window byselecting the row and clicking Delete Selected. You can rename a UDA bydouble-clicking the name and modifying it. You cannot remove or rename UDAsthat are currently used in process definitions.

Enabling signatures for jobsIn the IBM OpenPages GRC Platform application, automatic signatures are appliedto an object as a result of a workflow task. If a user is assigned a task to create asignature, completing the task results in a signature window. Once the user fillsout the window, the new signature is created on the object.

To create a signature event for a job started from an IBM OpenPages GRC Platformobject, add a Task node to the process definition in Interstage BPM Studio with anoutput arrow labeled Signoff (it must be this exact wording) and publish theprocess definition to the IBM OpenPages GRC Platform application. When userscomplete the task in the IBM OpenPages GRC Platform application, they areprompted to enter a signature which displays in the Signoff table in the object’sDetail page.

Using reports in workflow tasksYou can use Interstage BPM Studio to attach IBM OpenPages GRC Platformreports to Task nodes in process definitions. When you publish the processdefinition and access the job in IBM OpenPages GRC Platform, clicking on thename of an attached report runs the report and displays the results in a newwindow.

Attaching a report to a workflow taskYou can attach a report to a workflow task.

Chapter 1. Authoring workflows 15

Page 32: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Procedure1. In the Process Definition Editor pane, right-click the Task node to which you

are attaching the report and click Properties.2. In the Properties window, select the Reports tab.3. For each report you want to attach to the Task node, complete the following

steps.a. Click Add. A hierarchical view of report folders opens.b. Navigate to the folder containing the report you want to attach. A list of

reports in that folder opens.c. Select the report from the list. You cannot select multiple reports.d. Click OK. The attached report name is now listed for the Task node.

4. To apply all property changes and dismiss the Properties window for the Tasknode, click OK.

5. To save the latest changes to the process definition, in the Interstage BPMStudio toolbar, click the Save button.

Passing parameters to reports from workflow tasksIn order to use reports with interactive properties, simply attach the report asnormal to a workflow task. When the report is run, the report will prompt the userfor values for the interactive parameters.

If you have an interactive report parameter with the same name as a job property,the value of the job property will be passed to the report as a string in the report.

The following limitations apply to the use of autofilling interactive reportparameters with job properties:v No attempt is made to validate that the job property and interactive report

parameter are the same data type (for example: string, file path, enumerated list)v If a single interactive parameter matches the name of a job property, the user

will not be prompted to provide values for any other interactive parameters. Ifthey do not match job properties, they will be submitted to the report withblank entries. This may cause the report to fail, depending on the reportparameter.

Removing a report from a workflow taskYou can remove reports from the Task node.

Procedure1. In the Process Definition Editor pane, right-click the Task node to which you

are attaching the report and click Properties.2. In the Properties window, select the Reports tab.3. For each report you want to remove from the Task node, select the report from

the list and click Remove.

Note: You cannot select multiple reports.4. To apply all property changes and dismiss the Properties window for the Task

node, click OK.5. To save the latest changes to the process definition, in the Interstage BPM

Studio toolbar, click the Save button.

16 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 33: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Setting up hierarchical jobsThe IBM OpenPages GRC Platform application allows users to create hierarchicaljobs - jobs that spawn other jobs and then wait for those child jobs to complete.When all of the child jobs (which can spawn jobs of their own) are completed, theparent job is reactivated and continues on to the next task.

About this task

Hierarchical jobs are created by including a Spawn Jobs node in the parentworkflow. When activated, the node creates a child job for every child object thatmatches the type and criteria specified in the Spawn Jobs node. The object type canbe filtered on a set of object properties, so that jobs are only spawned for objectsthat meet the criteria.

For example, you may have a job for a business entity that requires sign-off oneach of the processes associated with the job. Using a Spawn Jobs node, you canautomatically start jobs for each of the processes underneath the business entitythat handle the workflow associated with signing off on the process. Once all ofthose jobs complete, the original job is reactivated and can continue along theworkflow path.

Procedure1. In the Process Definition Editor pane in Interstage BPM Studio, add a Spawn

Jobs node.2. Right-click the node and click Properties.3. In the OpenPages Spawn Jobs Node window, select the General tab.4. Enter a name and description for the Spawn Jobs node.5. Select the Job Hierarchy tab. To set the properties for the Spawn Jobs node that

control what jobs are started when the node is activated, complete thefollowing steps.a. Each process definition can be started from a certain object. The child jobs

that will be started by the Spawn Jobs node will also be associated with anobject type. For example, if the parent process definition (the workflowcontaining the Spawn Jobs node) will be started from a Business Entity, andthe child jobs will be associated with Risks, the hierarchy relationship isChildren.Select Parents or Children to determine whether the object that thespawned jobs will be assigned to is a parent or a child of the currentprocess definition's associated object type.

b. When you select a content type for the Spawn Jobs node, it determineswhich objects will be used to start the child jobs. For example, if you chooseSOXProcess and then start the parent job from a business entity, a child jobwill be started for each associated process.In the Content Type list, select the content type.

c. In the Job Type list, select the process definition that will be started for eachobject.

Note: If you are creating a process definition that will be used as a childjob for another process definition, the child process definition must have thegroup WorkflowJobOwners as its owner.

Chapter 1. Authoring workflows 17

Page 34: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

d. The Single File Property Type allows you to choose the set of object fieldsyou wish to set filters on for the child jobs. The list is restricted to thecurrent object types specified for the parent job type.In the Single File Property Type list, select the appropriate value.

e. You can optionally specify whether the child job will honor the primaryassociations between the object types. If you select Yes, only associatedobjects (of the selected object type) that have a primary association with theparent object will spawn jobs.

f. You can optionally limit the levels that the OpenPages GRC Platformapplication will traverse when selecting objects to spawn jobs. For example,if you have processes that have three levels of associated subprocessesunderneath them, and you change the Levels to Traverse value to 1, only thedirectly associated subprocesses will be considered when spawning jobs.

6. On the Filters tab, you can optionally filter the objects that will have jobsstarted for them by specifying a set of property/value pairs. See “Using filters”for more information.

7. Click OK to exit the window and then save the process definition.

Using filtersBy default, a job will be started for each child object associated with the object thatspawned the parent job. By specifying a set of property and value pairs, you canfilter the objects that will have jobs started for them.

Before you begin

Before you can set a filter, you must select a content type on the Job Hierarchy tab.

About this task

For example, you can set a filter for a job that will be started for all Risks under aBusiness Entity, and restrict the node behavior with a filter set for Risk InScope=true. In this case, only Risks that are marked as being in scope will havejobs started for them. Risks that are out of scope will be ignored.

Procedure1. On the Filters tab in the OpenPages Spawn Jobs Node window, for each filter

that you want to create and apply to the node, complete the following steps.a. In the Property Name list, select the property to be filtered.b. In the Operator list, select an operator.c. In the Value field, enter the value.d. Click Add. The new filter appears in the Applied Filters pane.

2. When you have added all of the desired filters to the node, choose one of thefollowing options:

AND All of the filters must be valid in order for a job to be spawned.

OR Any one of the filters must be valid in order for a job to be spawned.

Configuring timers and due datesDue dates specify when an activity is due to be completed once it has becomeactive. They also specify what will happen when the due date is reached and theactivity has not been completed. For example, the activity may be escalated toother users or an email may be sent.

18 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 35: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Timers are used to automatically perform an action at some point after the Tasknode is activated. They can be used, for example, with Delay nodes to suspendprocess execution for a certain amount of time. Timers may operate only once orrepeatedly. They can be defined for the process definition as a whole, forindividual activities (Task nodes, Voting Task nodes), or for Delay nodes.

When defining due dates and timers, you specify an absolute or relative time. Arelative time can be based on the regular calendar or on a business calendar thatcounts only business hours.

The following sections explain how to define due dates and timers. They alsoprovide instructions on using your own business calendars.

Defining due datesDue dates can be defined for Task nodes and Voting Task nodes.

About this task

When you are defining a due date, you can choose among the following due datetypes:

AbsoluteSets the due date to an absolute time, for example to January 1, 2007,00:00:00

CalendarSets a relative due date based on the regular calendar. The due date iscalculated relative to the time the activity becomes active. The time iscounted using all seven days of the week and 24 hours of the day. As such,they can expire outside the normal business hours.

BusinessSets a relative due date based on a business calendar. The time is countedusing only business days and hours. This ensures that activities are dueonly during normal business hours. Interstage BPM determines businessdays and hours using a business calendar. Refer to “Creating your ownbusiness calendars” on page 24 for more information on businesscalendars.

AdvancedSets the due date according to an expression that you specify. Theexpression defines an absolute or relative due date. The time can becounted using the regular calendar or a business calendar.

Procedure1. Right-click the node and select Properties.2. In the Properties window, select the Due Date tab.3. Specify one of the following due date types:

An absolute date based on the regular calendar Click Absolute and enter the date and time.

A relative date based on the regular calendarClick Calendar and specify after how many days and at what time theactivity is due to be completed once it has become active.

A relative date based on the business calendar Click Business and specify after how many business days and at what

Chapter 1. Authoring workflows 19

Page 36: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

business time the activity is due to be completed once it has becomeactive. For the business time, you have different options. You canspecify an absolute time, a time relative to the current time, a timerelative to opening time, or a time relative to closing time.

An absolute or relative date specified with an expression Click Advanced and type the expression.

For details on date codes that you can use in the expression, see “Time and daycodes for advanced due date and timer settings” on page 22.

4. Click Add and select the Java Actions to be executed when the due date isreached and the activity has not been completed.By default, an empty Timer Actions folder is displayed. You can add regularJava Actions, Error Actions, and Compensation Actions to the Action list.

5. Click OK to dismiss the window.

Defining timersYou can define timers to start running in specific situations.

About this task

You can use timers with the following elements:

Process DefinitionsThese timers start running whenever a new process instance is createdfrom the process definition containing the timer.

Task Nodes and Voting Task NodesThese timers start running when the node becomes active.

Delay NodesTimers are used with Delay Nodes to suspend process execution for acertain amount of time. These timers start running when the Delay Nodebecomes active.

Before a timer starts, it calculates an expiration time based on its settings. Thetimer is supposed to execute at its expiration time, and it usually does. If, however,the calculated expiration time is in the past relative to the timer start time, timersthat execute only once will execute upon starting, and a periodic timer will fail toexecute. A timer having an expiration time before its start time is considered anerror, so the timer's process instance will go into an error state. Periodic timersmust have expiration times that are in the future because they represent arepeating loop that could become an infinite loop in such a case.

When you are defining a timer, you can choose between the following timer types:

AbsoluteSets the absolute time when the timer will expire, e.g. January 1, 2007,00:00:00.

CalendarSets the duration after which the timer will expire based on the regularcalendar. These timers start when the node or process instance to whichthey are assigned becomes active. The time is counted using all seven daysof the week and 24 hours of the day. As such, they can expire outside thenormal business hours.

BusinessSets the duration after which the timer will expire based on a business

20 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 37: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

calendar. These timers start when the node or process instance to whichthey are assigned becomes active. The time is counted using only businessdays and hours. These timers can expire only during normal businesshours. Interstage BPM determines business days and hours using abusiness calendar. Refer to “Creating your own business calendars” onpage 24 for more information on business calendars.

AdvancedSets the timer according to an expression that you specify. The expressiondefines an absolute or relative timer. The time can be counted using theregular calendar or a business calendar.

Procedure1. Complete one of the following steps.v To define a timer for a process definition, open the Properties window for

the process definition.v To define a timer for a node, open the Properties window for the node.

2. Select the Timers tab.3. Enter a name for the timer in the New Timer field and click Add New.4. Make sure that the timer is selected in the Timers list.5. If you want the timer to operate only once, specify one of the following timer

types:

An absolute timer based on the regular calendar Click Absolute and type the date and time.

A relative timer based on the regular calendar Click Calendar and specify after how many days and at what time thetimer is to expire.

A relative timer based on the business calendar Select Business and specify after how many business days and at whatbusiness time the timer is to expire. For the business time, you havedifferent options. You can specify an absolute time, a time relative tothe current time, a time relative to opening time, or a time relative toclosing time.

An absolute or relative timer specified with an expression Select Advanced and type the expression. For details on date codes thatyou can use in the expression, see “Time and day codes for advanceddue date and timer settings” on page 22.

6. If you want the timer to operate repeatedly, specify one of the following timertypes:

A periodic timer based on the regular calendar Select Periodic and click Calendar. Specify the interval at which youwant the timer to expire.

A periodic timer based on the business calendar Select Periodic and click Business. Specify the interval at which youwant the timer to expire.

A periodic timer specified with an expression Select Periodic and click Advanced. Specify the interval at which youwant the timer to expire.

Periodic timers are always relative to a given event. The first operation of aperiodic timer is relative to the time when the process instance or the nodebecomes active. Subsequent operations are relative to the last operation.

Chapter 1. Authoring workflows 21

Page 38: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

7. Click Add and select the Java Actions to be executed when the timer is expired.You can add regular Java Actions, Error Actions, and Compensation Actions tothe Action list.

8. Click OK to dismiss the Properties window.

Results

For each timer that you define, one or multiple UDAs are created. The UDA namesidentify the timer and the timer action. For example, a typical UDA name might be__atmr_publication_time. The prefix __atmr identifies this as a timer, the middleterm publication contains the name of the timer, and the suffix time identifies thefunction of the UDA. These UDAs can be modified through a Java Action orthrough a JavaScript. You can check which UDAs belong to a timer by clickingAdvanced on the Timers tab.

Time and day codes for advanced due date and timer settingsThe following codes can be entered into the Set Expression field in the Propertieswindow when configuring an Advanced timer or due date. Remember thatbusiness time is set by the business calendar you are currently using.

Absolute time (AT)Used to set the absolute time of the day.

To set the timer to 4:30pm on that day:AT(16:30:00)

Relative to closing time (CT)Used to set the business time relative to the closing time. Typically you will usenegative hours with closing time in order to calculate a relative time before closingtime.

To set the business time relative to the closing time of the day:

At the closing time:CT(00)

Two hours before the closing time:CT(-02:00:00)

Relative to opening time (OT)Used to set the business time relative to the opening time of the day.

At the opening time:OT(00)

Two hours after opening time:OT(02:00:00)

Relative to current time (BT)Used to set the business time relative to the current time of the day. Note that thisis the current time of day when the job is started, not when the timer is created.

After 4 1/2 business hours from the current time:BT(04:30:00)

22 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 39: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Two business hours earlier than the current time:BT(-02:00)

The next time that falls inside business hours, if the current time is outsidebusiness hours. Otherwise, the current business time:BT(00)

Note: You may need this if different business days have different hours.

The previous time that falls inside business hours, if the current time is outsidebusiness hours. Otherwise, the current business time:BT(-00)

Setting business days (BD)Used to set the number of business days relative to the current day.

Four business days from today:BD(4)

Same day if it is a business day, else the next business day.BD(0)

Same day if it is a business day, else the previous business day.BD(-0)

Setting relative days (RD)Used to set the relative days from the current day (the day the task was started).This setting does not use the business calendar.

One week after the current time:RD(7)

One day earlier than the current time:RD(-1)

Setting days of the week (WD)Used to set the absolute days of the week.

Sunday of the week when the task was activated:WD(1)

Friday of the week when the task was activated:WD(6)

Setting the next day of the week (WN)Used to set the next week day after the current time.

The next Sunday after the current day:WN(1)

Setting relative month (RM)Used to set the relative months in the future. If the month does not have enoughdays to be the same day as the current day, then the day will be the last day of themonth.

Chapter 1. Authoring workflows 23

Page 40: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Three months from the current day:RM(3)

Setting the exact day of the month (DM)Used to set the exact day of the current month.

The first day of the month:DM(1)

The last day of the month.DM(-1)

Setting the exact business day of the month (BM)Used to set the exact business day of the month.

The first business day of that month.BM(1)

The last business day of the month.BM(-1)

Setting the day of the year(DY)Used to set the absolute day of the year.

The first day of the year:DY(1)

The last day of the year:DY(-1)

Setting the business day of the year(BY)Used to set the business day of the year.

The first business day of the year:BY(1)

The last business day of the year:BY(-1)

Creating your own business calendarsWhen defining due dates and timers, you can use a business calendar instead of aregular calendar. A business calendar defines the business hours and days of anorganization.

About this task

Using a business calendar ensures that timers expire during business hours only.The same applies for due dates; business calendars ensure that activities are dueduring business hours only. Interstage BPM Studio provides a fully functionaldefault business calendar. You can modify the default business calendar or you cancreate your own business calendars.

The IBM OpenPages GRC Platform application determines business days andhours using the business calendar defined for the process definition you are using.

24 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 41: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

If you haven't defined a business calendar for the process definition, the IBMOpenPages GRC Platform application uses the default business calendar installedwith the workflow server.

Procedure1. In your local application project, right-click the Calendar folder, point to New,

then click Calendar.2. In the New Calendar window, the Project field automatically shows the name

of the application project for which you want to create the business calendar. Ifyou want to select a different project, complete the following steps.a. Click Browse and select a project directory for the new calendar file.

Note: The .cal extension indicates that this is a business calendar.Calendars are like properties or .ini files that specify business days andhours.

b. Select the project where the new calendar file is to be saved, and click OK.If the file name already exists, type in a new name to avoid a file nameconflict.

3. In the Name field, type in a name for the new calendar file, and click Finish.The new calendar (.cal) file is automatically stored in the Calendar folder ofthe selected project. The new calendar file automatically opens in the text editoryou have specified for opening .cal files, with default values.

4. Define your business calendar file. You can use the default values as a startingpoint to create your business calendar. For a detailed explanation of businesscalendar file format and syntax, see “Business calendar file parameters andformat.”

What to do next

You can only save your changes using the Save option from the file menu. Youcannot select the Save As option for saving new resource files.

Once you have created a business calendar, it must be deployed on the workflowserver before you can assign it to process definitions or to particular timers. Formore information on deploying the business calendar on the server, see theDeploying a Business Calendar on the Workflow Server section in the IBM OpenPagesGRC Platform Administrator Guide.

Business calendar file parameters and formatEach line of a business calendar consists of a parameter-value pair terminated by asemicolon (;). The parameter-value pairs specify the business days and hours. Toindicate ranges, such as start and end times, use a comma (,) between the startingand ending values. The business calendar file must have a .cal file extension.

Default calendarA default calendar, named Default.cal, is provided at installation time. If no othercalendar is configured for use with Interstage BPM, you can still add a businesstimer to your process definitions, and the default calendar will supply the businessdays and hours. The default calendar provides an example of a fully functionalbusiness calendar that you can modify for your specific needs.

The content of the default calendar file is similar to the following:

Chapter 1. Authoring workflows 25

Page 42: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

EVERYDAY=8:00,18:00;SAT=;SUN=;2003/01/01=;2004/01/01=;2005/01/01=;2006/01/01=;2007/01/01=;2008/01/01=;2009/01/01=;2010/01/01=;CALENDAR_END=2010/12/31;CALENDAR_BEGIN=2003/01/01;TIMEZONE=-8:00;

Business calendar parametersThe following table describes the parameters that you can use in the businesscalendar to specify business hours, valid start and end dates, and the time zone.All times must be specified in 24-hour format. When specifying a time range, use acomma to separate starting and ending times.

Table 5. Business Calendar Parameters

Parameter Description Examples

EVERYDAY=<Start_Time, End_Time>;

Required. Defines thedefault business hours forevery day of the week,where <Start_Time> and<End_Time> are thestarting and ending timesof the business day.

EVERYDAY=9:00,17:00;

Business hours for every dayof the week are 9 AM to 5 PM.

<Day of the Week>=<Start_Time, End_Time>;

or

<Day of the Week>=;

Optional. Overrides theEVERYDAY setting for thespecified day of the weekonly.

Defines the businesshours for a specific day ofthe week, where <Day ofthe Week> is SUN, MON,TUES, WED, THU, FRI, orSAT and <Start_Time>and <End_Time> are thestarting and ending timesof the business day.

To exclude a day (such asa Saturday or Sunday)from the work week, set<Day of the Week> to novalue.

FRI=9:00,16:00;

Business hours for Friday onlyare 9 AM to 4 PM.

SAT=;

SUN=;

Excludes Saturday andSunday from the work week.

26 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 43: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 5. Business Calendar Parameters (continued)

Parameter Description Examples

<Date>=<Start_Time_1, End_Time_1>;...<Start_Time_N,End_Time_N>;

or

<Date>=;

Optional. Overrides theEVERYDAY setting and the<Day of the Week> settingfor the specified date only.

Defines the businesshours for a specific date,where <Date> is inyyyy/mm/dd format and<Start_Time> and<End_Time> are thestarting and ending timesof the business day.Multiple ranges can bespecified, separated by asemicolon.

To exclude a date (such asa holiday) from the workyear, set <Date> to novalue.

2010/12/01=9:00,12:00;15:30,17:00;

Business hours for 12/01/2010are 9 AM to 12 PM and 3:30PM to 5 PM.

2010/12/25=;

Excludes a holiday from thework year.

<Date>=DST <Time_Offset> Optional. Adjusts hourson a specified date forDST.

<Date> is in yyyy/mm/ddformat and <Time_Offset>is either the number ofhours to set the timeforward in the spring(four hours maximum) orzero to return to standardtime.

2010/04/20=DST(1);

Sets DST one hour forward inthe spring.

2010/10/19=DST(0);

Resets to standard time in thefall.

CALENDAR_END=<Date>; Required. Defines the lastdate the calendar is valid,where <Date> is inyyyy/mm/dd format. Thecalendar cannot be usedpast the date specified bythis parameter.

If timer expiration is set

after this date, then theprocess will go into anerror state with an arrayout of bounds error.

CALENDAR_END=2010/12/31;

Last valid date for thiscalendar is 12/31/2010.

Chapter 1. Authoring workflows 27

Page 44: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Table 5. Business Calendar Parameters (continued)

Parameter Description Examples

CALENDAR_BEGIN=<Date>; Required. Defines the firstdate the calendar is valid,where <Date> is inyyyy/mm/dd format. Thecalendar cannot be usedbefore the date specifiedby this parameter.

If timer expiration is set

before this date, then theprocess will go into anerror state with an arrayout of bounds error.Note: The maximumcalendar duration is tenyears. Therefore, theCALENDAR_BEGIN andCALENDAR_END valuescannot be more than tenyears apart.

CALENDAR_BEGIN=2003/01/01;

First valid date for thiscalendar is 01/01/2003.

TIMEZONE=<Timezone_Offset>;

Required. Defines thelocal time zone relative toGreenwich Mean Time(GMT).

TIMEZONE=-8:00

Sets the U.S. Pacific time zone,which is 8 hours behind GMT.

Assigning business calendars to process definitionsYou can assign different business calendars to a process definition.

About this task

Note that you must have created a business calendar as described in “Creatingyour own business calendars” on page 24 before you can assign it to a processdefinition.

Procedure1. Open the Properties window for the process definition.2. Select the User Defined Attributes tab.3. Add the UDA __businessCalendar of type STRING to the process definition.

Specify the name of your business calendar without the .cal extension as itsvalue.

4. Click OK to dismiss the Properties window.

Note: You can change calendars while a process is running using thesetProcessAttribute JavaScript and the __businessCalendar UDA. For example tochange the business calendar to Calif.cal, you would use the followingJavaScript:setProcessAttribute("__businessCalendar","string","Calif");

Assigning business calendars to due dates or timersYou can assign a business calendar to a due date or timer. The due date or timer isthen calculated based on this business calendar.

28 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 45: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

About this task

Note that you must have created a business calendar as described in “Creatingyour own business calendars” on page 24 before you can assign it to a due date ortimer.

Procedure1. Define an advanced timer or an advanced due date.2. In the Set Expression field, enter the following expression:

UC(<business_calendar>); where <business_calendar> is the name of yourbusiness calendar.

Note: Do not include the .cal extension when specifying the name of thebusiness calendar, as this will cause an error when running the job.

Using Java action sets with workflowsJava actions can be used to customize the execution of your process definition. Youcan invoke Java actions at the same points of process execution as JavaScripts.

The following list displays possible points of execution:v Before an activity starts (Prologue Actions and Role Actions)v At activity completion (Epilogue Actions)v When a timer expires (set by a Timer Action)

Assigning Java actionsYou can assign Java Actions to either the process definition as a whole or toindividual nodes (except for the Start and Exit nodes).

Procedure1. In Interstage BPM Studio, open the process definition in the Process Definition

Editor pane.2. Right-click a blank area in the process definition or right-click a selected node

and click Properties.3. In the Properties window for the process definition or selected node, select the

User Defined Attributes tab and add the data items you need for your JavaAction.

Note: If you do not add the correct data items to your process definition, yourJava Action may work unpredictably. For example, in Generic Java Actions themethod that you want to use in your Java Action may be unavailable. Amethod is available only if all the data items that it uses are defined as UDAs.Also in Generic Java Actions, only methods that use non-primitive data types(String, Integer, Float, and so on) display in the Method Name list.

4. Select the Action Set tab.5. In the Action Set tab, select the tab that applies to the position where you want

to add the Java Action: Role Actions, Prologue Actions, or Epilogue Actions.6. Click the Add button. The Action Type List window displays.

Chapter 1. Authoring workflows 29

Page 46: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Results

At this point in the procedure, see “Available Java actions” on page 31 for furtherinstructions on how to configure specific Java Actions.

Editing Java actionsYou can edit Java Actions that have been assigned to either the process definitionas a whole or to individual nodes.

Procedure1. In Interstage BPM Studio, open the process definition in the Process Definition

Editor pane.2. Right-click a blank area in the process definition or right-click a selected node

and click Properties.3. In the Properties window for the process definition or selected node, select the

User Defined Attributes tab and add the data items you need for your JavaAction.

4. Select the Action Set tab.5. Select the appropriate action tab category and then select the Java Action you

want to edit.6. Right-click and click Edit. The action editor for the selected action type

displays. Instructions for configuring Java Actions are provided in “AvailableJava actions” on page 31.

Copying Java actionsIf you want to use a Java Action that is assigned to a process definition at anotherpoint of execution in the process definition, you can use the following instructionsto copy it. For example, you may want to reuse the Java Action you defined in theprocess definition for a Role Action as a Prologue Action.

Procedure1. In Interstage BPM Studio, open the process definition in the Process Definition

Editor pane.2. Right-click a blank area in the process definition or right-click a selected node

and click Properties.3. In the Properties window for the process definition or selected node, select the

Action Set tab.4. Select the appropriate action tab category for the source Java Action, such as

Role Actions.5. Right-click the Java Action you want to copy and click Copy.6. Select the destination action tab category in which you want to paste the copied

Java Action.7. Right-click and click Paste. The copied Java Action displays.8. Save the process definition to store your changes.

Removing Java actionsIf you no longer want to use a Java Action that is assigned to a process definitionor node, you can use the following instructions to remove it.

30 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 47: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Procedure1. In Interstage BPM Studio, open the process definition in the Process Definition

Editor pane.2. Right-click a blank area in the process definition or right-click a selected node

and click Properties. The Properties window displays for the process definitionor the selected node.

3. In the Properties window for the process definition or selected node, select theAction Set tab.

4. Select the appropriate action tab category.5. Right-click the Java Action you want to remove and click Remove. The Java

Action is removed from the process definition or selected node.6. Save the process definition to store your changes.

Available Java actionsThis section describes how to configure specific Java Actions.

Note:

v In a Role Action set, you should only configure those Java Actions thatdetermine the assignee for a task (for example, the Assign Task to User JavaAction or the Escalate Task Java Action).

v If a task is assigned to a group as a default assignee when the task is created, aRole Java Action can only assign the task to a user who is a member of thatgroup. If a task is assigned to a user as a default assignee, then a Role JavaAction can assign the task to any user at runtime.

Assign task to userWhen modeling a task, you assign it to a role according to who is responsible forcompleting the activity. In some situations, however, you may want to assign anactivity to a particular user, and not just to any user who is a member of a certainrole. This can be achieved using the Assign Task to User Java Action.

Once you reassign a task to a particular user or users, it is assigned only to them.You can add this Java Action only to Task nodes or Voting Task nodes.

You can use either of the following two methods to select users for an Assign Taskto User Java Action:v “Using a workflow variable expression to select users”v “Using group and user lists to select users” on page 32

Using a workflow variable expression to select usersYou can use a workflow variable expression to reassign a task to users.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29. Make sure

that you select the Role Actions tab.2. Expand the Server Actions folder, then double-click Assign Task to User.3. In the Assignment Selection tab in the Assign Task to window, select the Use

Workflow Variable check box. A text field appears with the Expression Modeand Expression Builder buttons.

Chapter 1. Authoring workflows 31

Page 48: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

4. Enter an expression in the text field for the users to whom you want toreassign the task. The Expression Mode button next to the entry field denotesthe mode of entry for the text field. The button has three modes correspondingto three different expression modes:

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.The expression entered in the text field, whether it is a simple UDA name or amore complex expression, must be resolved into a user or users within the roleto which the task is currently assigned.

5. In the Details tab, optionally type a descriptive name and any notes for theJava Action.

6. Click the OK button on the Assign Task to window. Your Java Action appearsin the Role Actions tab in the Action Set tab of the properties window.

7. Click OK to close the properties window.

Using group and user lists to select usersYou can use selection lists to reassign a task to users.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29. Make sure

that you select the Role Actions tab.2. Expand the Server Actions folder, then double-click Assign Task to User.3. In the Assignment Selection tab in the Assign Task to window, clear the Use

Workflow Variable check box.4. For each user to whom you want to reassign the task, complete the following

steps.a. In the Group field, select the group to which the user belongs.

The Users box displays all of the users in the selected group.b. In the Users box, select the users to whom you want to reassign the task.

Note: You can use Ctrl-click or Shift-click to select multiple users.c. Click Add. The Selected Users box now lists the users that you selected.

Note: To remove users from the Selected Users box, select them and clickRemove.

5. In the Details tab, optionally type a descriptive name and any notes for theJava Action.

6. Click the OK button on the Assign Task to window. Your Java Action appearsin the Role Actions tab in the Action Set tab of the properties window.

7. Click OK to close the properties window.

32 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 49: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Using the Assign UDA from XPath Expression Java actionThe Assign UDA from XPath Expression Java action parses data from an XMLstring coming in to the IBM OpenPages GRC Platform workflow server andassigns the parsed data to the UDAs specified in properties.

About this task

This Java Action is usually used in conjunction with an HTTP Agent. Thisthree-component system forms a data-transfer interface to a system external to IBMOpenPages GRC Platform.

Information on applications for which these Java Actions might be used, how todesign the XML string expressions, or how to write the XPath expressions isbeyond the scope of this guide.

To parse incoming data using the Assign UDA from XPath Expression Java Action,do the following.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the XML Actions folder, then double-click Assign UDA from XPath.3. In the Assign UDA from XPath expression window, enter a name for your

Assign UDA from XPath Expression Java Action in the Action Name field.4. Select a UDA for your Assign UDA from XPath Expression Java Action from

the Source UDA field. This UDA contains an XML string from which yourUDA data will be parsed.

5. Select the UDA to which you want to move data in the Target UDA field.6. In the XPath of target UDA field, enter the XPath expression that specifies

where the data will be stored in the XML string of the target UDA. This field isonly active if you have selected a UDA of type XML.

7. In the XPath of source UDA field, enter the XPath expression that specifieswhere the data can be found in the XML string of the Source UDA.

8. Click OK. Your Java Action appears in the Action Set tab of the propertieswindow.

9. Click OK to close the properties window. Your Assign UDA from XPathExpression Java Action is now assigned to the process definition. You canattach these actions to map XML data in any one of the action sets.

Using the Escalate Task Java actionWhen defining a due date for a task, you also define what happens when the duedate is reached and the task has not been completed. One option is to escalate thetask to additional users using the Escalate Task Java action. The same applies whenyou define a timer for a task: you can escalate the activity when the timer expires.

The Escalate Task Java action can only be assigned to the Java action pane of atimer or due date specified on a Task node or Voting Task node. When the timer ordue date fires, the Escalate Task Java action is executed, and the task is reassignedto another user or group.

You can use either of the following two methods to select users for an EscalateTask Java action:v “Using a workflow variable expression to select users” on page 34v “Using group and user lists to select users” on page 34

Chapter 1. Authoring workflows 33

Page 50: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Using a workflow variable expression to select usersYou can use a workflow variable expression to escalate a task to users.

Procedure1. In the Timers or Due Date tab in the properties window, define a timer or due

date for a Task node or a Voting Task node, as described in “Configuring timersand due dates” on page 18.

2. Click the Add button.3. Expand the Server Actions folder, then double-click Escalate Task.4. In the Assignment Selection tab in the Escalate Task to window, select the Use

Workflow Variable check box. A text field appears with the Expression Modeand Expression Builder buttons.

5. Enter an expression in the text field for the users to whom you want to escalatethe task. The Expression Mode button denotes the mode of entry for the textfield. The button has three modes corresponding to three different expressionmodes:

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.The expression entered in the text field, whether it is a simple UDA name or amore complex expression, must be resolved into a user or users within the roleto which the task is currently assigned.

6. In the Details tab, optionally type a descriptive name and any notes for theJava Action.

7. When you are finished, click the OK button to return to the Timers or DueDate tab.

Results

The Escalate Task Java Action opens in the Java Action pane of the tab.

Using group and user lists to select usersYou can use selection lists to escalate a task to users.

Procedure1. In the Timers or Due Date tab in the properties window, define a timer or due

date for a Task node or a Voting Task node, as described in “Configuring timersand due dates” on page 18.

2. Click the Add button.3. Expand the Server Actions folder, then double-click Escalate Task.

34 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 51: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

4. In the Assignment Selection tab in the Escalate Task to window, clear the UseWorkflow Variable check box.

5. For each user to whom you want to escalate the task, complete the followingsteps.a. In the Group field, select the group to which the user belongs.

The Users box displays all of the users in the selected group.b. In the Users box, select the users to whom you want to reassign the task.

Note: You can use Ctrl-click or Shift-click to select multiple users.c. Click Add. The Selected Users box now lists the users that you selected.

Note: To remove users from the Selected Users box, select them and clickRemove.

6. In the Details tab, optionally type a descriptive name and any notes for theJava Action.

7. When you are finished, click the OK button to return to the Timers or DueDate tab. The Escalate Task Java action now displays in the Java Action pane ofthe tab.

Using the Evaluate Script Java actionThe Evaluate Script Java Action provides you with JavaScript functionality in aJava action. It allows you to combine other Java Actions with JavaScript in aparticular JavaAction set and control the order of JavaScript execution in relation tothe other JavaScripts. Also, multiple scripts can be evaluated in any order using aseries of these actions in action sets.

This section only provides instructions on how to add this Java action. It providesno information on writing the JavaScript for it. IBM OpenPages GRC Platformprovides an additional set of JavaScript commands for retrieving information fromthe workflow server or sending information. These JavaScripts are described inChapter 2, “Workflow JavaScript functions,” on page 47.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder and then double-click Evaluate Script.3. In the Evaluate Script window displays, enter your script in the Script text area.

You can also paste the script into the Script text area and edit it.4. Select the Details tab and enter a name and any notes for your Evaluate Script

action in the Action Name field.5. Click OK. Your Java Action appears in the Action Set tab of the properties

window.6. Click OK to close the properties window. Your Evaluate Script Java Action is

now assigned to the process definition.

Using the Get Performer Java actionYou can use this Java action only in the Epilogue Action field of a task. It assignsthe name of the user completing the task to the specified UDA. Before you can usethis Java Action, you must first create a UDA to which the user can be assigned.

About this task

Note: You can add this Java action only to Task nodes or Voting Task nodes.

Chapter 1. Authoring workflows 35

Page 52: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29. Make sure

that you select the Epilogue Actions tab.2. Expand the Server Actions folder and then double-click Get Performer.3. In the Get Performer window, select a UDA from the Target UDA list. This Java

Action assigns the name of the user completing the activity to the UDAselected in the Target UDA list.

4. Click OK. Your Java action appears in the Action Set tab of the propertieswindow.

5. Click OK to close the properties window. Your Get Performer Java action isnow assigned to the process definition.

Using the Get Process Initiator Java actionThe Get Process Initiator Java action assigns the name of the user who started thisprocess instance to the specified UDA. Before you can use this Java action, youmust first create a UDA to which the process initiator can be assigned.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder and then double-click Get Process Initiator.3. In the Get Process Initiator window, select a UDA to which the process

initiator's name is to be assigned from the Target UDA list.4. Click OK. Your Java action appears in the Action Set tab of the properties

window.5. Click OK to close the properties window. Your Get Process Initiator Java Action

is now assigned to the process definition.

Using the Make Choice Java actionThe Make Choice Java action allows you to make a particular choice on a workitem automatically using a JavaScript. The Make Choice Java action can only beassigned to the Java action pane of a timer specified on a Task node or Voting Tasknode.

Procedure1. In the Timers tab in the properties window, define a timer for a Task node or a

Voting Task node, as described in “Configuring timers and due dates” on page18.

2. Click the Add button.3. Expand the Server Actions folder, then double-click Make Choice.4. In the Choice field in the Make Choice window, enter an expression. The

Expression Mode button next to the entry field denotes the mode of entry forthe field. The button has three modes corresponding to three differentexpression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

36 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 53: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.5. Enter a name for your Make Choice action in the Action Name field.6. When you are finished, click the OK button to return to the Timers tab. The

Make Choice Java action now displays in the Java action pane of the Timerstab.

Using the Set Process Name Java actionBy default, a process instance is given the same name as the process definitionfrom which it was created. However, its name can be changed while the process isrunning using the Set Process Name Java action.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder, then double-click Set Process Instance Name.3. In the Process Name field in the Set Process Name window, enter an

expression. The Expression Mode button next to the entry field denotes themode of entry for the field. The button has three modes corresponding to threedifferent expression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.4. Enter a name for your Set Process Instance Name action in the Action Name

field.5. Click the OK button on the Set Process Name window. Your Java action

appears in the Action Set tab of the properties window.6. Click OK to close the properties window.

Using the Set Process Priority Java actionBy default, a process instance is given a medium priority. However, its priority canbe changed while the process instance is running using the Set Process InstancePriority Java action. You can choose between low, medium and high priority.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder, then double-click Set Process Instance

Priority.

Chapter 1. Authoring workflows 37

Page 54: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

3. In the Process Priority field in the Set Process Priority window, enter anexpression. The expression must evaluate to an integer value of either 0 (lowpriority, 8 (medium priority), or 16 (high priority).The Expression Mode button next to the entry field denotes the mode of entryfor the field. The button has three modes corresponding to three differentexpression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

4. Enter a name for your Set Process Instance Priority action in the Action Namefield.

5. Click the OK button on the Set Process Priority window. Your Java actionappears in the Action Set tab of the properties window.

6. Click OK to close the properties window.

Using the Set Process Description Java actionBy default, a process is given the same description as the template from which it iscreated. However, its description can be changed while the process is runningusing the Set Process Description Java action.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder, then double-click Set Process Instance

Description.3. In the Process Description field in the Set Process Description window, enter

an expression. The expression must evaluate to a string value.The Expression Mode button next to the entry field denotes the mode of entryfor the field. The button has three modes corresponding to three differentexpression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.

38 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 55: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

4. Enter a name for your Set Process Instance Description action in the ActionName field.

5. Click the OK button on the Set Process Description window. Your Java actionappears in the Action Set tab of the properties window.

6. Click OK to close the properties window.

Using the UDA Assignment Java actionUDA Assignment Java actions allow you to assign the value of one UDA toanother. You can also assign a value to a UDA.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Server Actions folder, then double-click UDA Assignment.3. In the Target UDA field in the Set Process Description window, select the UDA

to which you want to assign a value.4. In the Value field, enter an expression.

The Expression Mode button next to the entry field denotes the mode of entryfor the field. The button has three modes corresponding to three differentexpression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.5. Enter a name for your UDA Assignment action in the Action Name field.6. Click the OK button on the UDA Assignment window. Your Java action

appears in the Action Set tab of the properties window.7. Click OK to close the properties window.

Using the SendEmail Java actionThis Java action is used to send email messages. It can be used to notify anyonethat a process has been created or an activity has been started.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the Notification Actions folder, then double-click SendEmail.3. In the Send Email window, make sure that the Addresses tab is selected and do

the following for each email address you want to configure:a. Enter an expression for the email address:

The Expression Mode button next to the entry field denotes the mode ofentry for the field. The button has three modes corresponding to threedifferent expression modes.

Chapter 1. Authoring workflows 39

Page 56: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA asthe assignee.

Expression ModeButton displays the letter E. Used for complex expressions. Youmight use this if you want the value of a UDA to choose amongmultiple assignees. Click the A+B Expression Builder button todisplay the Expression Builder.

Clicking the Expression Mode button cycles through the different modes.b. Click the button corresponding to how you want the message addressed.

For example, if you want the address to appear in the To field, click To. Theaddress will move to the To field. When you have completed addingaddresses, click the Content tab.

4. In the Content tab, enter a subject in the Subject field and message text in theBody field. Note that you can use an expression, as described in the previousstep. Select the format in which you want your message to be sent by selectingeither Plain Text or HTML.

5. In the Details tab, enter a name for your SendEmail action in the Action Namefield.

6. Click the OK button on the Send Email window. Your Java action appears inthe Action Set tab of the properties window.

7. Click OK to close the properties window.

Using the Set Resource Property Java actionThe Set Resource Property Java action is used to set a new value for the availableresource properties. Resource properties are listed as UDAs that start with the IBMOpenPages GRC Platform object type, such as SOXRisk or SOXControl.

About this task

You can only set resource properties for the object type used to start the workflow,even if other properties are defined in the list of UDAs.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the OPX Actions folder, then double-click Set Resource Property.3. In the Set Resource Property window, select the resource property to be

modified from the list.4. In the New Value field, enter an expression.

The Expression Mode button next to the entry field denotes the mode of entryfor the field. The button has three modes corresponding to three differentexpression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

40 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 57: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA as theassignee.

Expression ModeButton displays the letter E. Used for complex expressions. You mightuse this if you want the value of a UDA to choose among multipleassignees. Click the A+B Expression Builder button to display theExpression Builder.

Clicking the Expression Mode button cycles through the different modes.

Note: If you are entering a multi-valued enum type, the values should beseparated by commas (for example: Existence, Completeness).

5. Enter a name for your Set Resource Property action in the Action Name field.6. Click the OK button on the Set Resource Property window. Your Java action

appears in the Action Set tab of the properties window.7. Click OK to close the properties window.

Using the Get User Email Address Java actionThis Java action allows workflow administrators to specify a list of users whoseemail addresses will be assigned to a user-defined attribute.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Expand the OPX Actions folder, then double-click Get User Email Address.3. On the Assignment Selection tab of the Get User Email Address window,

select the UDA that will contain the list of email addresses from the TargetUDA list.

4. You can designate the email addresses using either of the following methods.v From the Group list, select the group that contains the users whose email

addresses you want to add. Select the desired users and click the Add buttonto add the users to the Selected Users list.

v Alternatively, select the Use Workflow Variable check box to enable anexpression field. The Expression Mode button next to the entry field denotesthe mode of entry for the field. The button has three modes corresponding tothree different expression modes.

Constant ModeButton displays the letter C. Used for simple constant (literal)expressions. To enter a value, simply type it into the field.

Variable ModeButton displays the letter V. Used for simple variable (user-definedattribute) expressions. This mode allows the user to pick a UDA asthe assignee.

Expression ModeButton displays the letter E. Used for complex expressions. Youmight use this if you want the value of a UDA to choose amongmultiple assignees. Click the A+B Expression Builder button todisplay the Expression Builder.

Clicking the Expression Mode button cycles through the different modes.5. On the Details tab, enter a name for your Get User Email Address action in the

Action Name field.

Chapter 1. Authoring workflows 41

Page 58: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

6. Click the OK button on the Get User Email Address window. Your Java actionappears in the Action Set tab of the properties window.

7. Click OK to close the properties window.

Using the Generic Java actionGeneric Java actions allow you to execute Java business methods that are outsidethe scope of the OpenPages GRC Platform system. Using Generic Java actions, youcan customize your business processes using methods within autonomous Javaclasses that you have written and compiled yourself.

About this task

The following procedure applies to adding a Generic Java action to a processdefinition.

Procedure1. Copy the Java class that you want to use. You must differentiate whether you

are working with an application project or a server project:

Application project In the application project's folder structure, store the Java class files inthe Application Classes > engine > classes folder in the Navigatorpane.

Server projectCopy the Java class files to the <drive>:<Workflow_Home>\ibpm\Data\attachments folder in Windows, where <drive>:<Workflow_Home> isthe location of the Interstage BPM Studio installation files (defaultlocation is C:\OpenPages\IBPMStudio).

2. Follow the instructions in the “Assigning Java actions” on page 29.3. Double-click Generic Java Action.4. In the Generic Java Action window, enter a name for your Java action in the

Action Name field.5. Click the Browse (...) button.6. In the Select Java Class window, navigate to the class that you will use for

your Java action, then click the class file to highlight it. The full path withclass name appears in the Path field of the window.

7. Check to make sure that you are specifying the correct class, then click OK.The window re-displays with the name of your class in the Class Name field,and the path to your class in the Class Path field.

8. Select the method that you want to use in your Java action from the MethodName list.

9. In the Return Value list, select the UDA that will receive the return value, ifany, from your Java action method.

10. Check the UDA Mapping section. Verify that the UDAs are mapped correctlyto the method parameters. These UDAs will provide input values to themethod. Note that mapping UDAs to the method parameters requiresknowledge of the method that you are calling.

11. Click the OK button on the Generic Java Action window. Your Java actionappears in the Action Set tab of the properties window.

12. Click OK to close the properties window.

42 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 59: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Using No-Operation Java actionsNo-Operation Java actions are built-in Java actions that specify no operation. TheseJava actions allow you to catch a Java action exception without executing anyadditional actions. Using No-Operation Java actions, a workflow simply moves onto the next sequential instruction. You can assign No-Operation Java actions toprocess definitions or nodes.

About this task

For example, you have created a Generic Java action, such as a Sending an emailmessage Java action. For this Java action, you have defined a No-Operation Javaaction as an Error action. An error might occur if the recipient's mailbox is full sothat all incoming emails are bounced back to the sender. If executing the job ismore important than sending the email, you can define a No-Operation action asan Error action. This assures that the job continues regardless of the error.

Procedure1. Follow the instructions in the “Assigning Java actions” on page 29.2. Double-click No-Operation Java Action.3. In the No Operation Java Action window, enter a descriptive name for your

Java action in the Action Name field.4. Click the OK button on the No Operation Java Action window. Your Java

action appears in the Action Set tab of the properties window.5. Click OK to close the properties window.

Accessing computed fields from workflowsThe ExecuteComputedField process definition is a standard predefined processdefinition supplied by IBM OpenPages GRC Platform, Inc. and should be used asthe only method for retrieving computed field values in workflows.

For information about computed fields, see “Creating Computed Fields” in theIBM OpenPages Administrators Guide.

About this task

The ExecuteComputedField process definition uses the configured Child Job nodeto spawn a subprocess that calculates and retrieves the value of a computed fieldwithin the workflow. Once a valid value is obtained for the computed field, anamed UDA is set in the parent workflow and processing continues.

To use the ExecuteComputedField process definition, you must configure aSubprocess node and map the list of UDAs to the input and output properties ofthe ExecuteComputedField process definition.

Example: You want to use the total actual financial loss amount associated witheach loss event in a workflow. You know that the Total Actual Financial Loss fieldis a standard supplied computed field for Loss Event objects, and that this fieldbelongs to the OpenPagesStandardLossEvent field group.

You could create a workflow for the LossEvent object type that returns the value ofthe computed field Total Actual Financial Loss, and then uses that returned valueat other points in the workflow (for example, to drive routing logic or contextualinformation in e-mails).

Chapter 1. Authoring workflows 43

Page 60: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Procedure1. Create a new process definition.2. Define the job owners.3. Add and invoke a Subprocess node.4. Select ExecuteComputedField for the process definition.5. Map the values (input and output parameters) to the ExecuteComputedField

process definition properties.

Note: Computed fields for Reporting Fragments are not supported inworkflows.

Configuring a computed field subprocess nodeWhen configuring a Subprocess node for a computed field, you define certainUDAs and then map these UDAs to the properties of the ExecuteComputedFieldprocess definition.

Before you begin

Have the following information available:v The name of the computed field you want included in a workflowv The name of the field group containing the computed fieldv The object type associated with the computed field

Procedure1. In Interstage BPM Studio, first add a project and process definition for the

parent job, as described in “Creating an application project and processdefinition name” on page 1, “Creating a server project for the processdefinition” on page 2, and “Building the process definition and addingproperties” on page 3.

2. In the Process Definition Properties window for the process definition, selectthe User Defined Attributes tab and add a row (Name and Data Type) foreach UDA listed in Table 6.

Note: The UDA Name column in Table 6 contains sample UDA name values.Substitute a name that you want for the values listed in this column.

Table 6. Required UDAs

UDA Name(defined by user) Description Data Type Example Default Value

FieldGroupName The name of the fieldgroup that contains thecomputed field.

Simple String OpenPagesStandardLossEvent

ComputedValue A container that willhold the value of thecomputed field.

Simple String

ComputedFieldName

The name of thecomputed field.

Simple String Total Actual Financial Loss

3. In the Process Definition Editor pane, complete the following steps.a. Click the Subprocess node on the palette and drop it onto the pane.b. Right-click the Subprocess node and click Properties.

44 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 61: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

4. To connect the parent process definition to the subprocess definition(ExecuteComputedField), complete the following steps.a. In the Child Job Node Properties window, select the Data Mapping tab.b. Click Select.c. In the Select Subprocess Definition window, click Get List.d. Select the ExecuteComputedField subprocess definition from the list and

click OK.5. In Child Job Node Properties window, map the UDAs as shown in Table 7.

Note: The system automatically prepends op_prop_ to user-defined UDAnames. For example, a UDA named ComputedValue becomesop_prop_ComputedValue. Substitute the value that you previously defined inTable 6 on page 44 for the type of UDA listed in the For this UDA column ofTable 7.

Table 7. UDA Mapping

Select thisMappingType... For this UDA...

Map it to this Sub-Plan DataItem...

And in the DataMapping row after it isadded...

LONG op_prop_<ObjectType>

op_prop_Input_Resource_Id Clear the Output box,and select the Inputbox.

STRING Field groupname

op_prop_Input_Bundle_Name Clear the Output box,and select the Inputbox.

Computed fieldname

op_prop_Input_Property_Name

Computedvalue

op_prop_Output_Computed_Value

Clear the Input box,and select the Outputbox.

6. When you are finished, click OK.7. If necessary, add other nodes to complete the process definition and then save

it.

Chapter 1. Authoring workflows 45

Page 62: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

46 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 63: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Chapter 2. Workflow JavaScript functions

Interstage BPM Studio provides a set of JavaScript functions for exchanginginformation with the IBM OpenPages GRC Platform application. This chapterdescribes these functions and provides examples.

Apart from functions listed in this chapter, you can also use the JavaScriptfunctionality that is defined in the ECMA Standard.

Functions for Java actions and complex conditional nodesYou can use the JavaScript functions described in this section in both Java actionsand complex conditional nodes.

string DateAdd(String Date, Int Offset, String field)Returns a JavaScript Date object (of type STRING) containing the date and time thatis the result of adding the Offset value to the Date.

The unit of time measure for Offset is determined by the field. Valid field valuesare:v "ss" - secondsv "mi" - minutesv "hh" - hoursv "dd" - daysvar now = CurrentDate();var tomorrow = DateAdd( now, 1, "dd");

If now (CurrentDate) has the following value:Tue Dec 02 2003 14:02:59 GMT-0800 (PST)

then tomorrow (DateAdd( now, 1, "dd")) has the following value:Tue Dec 03 2003 14:02:59 GMT-0800 (PST)

boolean DateCompare(String Date1, String Operator, StringDate2)

Compares two date values. Returns true or false as the result of the comparison.

Valid operators are:v ">" - greater thanv "<" - less thanv ">=" - greater than or equal tov "<=" - less than or equal tov "==" - equal tov "!=" - not equal tovar now = CurrentDate();var tomorrow = DateAdd( now, 1, "dd");if (DateCompare(now, "<", tomorrow))...; //... will execute because DateCompare evaluates to true.

47

Page 64: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

integer DateDiff(String Date1, String Date2, String field)Subtracts Date2 from Date1. Returns the difference between these date/times ineither days, hours, minutes or seconds depending on the field value.

Valid field values are:v "ss" - secondsv "mi" - minutesv "hh" - hoursv "dd" - daysvar now = CurrentDate();var tomorrow = DateAdd(now, 1, "dd");var diff = DateDiff(tomorrow, now, "dd"))//diff will have a value of 1.

boolean toBoolean(String or Integer value)Converts the String or Integer value to a JavaScript boolean. The value can beeither a String containing true or false, or a number containing zero or a nonzerovalue. Returns true or false depending on the value. If the value parameter cannotbe converted into a Boolean, then false is returned.

Functions for Java actions onlyYou can use the additional JavaScript functions described in this section only inJava actions. They are not supported for complex conditional nodes.

boolean addAttachment(String attachmentName, StringattachmentPath)

Adds the attachment stored at the specified path in the DMS to the process andgives it the specified name.addAttachment("FSC News","C:\\Test\\FSC_news.doc");// Native DMS Adapter and NT LDAP DMS Adapter.addAttachment("FSC News","\\opt2\\netscape\\suitesopt\\iflow\\docs\\FSC_news.doc");// Solaris LDAP

boolean deleteAttachment(String attachmentName)Deletes the attached file named in the argument.

string getActivityActor()Returns the name of the person who committed the work item that belonged to thecurrent activity. This command should only be used in an Epilogue Java action,and only for a Task node or Voting Task node.name=getActivityActor();

string getActivityAssignees()Returns a comma-separated list of names assigned to the current active Activity.This command is only useful in scripts that belong to an activity, such as a RoleJava action or an Epilogue Java action.names=getActivityAssignees();

48 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 65: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

string getActivityName()Returns the name of the current activity. Can only be used for Role, Prologue, orEpilogue Java actions.var name=getActivityName();setProcessAttribute("ActivityName","string",name);

array getAllAttachmentNames()Returns an array of names corresponding to all of the attachments on the currentprocess. If there are no attachments on the process, this function returns anexception. In the following example, the array of all attachment names is set toname. Then, the array is converted into a comma-separated list.var name = getAllAttachmentNames();var attList = "";for (var i=0; i<name.length; i++) {attList = attList + ", " + name[i];}setProcessAttribute("AttachmentList", "STRING", attList);

string getAttachment(String AttachmentName)Returns the file location and file name of the attachment whose name is specified.PathName=getAttachment("MyAttachment");setProcessAttribute("AttachmentPath","string",PathName);

string getGroupMembers(String groupName)Returns a comma-separated list of the members of the specified group. Uses theDirectory Service to determine this information.names=getGroupMembers("QA");//You might use the information returned by this command//in the following way.setProcessAttribute("Group Members","string",names);

string getInitiator()Returns the name of the person who initiated the process.name= getInitiator();setProcessAttribute("Process Initiator","string",name);

string getMembers(String groupName)Returns a merged list of all the immediate members of the specified group.names=getMembers("QA");//You might use the information returned by this command//in the following way.setProcessAttribute("Group Members","string",names);

string getOwners()Returns a comma-separated list of owners of the process.names= getOwners();setProcessAttribute("Template Owners","string",names);

string getProcessAttribute(String name)Returns the value of the process attribute that is specified. Only works for UDAsthat have been defined for a process definition.

Chapter 2. Workflow JavaScript functions 49

Page 66: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

SetProcessAttribute("Name","string","FSC");Value=getProcessAttribute("Name");SetProcessAttribute("Name2","string",Value);

int getProcessAttributeStringType(String name)Returns the type of the specified process attribute as an integer. The integer returnvalue corresponds to the data type of the specified process attribute. Use thefollowing table to determine the data type.

Table 8. Data Type

Return Value Data Type

0 Boolean

1 String

2 Integer

3 Float

4 Long

8 Big Decimal

9 Date

SetProcessAttribute("Name","string","FSC");Value=getProcessAttributeStringType("Name");SetProcessAttribute("Type","INTEGER",Value);

string getProcessDescription()Returns the description of the current process.description1= getProcessDescription();setProcessAttribute("Description","string", description1);

string getProcessInitiator()Returns the name of the person who initiated the current process.name= getProcessInitiator();setProcessAttribute("Process Initiator","string",name);

int getProcessInstanceId()Returns the ID of the current process to which this work item belongs.ID = getProcessInstanceId();

string getProcessName()Returns the name of the current process.name=getProcessName();setProcessAttribute("ProcessName","string",name);

string getProcessOwners()Returns a comma-separated list of owners of the process.names= getProcessOwners();setProcessAttribute("Template Owners","string",names);

int getProcessPriority()Returns the priority of the process. Process priorities are categorized as follows:high, medium, and low. This categorization of priorities is made according to thefollowing rules:

50 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 67: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

v HIGH - Any number greater than or equal to 16.v MEDIUM - Any number between eight and 16 (including eight).v LOW - Any number less than eight.priority1= getProcessPriority();SetProcessAttribute("Priority","integer",priority1);

string getProcessTitle()Returns the title of the current process.title1= getProcessTitle();setProcessAttribute("Title","string",title1);

boolean setActivityAssignees(String assignees)Takes a comma-separated list of names and uses them to assign the work items forthe current activity. This command should be used only in Role Java actions.setActivityAssignees("john,mary,chris");

boolean setOwners(String owners)Sets the owners of a process, where owners is a comma-separated list of users.Only administrators and current owners of the process may change ownership ofthe process.setOwners("chris,david");

boolean setProcessAttribute(String name, String value)Sets the value of an existing UDA with the specified name to the specified value.setProcessAttribute("Name","FSC");name1=getProcessAttribute("Name");setProcessAttribute("Name",name1);

boolean setProcessDescription(String description)Sets the given string as the description of the process.setProcessDescription("My Process description.");

boolean setProcessName(String name)Sets the given string as the name of the process. Name cannot exceed 64 charactersor include the \, |, /, :, *, ", <, or > characters.setProcessName("My Process name");

boolean setProcessOwners(String owners)Sets the owners of a process, where owners is a comma-separated list of users.Only administrators and current owners of the process may change ownership ofthe process.setProcessOwners("chris,david");

boolean setProcessPriority(int priority)Sets the process priority. Process priorities are categorized as follows: high,medium, and low. This categorization of priorities is made according to thefollowing rules:v HIGH - Any number greater than or equal to 16.v MEDIUM - Any number between eight and 16 (including eight).v LOW - Any number less than eight.

Chapter 2. Workflow JavaScript functions 51

Page 68: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

setProcessPriority(11);priority1= getProcessPriority();SetProcessAttribute("Priority","integer",priority1);

boolean setProcessTitle(String title)Sets the specified string as the process title.setProcessTitle("My Process title.");

52 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 69: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Notices

This information was developed for products and services offered worldwide.

This material may be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service. This document maydescribe products, services, or features that are not included in the Program orlicense entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

53

Page 70: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationLocation Code FT0550 King StreetLittleton, MA01460-1250U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

54 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 71: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

Copyright

Licensed Materials - Property of IBM Corporation.

© Copyright IBM Corporation, 2003, 2016.

US Government Users Restricted Rights – Use, duplication or disclosure restrictedby GSA ADP Schedule Contract with IBM Corp.

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written.

These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM for the purposes of developing, using, marketing, ordistributing application programs conforming to IBM's application programminginterfaces.

Trademarks

IBM, the IBM logo and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.

The following terms are trademarks or registered trademarks of other companies:v Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.v Java and all Java-based trademarks and logos are trademarks or registered

trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “ Copyright andtrademark information ” at www.ibm.com/legal/copytrade.shtml.

Notices 55

Page 72: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

56 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 73: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

Index

AaddAttachment JavaScript function 48AND node xiiiAnnotation tool xiiiapplication project

about 1copying 11deleting 12

Arrow element xiii, 3, 4Arrow tool xiii, 3Assign Task to User Java Action 31Assign UDA from XPath Expression Java Action 33

Bbusiness calendar

assigning to due dates or timers 29assigning to process definition 28creating 24parameters and format 25

CChained-Process node xiiiChild Job node. See Subprocess node. xiiiComplex Conditional node xiiicomputed fields 43Conditional node xiiicreating process definition 1

DDateAdd JavaScript function 47DateCompare JavaScript function 47DateDiff JavaScript function 48Delay node xiiideleteAttachment JavaScript function 48Draft version numbering 5due dates

assigning business calendar to 29defining 19time and day codes for 22

Eediting process definitions 11email node xiiiEscalate Task Java Action 33Evaluate Script Java action 35Exit node 3, 4

GGet Performer Java action 35Get Process Initiator Java action 36getActivityActor JavaScript function 48getActivityAssignees JavaScript function 48getActivityName JavaScript function 49

getAllAttachmentNames JavaScript function 49getAttachment JavaScript function 49getGroupMembers JavaScript function 49getInitiator JavaScript function 49getMembers JavaScript function 49getOwners JavaScript function 49getProcessAttribute JavaScript function 50getProcessAttributeStringType JavaScript function 50getProcessDescription JavaScript function 50getProcessInitiator JavaScript function 50getProcessInstanceId JavaScript function 50getProcessName JavaScript function 50getProcessOwners JavaScript function 50getProcessPriority JavaScript function 51getProcessTitle JavaScript function 51Group element xiii

HHelp system viihierarchical job

setting up 17

IInterstage BPM Studio

features not supported in OpenPages vifeatures supported in OpenPages xvonline help system viistarting the application xiWorkbench window xi

JJava action

Evaluate Script 35Get Performer 35Get Process Initiator 36Make Choice 36SendEmail 39Set Process Description 38Set Process Name 37Set Process Priority 37UDA Assignment 39

Java Actionadding to a process definition 8, 29Assign Task to User 31Assign UDA from XPath Expression 33copying 30editing 30Escalate Task 33removing 31

jobdefinition of viienabling signature for 15hierarchical 17

job instance. See task. viijob type. See process definition. vii

57

Page 74: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

MMake Choice Java action 36

NNavigator pane xinode xiii

AND node xiiiChained-Process node xiiiComplex Conditional node xiiiConditional node xiiidefining due date for 19defining timers for 20definition of viiDelay node xiiiemail node xiiiExit xiiiExit node 3, 4OR node xiiiSpawn Jobs node xiiiStart viii, xiiiStart node 3, 4Subprocess node xiiiTask viiiTask node xiii, 3, 4Voting Task node xiii

Ooffline mode vii, ix, xv, 5online and offline editing modes compared ixonline mode vii, xv, 1, 2, 5OR node xiiiOutline pane xiiOverview pane xi

PPalette xii, 3process definition

adding Java Actions to a 8assigning business calendar to 28associating with object type 6copying 12creating 1defining timers for 20definition of vii, viiideleting 12editing 11elements xiiiimporting and exporting 13publishing to OpenPages 9specifying UDAs 14

Process Definition Editor pane xiiproject

definition of viiProperties pane xiipublishing a process definition 9

RReporting Fragment fields vireports

in tasks 15

SSelect tool 4SendEmail Java action 39server project 1, 2, 5

deleting 12Set Process Description Java action 38Set Process Name Java action 37Set Process Priority Java action 37setActivityAssignees JavaScript function 51setOwners JavaScript function 51setProcessAttribute JavaScript function 51setProcessDescription JavaScript function 51setProcessName JavaScript function 51setProcessOwners JavaScript function 51setProcessPriority JavaScript function 51setProcessTitle JavaScript function 52signatures 15Spawn Jobs node xiiiStart node viii, xiii, 3, 4starting Interstage BPM Studio xiSubprocess node xiiiSwimlane element xiii

Ttask

definition of viiusing reports in a 15

Task node viii, xiii, 3, 4timers

assigning business calendar to 29defining 20time and day codes for 22

toBoolean JavaScript function 48

UUDA Assignment Java action 39UDAs

specifying in a process definition 14Undo function xiiuploading process definition to workflow server 5

VVoting Task node xiii

WWorkbench window

menu bar xiNavigator pane xiOutline pane xiiOverview pane xiPalette xiiProcess Definition Editor pane xiiProperties pane xiitoolbar xi

WorkflowAdministrators group x, 1Workflows

about viiaccessing computed fields from 43life cycle x

58 IBM OpenPages GRC Version 7.3.0: Workflow Author's Guide

Page 75: IBM OpenPages GRC Version 7.3.0: Workflow Author's Guidepublic.dhe.ibm.com/software/data/cognos/...The Interstage BPM application and IBM OpenPages GRC Platform Interstage Business

XXPDL format 3, 13

Index 59


Recommended