Process Workflow

Process Workflow User Guide

Process Workflow User Guide

1

Process Workflow Overview

3

What is Process Workflow? PW Setup Enquiries PW.STATUS PW.TRANSITION PW.VERB and PW.ACTIVITY.OBJECT PW.PARTICIPANT PW.ACTIVITY PW.PROCESS.DEFINITION API Overview Process Workflow Deal Processing Overview Used Records for ENROL.CUSTOMER process PW Designer Installation Instructions for PW Designer Creating a PW Designer Project Modeling a Process Deploy a Process into T24 Check-Out a Process from T24 Troubleshooting instructions for PW Designer Pattern Based Workflow Arbitrary Looping Structured Looping Recursion Parallel Split Switch construct Process Workflow Glossary ACTIVITY : Process : Launching User:

Process Workflow User Guide- Release R13.00 -Page 2 of 85 - (c) Temenos Systems 2013 18/07/2013

4 5 6 9 10 11 12 13 15 19 21 23 38 39 42 45 50 52 59 63 64 67 72 76 79 82 83 84 85

Process Workflow Overview T24 Process Workflow is aimed at grouping various businesses and banking procedures into a logical process of activities. This grouping enables allocation of work to different users, ensuring vital tasks are not left out causing a breakdown or delay in the process chain Individual activities are defined at micro level defining rules, statuses and user groups, which can all be reused. These activities are then set out in a pre-defined sequence allowing a customized business processed to be followed. This module does not in itself carry business functionality but can be used to define and tune the flow of business supported by other T24 modules. It can be seen as a way of linking together T24 applications, providing automatic mapping and directing of tasks to appropriate task members and groups. Click for more in formation on what is a Process Workflow

Process Workflow User Guide- Release R13.00 -Page 3 of 85 - (c) Temenos Systems 2013 18/07/2013

What is Process Workflow? What do you understand by the words process and workflow in general? A process is a particular course of action intended to achieve an end result.A workflow is progress of work done by a business. Therefore, Process Workflow is a series of steps through which work is routed to achieve a result. Examples of real-time workflows are Customer Feedback processes, Employee appraisal workflows etc. Now that you know the meaning of Process Workflow, what do you think could be the need for Process Workflow in T24? All banks have processes defined even for the simplest of activities. The Process Workflow product allows you to build these processes into T24. In short, the PW module is aimed at grouping various business and banking procedures into logical processes of activities. The advantage of this module is that, a process can be handled with the least amount of business expertise. For example, Mr. Brown who is currently not a customer of your bank, walks in and wants to open an account. Does he go straight to the account opening desk? The bank will have a process defined for circumstances like this. Firstly, the bank needs to know whether Mr. Brown is an existing or a new customer. Based on the information provided, you might have to either open a current account or savings account.

Process Workflow User Guide- Release R13.00 -Page 4 of 85 - (c) Temenos Systems 2013 18/07/2013

PW Setup PW Configuration requires the creation/identification of multiple settings with several dependencies. A composite screen, PW.BUILDER, is supplied with Model Bank to ease in the configuration of workflows. All applications required for the configuration of a process workflow should be found within the composite screen of PW.BUILDER, however for the purposes of documentation this screen has not been used, since at any one time only a small component of it would require illustration.

Pre-Setup Configuration In order to work, AUTO.ID.START needs to be configured. By ModelBank default, this will have been provided by default. If not, please see AUTO.ID.START for more information

Process Workflow User Guide- Release R13.00 -Page 5 of 85 - (c) Temenos Systems 2013 18/07/2013

Enquiries There are two principle ways in which activities may be presented to a user l

Through Auto Screen Creation where the user who caused the activity to be launched, is also within the team that can action that activity.

l

By drilling down on an enquiry, which lists outstanding activities that require action.

There are multiple enquiries incorporated into ModelBank, to assist the workflows of specific roles and departments. This guide will focus on the two basic, principle enquiries, upon which the others are based. These are: l

PROCESS.STATUS - which gives a view of the overall process

l

TO.DO - which lists the activties within the process, for direct action.

ModelBank Configuration : It is possible to view a version of the PROCESS.STATUS through 'User Menu --> Business Tools --> Process Workflow --> Process Status View

You then need to specify the process that you want to follow

Click 'Process These two ENQUIRY records come as part of the T24 PW module. As they are core enquiries, care must be taken to not delete or change vital fields as these changes may be overwritten in an upgrade.

When the ENQUIRY is run, process.status displays all activities and their statuses that can be or have been executed. Drilldown on the enquiry will allow the chosen activity to be executed automatically. 

Process Workflow User Guide- Release R13.00 -Page 6 of 85 - (c) Temenos Systems 2013 18/07/2013

Enquiry Process Workflow Status.

Enquiry PROCESS ACTIVITY TXN. The standard ENQUIRY record TO.DO allows activities to be listed per user, which allows a specific user to concentrate on their allocated tasks. With two stage applications LD and LD.SCHEDULES it is advisable to complete the activity before launching applications via the explorer menu or command line.

PR OC ESS.D U R A TION .A N A LYTIC S

This enquiry will help us to monitor the actual time taken to complete the activity. While defining the Activity, the user has to define the days, the hours and minutes to capture the time. The user has to set the MONITOR.STAGE field to START. Only then the time will be monitored. Completion Date, Time and Time taken in the enquiry will capture the actual time taken to execute each activity.

PR OC ESS.WOR K LOA D .MON ITOR  The workload of each activity can be monitored using the enquiry PROCESS.WORKLOAD.MONITOR. We get a pictorially representation of the percentage of time taken to execute each activity.

Process Workflow User Guide- Release R13.00 -Page 7 of 85 - (c) Temenos Systems 2013 18/07/2013

It is also possible to view the status of the activity from the enquiry PROCESS.STATUS. In a process there can be any number of activities , PROCESS.STATUS can be used to monitor the current stage of the process.The status marker will be in red for the current activity and it will be in green for the activity which is already completed

Process Workflow User Guide- Release R13.00 -Page 8 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.STATUS At any time, any Activity and any Process must have a STATUS. The status of an activity may cause one or more activities to launch. The status of a process may indicate that process itself has completed The PW.STATUS application is itself quite straightforward, containing only the description and short description of the status.

PW.STATUS example Status codes are defined separately and attached to PW.ACTIVITY records. They are needed to define the default, starting status of an activity (DEF.STATUS.CODE on the PW.ACTIVITY record) e.g. PENDING. As an activity is worked on, that activity may go through a series of statuses. PW.STATUS is then also used to describe the status that the activity is in, at any one moment, in conjunction with the STATUS.RULE (the first status rule that the activity fits, is the status that the activity is tagged with).

Example: An ac t ivit y 'G et C us t o mer Det ails ' may s t art w it h a s t at us of 'Info rmat io n P ending'. T he ac t ivit y may als o have t he s t at us o f 'P art ial Info rmat io n Rec eived' - w hic h is t riggered w hen s o me but no t all info rmat io n has been ent ered. T he ac t ivit y may als o have t he s t at us o f 'C o mplet e' o nc e all info rmat io n has been rec eived. T he ac t ivit y may als o have t he s t at us o f 'Aut ho ris ed' o nc e t he c o mplet ed info rmat io n has been review ed by a s eparat e aut ho ris er. In t his c as e, t he s t at us es 'Info rmat io n P ending', 'P art ial Info rmat io n Rec eived', 'C o mplet e' and 'Aut ho ris ed' w o uld be needed fo r t he ac t ivit y 'G et C us t o mer Det ails '. For explanation of how to create this setup, see PW.ACTIVITY PW.STATUS may also be used in the PW.PROCESS.DEFINITION itself, as a way of working out what the status of the overall process is. For example, a process may have 10 steps to it. Once the process moves from step 7 to step 8, it may have moved into the 'Compliance' phase - in which case, a PW.STATUS of 'Compliance' may be required and used, to describe the status of the process. For more information on how this is done, see Determining the status of the PW.PROCESS and overall owner

Process Workflow User Guide- Release R13.00 -Page 9 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.TRANSITION

Example PW.TRANSITION record. PW.TRANSITION is the table used to define conditions/transition rules. Transition rules are attached to activities via the PW.ACTIVITY or the PW.PROCESS.DEFINITION table. These rules determine when the status of an activity changes. The status further determines if and when a subsequent activity is launched, to appear on the TO.DO list or to automatically be presented to the user.. The PW.TRANSITION is principally build from the multivalue set SELECTION.FIELD - CRITERIA. When each multi-value is added from fields SELECTION.FIELD – CRITERIA, this acts as an ‘AND’ between the criteria – so if we have two multi-values, both conditions need to be met for the PW.TRANSITION test to be passed. The Selection Operand determines whether the above fields AND the below routine, or the above fields OR the below routine, need to be satisfied in order for the PW.TRANSITION test to be passed.

Process Workflow User Guide- Release R13.00 -Page 10 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.VERB and PW.ACTIVITY.OBJECT Any activity can be considered as a verb and object : Create Customer, Create Account, Create Contract – or Create Account, Amend Account, Close Account. Imposing a verb/object structure  on the activity maintains a structure to Activities. Therefore, all PW.ACTIVITY records are made up of ., for example CREATE (verb) .CORP.CUSTOMER (activity object) Beyond description, the PW.ACTIVITY.OBJECT also contains a default target – this is defaulted into any activity which this PW.ACTIVITY.OBJECT is used in. However, this default is not mandatory and can be overwritten in any activity.

Example PW.VERB

Example PW.ACTIVITY.OBJECT As the activity must be made of VERB and ACTIVITY.OBJECT, both these records must be in place before the PW.ACTIVITY itself can be created.

Process Workflow User Guide- Release R13.00 -Page 11 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PARTICIPANT

PW.PARTICIPANT

This table is used to group Users or Account Officers together and is attached to either the PW.ACTIVITY or PW.PROCESS.DEFINITION record. When an Activity is launched, a User/Account Officer is then automatically allocated to it on the PW.ACTIVITY.TXN record, spreading the workload systematically between all users/ Account Officers within the PW.PARTICIPANT group. This helps Users/Account Officers in identifying their daily work by using an Enquiry to drill down and launch their specific tasks. Any defined activity must be owned by a particular PW.PARTICIPANT group. Any process must be owned by a PW.PARTICIPANT group. Enquiry TO.DO also provides a drill down and launch their specific tasks. When an activity is triggered, with FOLLOW.ON.ACT set to YES, if the user who causes the activity to be triggered is on the PW.PARTICIPANT group (either specified in the USER field, or is the ACCT.OFFICER) then that activity will be automatically presented to the user. For more information about this, see Auto Screen Creation. Note, only one activity can be automatically presented, so if two activities are launched, both with FOLLOW.ON.ACT = YES, both of which the USER is in the PW.PARTICIPANT group, only one will be presented to the user. The field ALLOW.EXT.USR is for ARC-IB, and indicates whether the individual who should be executing the activity could also be an external user, rather than a bank user. If it is set to Y then if an external user causes the activity to be launched, the customer number will be specified in the OWNER field.

Process Workflow User Guide- Release R13.00 -Page 12 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.ACTIVITY Each individual step in a process is described as a 'PW.ACTIVITY'. They are the separate actions, which the overall PW.PROCESS.DEFINITION links together to form the overall process These records determine the duration, possible statuses, transition rules (which determine which status should be used), owner, along with the TARGET . The TARGET field defines which T24 application will be launched when the activity is executed; it details how the application will be run i.e. how the application is usually executed from the command line. The target should be an application, version or function and depending on whether a new record is being generated or an existing record updated, 'F3' or 'NEW'. The application can either be a T24 application or an EB.TABLE.DEFINITION record.

This PW.ACTIVITY record will create new AA.ARRANGEMENT.ACTIVITY records when triggered. It starts in a status of Pending, and can move to statuses 'Completed' and 'Authorised' The DEF.DURATION field will calculate the end date of the activity, taking TODAY and adding the number of days specified here. Activity Type handles whether the system automatically processes this activity, without user intervention - for more information on automatic prockessing, click HERE. The STATUS.CODES - STATUS RULES multivalue set handle the decision on what status the PW.ACTIVITY.TXN will take : the target record will run through each PW.TRANSITION (set in the STATUS.RULES field). As soon as one of the PW.TRANSITION tests is found to be true, the corresponding STATUS.CODE from that multivalue set will be applied to that PW.ACTIVITY.TXN. If no STATUS.RULE applies to the target record, then the DEF.STATUS.CODE will be used instead. The COMPLETE.STATUS field indicates which statuses indicate that this activity has been completed. As soon as the activity reaches one of these statuses, the 'END.DATE' and 'END.TIME' fields will be populated, and that step in the process will be considered closed. Once an activity has been closed, it cannot be reopened. This will mean that even if there is a change to the record being handled by this activity, it will not update the status of this activity. For example, there could be an activity called HOLD.MEETING. This activity could have statuses of MEETING.PLANNED, MEETING.HELD and MEETING.CANCELLED. Both MEETING.HELD and MEETING.CANCELLED could be considered 'COMPLETE.STATUS' types - so as soon as the meeting has either been held or cancelled, this activity is done. No change to the record being handled by this activity will then change the status. The OWNER field indicates which PW.PARTICIPANT group is responsible for working on this activity. One user or account officer from this PW.PARTICIPANT group will be individually assigned to complete this task, and this group will also be put on the PW.ACTIVITY.TXN record - so any enquiry on PW.ACTIVITY.TXN can be filtered by user, account officer or participant group to find a 'to do' list of work. If the user responsible for launching this activity is also a member of this participant group, and the PW.PROCESS.DEFINITION has defined this activity to be FOLLOW.ON.ACT = YES, this will automatically cause this activity to be presented to the user. The field ALT.OWNER can be used to accept a hook routine only with a valid entry EB.API record - on keying in any other value not already predefined in EB.API, an error message,” RECORD NOT FOUND” will be shown. This field enables distribution of an activity to a user in PW

Process Workflow User Guide- Release R13.00 -Page 13 of 85 - (c) Temenos Systems 2013 18/07/2013

based on certain selection criteria (i.e., by competence level or region). Alternatively, a user could be assigned to handle continuous activities (i.e., the same user from the previous activity will be assigned to handle the next activity). 

Process Workflow User Guide- Release R13.00 -Page 14 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PROCESS.DEFINITION The PW.PROCESS.DEFINITION application ties together all constituent parts of the Process Workflow module, to create a single process. This table allows the linking of activities together in a logical business flow. It defines when an activity or spawned processes is enabled depending on pre-required Activities and their Statuses or Transition Rules. So PW.PROCESS.DEFINITION helps not only in defining the activities to be a part of the process, but the sequence and the stage at which they have to appear in the process. There are two Description fields, followed by a Duration field which gives an indication of how long, in days, the overall process is expected to take. This will then be defaulted into the DUE.DATE field on individual PW.PROCESSes as TODAY+DEF.DURATION Following Duration, the PW.PROCESS.DEFINITION application can be divided into two sections, the first handling which activities should be launched, when and how, and the second section dealing with the overall process - what status it is in, and who is the owner of the overall process. Click Here for PW.PROCESS.DEFINITION : Handling of Activities Click Here for PW.PROCESS.DEFINITION : Determining the status and overall owner

Handling of Activities PW.PROCESS.DEFINITION application handles which activities and sub processes are launched, and when.

Example PW.PROCESS.DEFINITION In

the

above

snapshot,

a

relatively

straightforward

flow

is

being

described.

Any ACTIVITY which does not have a 'PRE.REQ.ACT' field populated is automatically launched when the process starts (this is because this

Process Workflow User Guide- Release R13.00 -Page 15 of 85 - (c) Temenos Systems 2013 18/07/2013

activity is not reliant on any other activity in order to start - therefore, logically, it must start as soon as the process starts). This is the case with the first activity, CAPTURE.ONESTOP.CUSTOMER. The second activity, CAPTURE.ONESTOP.SCREEN (Activity.2), is launched when the first activity CAPTURE.ONESTOP.CUSTOMER (PRE.REQ.ACT.2.1) is in a status of completed (PRE.REQ.STAT.2.1). Both these activities will present themselves to the launching user the moment they are launched, providing the launching user is a member of the PW.PARTICIPANT group (defined on PW.ACTIVITY). This is because in both cases, FOLLOW.ON.ACT is set to YES There is also some mapping done at this point (EB.MAPPING.2), which is dealt with in Mapping in PW

Example Mapping Source This

example

is

relatively

straightforward

-

when

one

activity

reaches

a

particular

status,

launch

another

activity.

Later on in the process however, the launching of the activity is more complicated.  In this case, Activity 5 (CREATE.LCY.SAVINGS.ACCT) is dependent on an activity being in a particular status AND also passing a PW.TRANSITION rule. This is expressed through the configuration below:

Example PW.TRANSITION rule This functionality also can use 'OR' functionality - so could have been set to indicate 'launch activity B when activity A is in status X OR passes rule Y'. The functionality can also take into account multiple different activities, such as the below scenario: Where AUTHORISE.ONESTOP.CUSTOMER is only launched when two activities (CAPTURE.ONESTOP.CUSTOMER and CAPTURE.ONESTOP.SCREEN) reaches a status of COMPLETE. Of course, with different configuration this could also be launched when Activity X is in Status Y OR Activity A is in Status B. As a result, there is a great deal of flexibility in deciding when activities are launched. An important detail to understand is that activities affect other activities, rather than launch them - the system does not enable the configuring of 'Activity X causes activity Y to launch', but instead 'Activity Y launches when Activity X reaches a set status' a subtle but important difference.

Process Workflow User Guide- Release R13.00 -Page 16 of 85 - (c) Temenos Systems 2013 18/07/2013

Along with determining which activities are launched and how, this MV component of PW.PROCESS.DEFINITION also controls the following details about the activity being launched: l

If the same activity is launched more than once in a process (for example, an activity to charge the customer a fee), it is possible to distinguish between the activities for mapping purposes. This is done using the Unique Name field.

l

If the activity should be automatically presented to the user if the launching user is in the PW.PARTICIPANT group, this is indicated through the FOLLOW.ON.ACT field.

l

If the activity may be triggered through action other than the direct updating of one of the records within the process - for example, if an activity is triggered 3 days after a record is created if it hasn't been updated, or if an activity is triggered if a currency or share price goes below a certain amount : these are triggers that can only be evaluated by a service. In this case, TIME.TRIGGER functionality needs to be used.

l

How the mapping should be handled when this activity is launched - what data can be automatically mapped into the target record, and even what the ID of the target record should be - see Mapping in PW for more information

l

As an alternative to the above methods for launching a process,it is also possible to launch an activity based on the outcome from the Rules Engine  this is defined in PRE.REQ.EVAL

Tip: Along with handling which activities follow other activities, there is also functionality to launch a new process when the correct circumstances are met. In order to do this, the following convention must be followed :  In field ACTIVITY, instead of specifying an ACTIVITY the user must enter .DEF - this will result in the launching of a new PW.PROCESS when the circumstances are met. Whenever this page mentions launching an activity, it can also be assumed that the system can launch a new process as well. For more details, see How to set one Process to launch another

Determining the status of the PW.PROCESS and overall owner It is likely that there could be many different ways that a process to stop : if the customer calls and says they have decided to stop the loan application, if a KYC test has shown the trade would be inappropriate, if Compliance find an issue which indicates the process should finish. In these cases, it is possible/likely that multiple activities may be running in parallel, all of which should be stopped by changing the status of the process. This is why it is important to be able to control the overall status of the process, and also to indicate which statuses indicate the process is closed.

Field Name

Purpose

Process Complete

Indicates which PW.STATUS that the PW.PROCESS could be in would indicate that the PW.PROCESS has stopped (and therefore all current activities should also be stopped). Examples could be 'Customer Withdraws', 'Compliance Objections', 'Final Signatory Completed' Start of Multivalue set including Process Activities, Activity Status and Process Status. The actions of the fields can be described as 'the whole Process will be in status set in ALLOWED.STATUS if the activity described in ACTIVITY.STATUS reaches the status defined in PROCESS.STATUS'. For example, 'Process will be in  status 'COMPLETED' if activity 'Arrange Appointment' is in a status of 'Completed' OR Activity 'Contact Teller' is in a status 'Closed' would translate to: ALLOWED.STATUS : COMPLETED ACTIVITY.STATUS.1 : ARRANGE.APPOINTMENT PROCESS.STATUS.1 : COMPLETED ACTIVITY.STATUS.2 : CONTACT.TELLER PROCESS.STATUS.2 : CLOSED

There are multiple different statuses a Process could be in them. You can specify which of these statuses marks the process as closed.     If the above functionality does not give sufficient flexibility, the user can use the Rules Engine Gateway functionality to specify an EB.RULE.GATEWAY rule in PROC.STAT.EVAL which will otherwise determine the status of the process.

Process Workflow User Guide- Release R13.00 -Page 17 of 85 - (c) Temenos Systems 2013 18/07/2013

    The OWNER field holds the PW.PARTICIPANT for the activity in the process definition. The user can define the OWNER either at activity level or Process definition level.  The OWNER field defined in PW.PROCESS.DEFINITION takes precedence over the OWNER defined at activity level.

Process Workflow User Guide- Release R13.00 -Page 18 of 85 - (c) Temenos Systems 2013 18/07/2013

API Overview Routines Routines may be used to provide information to map into other records. The EB.MAPPING.SOURCE record setup differs from other mapping operations, here we have nominated ROUTINE as FLD.SRC.TYPE and the FLD.DATA.SRC is populated with the name of the routine prefixed by the @ symbol.

EB.MAPPING.SOURCE. The EB.FORMAT.ENTRY record attached to the above EB.MAPPING.SOURCE is constructed as normal, here it is mapping the routine’ @ID field in to the customer field of the account application.

EB.FORMAT.ENTRY. Below is an example routine that can be used in Data Mapping.

Process Workflow User Guide- Release R13.00 -Page 19 of 85 - (c) Temenos Systems 2013 18/07/2013

Data Mapping Routine.

Process Workflow User Guide- Release R13.00 -Page 20 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow Deal Processing Overview The underlying files managing a Process Workflow are PW.PROCESS and PW.ACTIVITY.TXN.

Whenever a process is launched, a PW.PROCESS is created. Each activity that is triggered within that PW.PROCESS causes a PW.ACTIVITY.TXN record to be created.

Reports D ur a tion A na ly tic s To enhance reporting, additional duration data has been added to the PW.ACTIVITY.TXN table. The time the PW.PROCESS was created, each time the PW.ACTIVITY.TXN under goes a status change and finally completes will be recorded so that the time each activity took, how long it spent in different statuses can easily be calculate. The below record displays a START.DATE and DUE.DATE for the PW.ACTIVITY.TXN, these are set in PW.PROCESS. The three sets of Times and Dates are displayed: The first set gives the start time it of the PW.PROCESS record. The second set gives the time and date the PW.ACTIVITY.TXN record was created. The Third and final set gives the time and date the PW.ACTIVITY.TXN goes to a completed status.

Process Workflow User Guide- Release R13.00 -Page 21 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.ACTIVITY.TXN

Process Workflow User Guide- Release R13.00 -Page 22 of 85 - (c) Temenos Systems 2013 18/07/2013

Used Records for ENROL.CUSTOMER process This topic simply lists all the records that have been used in this How To - so you can check the demo configuration, in case you are not getting the required results. If a record is not visible here, it should be supplied by default by ModelBank. PW.ACTIVITY.OBJECT records:

PW.VERB records

Process Workflow User Guide- Release R13.00 -Page 23 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PARTICIPANT records

PW.ACTIVITY records

Process Workflow User Guide- Release R13.00 -Page 24 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 25 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 26 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 27 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 28 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.TRANSITION records If not listed here, all PW.TRANSITION records are available in ModelBank

Process Workflow User Guide- Release R13.00 -Page 29 of 85 - (c) Temenos Systems 2013 18/07/2013

EB.FORMAT.ENTRY records

Process Workflow User Guide- Release R13.00 -Page 30 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 31 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 32 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 33 of 85 - (c) Temenos Systems 2013 18/07/2013

EB.MAPPING.SOURCE records

Process Workflow User Guide- Release R13.00 -Page 34 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 35 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PROCESS.DEFINITION records Note - in this case, we only show the underlying file, rather than the MB version, as this is split across multiple screens

Process Workflow User Guide- Release R13.00 -Page 36 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow User Guide- Release R13.00 -Page 37 of 85 - (c) Temenos Systems 2013 18/07/2013

PW Designer PW Designer is a GUI tool that helps us to design the process model in easy steps.  The process model is implemented using industry standard BPMN (Business Process Modeling Notation) symbols. This tool will work based on Eclipse IDE (Eclipse 3.6.1 and above) which is an open source IDE for application development. Advantages of using PW Designer 1. Symbolic representation of components provides a clear picture of process flow 2. Drag and drop feature provide easy way of designing a process. 3. Process is created locally so updating and re-using the same process is possible. 4. Using BPMN symbols which is a generic business model 5. Deployed in eclipse IDE which is an Open Source IDE 6. Configuring and using the PW Designer is simple.   Features available with the PW  Designer 1. Provides the users with the ability to model a process on a single (BPMN) pool. 2. Provides the ability to use the Task, Empty Start & End Event symbols and their associated (PW) properties only. These are meant for enriching the process model for execution in T24. 3. Provides the feature to map data across activities already defined in the process model using the Task symbols. 4. Provides the feature to retrieve data from T24 and store it in local cache for use in modelling of the process. 5. Provides the option to deploy & check-out a process model in and out of T24.  The detailed description about how to setup PW Designer environment in eclipse, how to create a process model using PW Designer etc is described in the following links l

Installation Instructions for PW Designer

l

Creating a PW Designer Project

l

Modeling a Process

l

Deploy a Process into T24

l

Check-Out a Process from T24

l

Troubleshooting instructions for PW Designer

Process Workflow User Guide- Release R13.00 -Page 38 of 85 - (c) Temenos Systems 2013 18/07/2013

Installation Instructions for PW Designer PW Designer tool can be configured with eclipse IDE (Eclipse 3.6.1 or above). Eclipse can be downloaded from the following url http://www.eclipse.org/downloads Once the eclipse is installed, the BPMN Project feature and the PW Designer plugin needs to be installed manually. Following steps need to be followed  1.

Install BPMN Project feature by selecting Help -> Install New Software

2.

In the field "Work with" of the dialog box, type - http://download.eclipse.org/releases/helios

3. The dialog box will list all the available updates, expand SOA Development and select BPMN Project Feature and click on next and then finish buttons.

Next step is to install the PW Designer plugin. It should be available as an archive for installation. Install it as a plugin into the Eclipse IDE. For the changes to be effective, eclipse needs to be restarted. 1. Select File -> Restart which will restart the Eclipse IDE 2. During restart, a valid location of the workspace needs to be defined.

Process Workflow User Guide- Release R13.00 -Page 39 of 85 - (c) Temenos Systems 2013 18/07/2013

Next step is to configure the eclipse environment to work with PW Designer. 1. Select Window -> Open perspective -> other which opens a dialog box with the list of available environment, select PW Designer. 

1. To connect the PW Designer environment with T24, select Window -> Show View -> Other  2. Expand PW Designer and select PW Site Manager and click OK 3. In the PW Site Manager Window click the NEW button. 4. Provide the details of the T24 server

Process Workflow User Guide- Release R13.00 -Page 40 of 85 - (c) Temenos Systems 2013 18/07/2013

Note: Before configuring the PW Site Manager, an instance of jbase agent needs to be started in T24. The same port number in which the jbase agent runs needs to be used in the PW Site Manager. Once the connection is established, click on Refresh Static Data button on PW Site Manager to load static information into the static cache of PW Designer.  Once the data is successfully loaded a message box will display like follows else it displays an error message if there is a problem with the connection.

Process Workflow User Guide- Release R13.00 -Page 41 of 85 - (c) Temenos Systems 2013 18/07/2013

Creating a PW Designer Project To create a process using PW Designer , following steps needs to be followed 1. A project needs to be created (a project is a collection of files and properties in an organized manner). To create projects select File -> New -> PW Project which opens a new project dialog box as follows 

2. Enter a name and click finish to create a project.  3. Next step is to create a GUI design for the process, click on diagram folder inside the Navigator pane and select New -> Other which opens a dialog box as follows

Process Workflow User Guide- Release R13.00 -Page 42 of 85 - (c) Temenos Systems 2013 18/07/2013

4. Expand Other and select Bpmn Diagram and click on next which will prompt for the name for the diagram, enter a name and click finish 5. New workspace area is displayed for creating the process. By default the workspace is available with a single task displayed (a task in the PW Designer is equivalent to the activity in the T24.)

The process can be designed with the help of components available in the palette on the right side of the screen, the palette contains a list of BPMN symbols where PW process requires only few basic symbols which are all displayed in the following diagram.

Process Workflow User Guide- Release R13.00 -Page 43 of 85 - (c) Temenos Systems 2013 18/07/2013

The above diagram contains some commonly used PW Designer symbols for designing a process like Task which represents an activity (used to create an activity record in T24), EMPTY START (to indicate the start of a process), EMPTY END (for defining completing state of a process), FLOW CONNECTOR (used to connect artefacts within the model), Pool used to define the process owner, Lane used to define the activity owner, Switch construct and Parallel construct. Note: PW Designer allows only one project to be created per workspace, and it is recommended to create only one diagram per project to avoid deployment errors.

Process Workflow User Guide- Release R13.00 -Page 44 of 85 - (c) Temenos Systems 2013 18/07/2013

Modeling a Process Create a process diagram using various symbols from the BPMN palette. The process model should be designed on a single Pool canvas with all the symbols placed as shown below in the diagram.  Once the diagram is created , the next step is to add properties to each of the symbols laid down in the process model. Note on navigation : It is necessary to review each of the fields in the properties of the symbols in the process model during navigation around the PW Designer.

START and END events These components are used to configure the values related to the process. Right Click on the component and choose Show properties Window to define the properties. 

The PROCESS.DESCRIPTION field captures a short description about the process. PROCESS.DURATION is used to specify the maximum time duration being defined to complete the process.

Process Workflow User Guide- Release R13.00 -Page 45 of 85 - (c) Temenos Systems 2013 18/07/2013

PROCESS.OWNER field refers to various groups of business users who own the process. Process Owner is the property of the pool. Note: In the above mentioned properties, the Description and Owner fields need to have a value for successful deployment into T24.

The PROCESS COMPLETION STATUS field represents the status achieved by the process after all the activities are complete. This value needs to be defined in relation with the final activity defined in the process model.

Process Workflow User Guide- Release R13.00 -Page 46 of 85 - (c) Temenos Systems 2013 18/07/2013

Activity or Task

Once an activity is added in the process the title given for the task will become the Description of the activity. The user has a choice to enter the fields manually or default the values from an existing base activity. To default the values from an existing base activity select an activity name from the dropdown box against the Select Base Activity field, once activity is selected, a warning dialog box appears as follows

If yes button is clicked all the values including the description field will be defaulted with the selected activity values, if the no button is clicked except the description field all other field values will be defaulted.

Process Workflow User Guide- Release R13.00 -Page 47 of 85 - (c) Temenos Systems 2013 18/07/2013

Activity Description field contains a brief description about the activity, Activity Short Description hold a short description about the activity.  Task Duration (days, hours, minutes) all these three fields are used for reporting purposes which helps in monitoring the activity duration. Business Service field contains the specific application to be executed in T24 once this activity is triggered from the process. Activity Type field contains the mode for executing the activity like auto or manual. Monitor Stage should be set to START to record the duration metrics around the Activity. Select Base Activity is used to default values to the fields from the activities defined in T24. If upon selecting a base activity, there are no values being defaulted into the fields, then the connection with T24 needs to be reviewed. An activity reaches a specific status (mentioned in Status Code) upon satisfying the associated rule defined in Status rule. Hence an activity needs to have the Status Code & Complete Status set to the same value. Default Status Code is the initial status of the activity before it is picked from the queue for execution.

Owner is used to assign a specific user group who are eligible to execute the activity. Represented as Lane in the designer Note: In the above mentioned properties Activity Description, Activity Short Description, Business Service, Activity Type, Status Codes, Status rules, Complete status, Owner, Default Status Code need to have value for successful deployment.

Mapping values between Activities Configuring data mapping between two activities is also possible using PW Designer, this can be achieved with the help of another window named Assignment View. To open Assignment View window select Window -> Show View -> Other and expand PW Assignment View and select Assignment View and click on OK.

Process Workflow User Guide- Release R13.00 -Page 48 of 85 - (c) Temenos Systems 2013 18/07/2013

The above step will add a tabbed window on the bottom of the screen which contains the option for configuring data mapping between different activities and its fields.

The above diagram represents a sample data mapping details between 2 activities CREATE CUSTOMER and CREATE ACCOUNT. To map the data between two activities the source activity and target activity needs to be selected, then source table and target table name need to be entered manually.  Note: After manually putting in the table name in Source Table and Target Table fields, it is mandatory to hit <Enter> key to populate the Source and Target field with values. Once the source and target table is specified, the list of fields available will be populated in source and target field drop down list boxes, select the field name from the list and click on Map button to configure the data mapping. In case of modifying the existing mapping, select the mapping value from the table and click on edit and to remove the mapping click on delete button, once all the configuration is completed, save the project.

Process Workflow User Guide- Release R13.00 -Page 49 of 85 - (c) Temenos Systems 2013 18/07/2013

Deploy a Process into T24 Note:  Before deployment, it is necessary to ensure that each of the properties of the symbols are supplied with appropriate values. Improper values in the properties will result in problems during deployment. Hence it is advisable to navigate  and review through each of the properties of the symbols in the process model before deployment. The activities created using the designer needs to be deployed into T24. In PW Designer, deployment refers to the process of translating the process model into an executable process in T24. Also the transfer of the related process artefacts(bpmn diagram, etc.) from the designer to T24 happens during deployment.  Following steps needs to be followed to deploy the process 1. Select the diagram that needs to be deployed 2. Select Project -> Deploy menu to start the deployment.  3. Select the project where the activities were designed.

4.Provide a valid T24 user id and password along with the site name which is configured using the PW Site Manager and click on continue button.

If the process is deployed successfully, then a message will be displayed accordingly else the following error message will be displayed - “An error occurred during the deployment of T24”. For reviewing any problems occurring due to deployment, the Console window in eclipse can be visited.

Process Workflow User Guide- Release R13.00 -Page 50 of 85 - (c) Temenos Systems 2013 18/07/2013

If the deployment was successful then the relevant activities and T24.  PW.PROCESS.DEFINITION record in T24 will be created as shown below

process

definition

records

will

be

created

Process Workflow User Guide- Release R13.00 -Page 51 of 85 - (c) Temenos Systems 2013 18/07/2013

in

Check-Out a Process from T24 The PW Designer tool also provides an option to extract or check-out and amend the processes designed through the tool. 

Configuration 1. Open eclipse IDE with a new workspace (it is mandatory to use a blank workspace to check-out and edit a process model)

2.Switch to PW Designer perspective - Window -> Open Perspective -> Other and select PW Designer.

Process Workflow User Guide- Release R13.00 -Page 52 of 85 - (c) Temenos Systems 2013 18/07/2013

3.To establish connection to T24 server, Click the New button on PW Site Manager and enter the T24 server details.

Process Workflow User Guide- Release R13.00 -Page 53 of 85 - (c) Temenos Systems 2013 18/07/2013

4. Select Project -> Checkout.

Once the check out option is selected, a dialog box will be displayed with the list of projects available for PW Designer. 5. Select a project for amendment and click on OK, which opens the project with BPMN process model created in it.

Process Workflow User Guide- Release R13.00 -Page 54 of 85 - (c) Temenos Systems 2013 18/07/2013

6. Open the diagram and proceed with the amendment.

(Diagram before amendment)

(Diagram after amending a new activity)

Note: Before deployment, it is necessary to ensure that each of the properties of the symbols are supplied with appropriate values. Improper values in the properties will result in problems during deployment. Hence it is advisable to navigate  and review through each of the properties of the symbols in the process model before deployment. 

7. Deploy the project again using Project -> deploy and provide T24 Login id and password on the triggered dialog box and click on Continue.

Process Workflow User Guide- Release R13.00 -Page 55 of 85 - (c) Temenos Systems 2013 18/07/2013

8. On the successful deployment of the process, the existing PW.PROCESS.DEFINITION record will be updated.

Process Workflow User Guide- Release R13.00 -Page 56 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PROCESS.DEFINITION before Check Out

Process Workflow User Guide- Release R13.00 -Page 57 of 85 - (c) Temenos Systems 2013 18/07/2013

PW.PROCESS.DEFINITION after Check Out and amendments Note: While amending the diagram, the value in the Process description properties field of the START event should not be changed.

(c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 58 of 85 - (c) Temenos Systems 2013 18/07/2013

Troubleshooting instructions for PW Designer Pr oble m  1 : A c tiv ity not be ing lis te d in A s s ignm e nt Vie w BPMN diagram pool contains more Task symbols (i.e., activity) but in the Assignment View window Source activity and Target activity fields do not list all or some of them.

  Solution This indicates that the changes made to the diagram have not been saved.  Choose File -> Save All or click on Save All icon on the tool bar to fix the problem.

Pr oble m 2 : C ould not la unc h the A s s ignm e nt v ie w option While opening the Assignment View window, an error is thrown as shown - "Could not create the view: Could not connect to the default site in PW Site Manager".  Solution

Process Workflow User Guide- Release R13.00 -Page 59 of 85 - (c) Temenos Systems 2013 18/07/2013

You need to check whether a connection is available in PW Site Manager, if not establish a new connection.  If connection is already available, restart the Eclipse IDE instance to fix this problem.

Pr oble m 3 : A n e r r or oc c ur r e d while r e fr e s hing da ta fr om T2 4 While clicking on the Refresh Static Data button on PW Designer Site manager view, the following error occurred. 

Solution This message indicates that while trying to retrieve static data from T24, an error has occurred.  The cause for this error may be of connection failure due to in correct Login Id and password or jbase agent is not running on the specified port or unable to reach the server etc.  Review all the properties of remote site connection in the PW Site manager.

Pr oble m 4 : N o B a s e a c tiv ity is be ing lis te d in Ta s k s y m bol pr ope r tie s v ie w While trying to select a base activity from existing activities in T24, the list box is empty as follows

Process Workflow User Guide- Release R13.00 -Page 60 of 85 - (c) Temenos Systems 2013 18/07/2013

This situation occurred due to improper connection with T24, or no connection at all.  Check the connection properties in the PW Site Manager for this problem in case the connection is already available, if else establish a new connection.

Pr oble m 5 : Is s ue dur ing de ploy m e nt of a pr oc e s s to T2 4 Solution

In case of encountering the below mentioned error during deployment after selecting the 'Continue' button shown above, ensure to visit each of the PW properties tab associated with the Task, Start Event & End Event symbols. All the mandatory information (refer to the Modeling a Process section for details about the mandatory information for each symbols) needs to be entered to enable the process for successful deployment.

Process Workflow User Guide- Release R13.00 -Page 61 of 85 - (c) Temenos Systems 2013 18/07/2013

 In case of persistent issues with the deployment, contact the Temenos Customer Support team with information from the Console view (retrieved while deploying a process into T24).

Pr oble m 6 : Pr oble m oc c ur r e d dur ing the c r e a tion of B PMN D ia gr a m in the PW pr oje c t While trying to add a BPMN diagram to the PW project the following error occurred.

This is due to the incorrect selection of BPMN diagram option while using the wizard.  While using the wizard, select the BPMN Diagram listed under the Other category (as shown below). The one listed under PW Project should not be used (reserved for future use).

Process Workflow User Guide- Release R13.00 -Page 62 of 85 - (c) Temenos Systems 2013 18/07/2013

Pattern Based Workflow The PW module supports different pattern based workflow apart from sequential workflow. The PW process engine can loop back to a previous activity or repeat certain activities within a process. The looping can be triggered with or without condition.  It is also possible to add a different construct in the workflow to control the flow of the process, say which activity to be executed next or execute more than one activity in parallel. The loops and constructs needs to be configured in the application PW.PROCESS.DEFINITION.  For example while creating customer record, customer is suppose to give all the necessary documents.  At that point, if one of the documents was not submitted and later the customer comes and submits the document.  Then in that case patterns allow the process to re-execute the same transaction to amend the record and complete the process.  This is possible even after the next activity is completed.  Note: Different patterns can be defined in PW.PROCESS.DEFINITION, only if the field USE.WORKFLOW.PATTERNS in PW.PARAMETER is set to YES.  Following fields in PW.PROCESS.DEFINITION needs to defined to configure the supported looping patterns and construct. l

ACTIVITY OWNER specifies the user(s) who is/are privileged to execute this activity.  Having precedence over the value specified in OWNER field in PW.ACTIVITY application. 

l

PATTERN.CONSTR is used to define a specific workflow pattern construct.  There are three pattern construct options available as ROUTE.TO, PARALLEL.FLOW and SWITCH.  ROUTE.TO pattern construct implements looping pattern, PARALLEL.FLOW pattern construct implements parallel execution of activities and SWITCH pattern construct used to implement exclusive choice for activities like select and execute a particular activity. 

l

PRE.REQ.CONSTR field used to define a previous CONSTRUCT (any pattern construct) that has to be run in this process before the corresponding ACTIVITY will be allowed to execute. 

l

EVAL.CONDITION is used to specify condition for loop and switch patterns.  It can hold the values from the EB.API application, "@" symbol should be prefixed with the EB.API id .

l

RECU.EVAL.COND is used to implement the recursive pattern, holds the EB.API id. If the condition returns TRUE the specific activity instance executes recursively until the condition returns FALSE. 

l

UNIQUE.NAME is used for data mapping and to differentiate activity records if two or more identical ACTIVITY names are defined.  Mandatory if PATTERN.CONSTR is specified.

l

EVAL.CONDITION is used to specify condition for loop and switch patterns.  It can hold the values from the EB.API application, "@" symbol should be prefixed with the EB.API id.

l

ROUTE.TO.ACT field define the activity to which the process need to be routed for re- execute the activity.  If the activity the process routing is not defined more than once in the process then ROUTE.TO accept values from PW.ACTIVITY.  If the activity has been defined more than once in the process definition then field should accept values in the format PW.ACTIVITY_UNIQUE.NAME where UNIQUE.NAME corresponds to the specific instance of the activity. 

l

ROUTE.ACT.STATUS is used to define the status to be set for activity to which the process loops back.

l

FLOW.ACT is used to define multiple activities which will execute in parallel.

l

CASE.ACTIVITY is used to define the activities for SWITCH pattern construct in the process.  Any one of the activity defined in the field will execute based on value return by EVAL.CONDITION.

l

DEF.ACTIVITY field holds a PW.ACTIVITY id value.  If the PATTERN.CONSTR field is set as SWITCH, then the DEF.ACTIVITY should be defined. The DEF.ACTIVITY and CASE.ACTIVITY are mutually inclusive fields. 

The different types of patterns available PW module are: l

Arbitrary Looping

l

Structured Looping

l

Recursion

l

Parallel Split

l

Switch Construct

Process Workflow User Guide- Release R13.00 -Page 63 of 85 - (c) Temenos Systems 2013 18/07/2013

Arbitrary Looping Arbitrary Looping is a very standard functionality in any workflow management which provides the ability to direct the flow of activities in both forward and backward direction within a process definition. The process can be routed back to any of the completed activities. The Following Diagram shows how the Arbitrary Loop will execute the given activities.

Note:  If the workflow is routed backwards, some of the previous activities will be triggered once again  and the transition rules, if any, would be applied again. Since same transactions are revisited, the workflow path could vary depending upon the current value and some of the records may become redundant. The arbitrary looping will execute the activities in sequence as defined in the process definition until it reaches the ROUTE.TO construct. The process will now be redirected to the activity defined in the field ROUTE.TO.ACT.  After the execution of the activity, the process will now jump to the next activity where the loop had started.  For example, in the above diagram, Activity 1, Activity2 and Activity 3 will execute in sequence, the process is routed back to Activity 1. On completion, the process will not execute Activity 2 and Activity 3, it will directly jump to Activity 4 if any, otherwise the process will complete. The following screenshot shows a sample definition of the PW.PROCESS.DEFINITION for arbitrary looping. The field PATTERN.CONSTR needs to be defined as ROUTE.TO (indicating this construct will route the flow to an already executed activity)

Process Workflow User Guide- Release R13.00 -Page 64 of 85 - (c) Temenos Systems 2013 18/07/2013

In the above screen shot three activities(CREATE.CUSTOMER,CREATE.ACCOUNT and CREATE.SECTOR) and one looping activity (Activity with UNIQUE NAME as LOOP) has been defined.  The activity CREATE.CUSTOMER will be executed first when the process is initiated. On completion of the first activity, CREATE.ACCOUNT activity will trigger automatically because the FOLLOW.ON.ACT for CREATE.CUSTOMER is set to YES.  Once the CREATE.ACCOUNT activity is completed, the process will hit the ROUTE.TO construct and the activity defined in the ROUTE.TO.ACT will be triggered. The activity CREATE.CUSTOMER will be triggered again. The next activity to be executed would

Process Workflow User Guide- Release R13.00 -Page 65 of 85 - (c) Temenos Systems 2013 18/07/2013

be CREATE.SECTOR because the field PRE.REQ.CONSTR has the value ROUTE.TO_ LOOP (combination of pattern construct and unique name) The enquiry PROCESS.STATUS can be launched to view the status of each activity within a process. This enquiry will display the current status of each activity and provide option to execute any activity in the list. The following screen shot shows the output of PROCESS.STATUS enquiry which lists the activities that are completed and pending in a process.

It is also possible to define an arbitrary process with complex pattern incorporated in the designer using BPMN symbols as shown in below screenshot.

The activity to which the process needs to be routed to is defined in the field ROUTE.TO.ACT. The route to activity must belong to the same process. The default status to be assigned to the activity once routed to is defined in the field ROUTE.ACT.STATUS.

The activities created using the designer needs to be deployed into T24. The following screenshot shows a sample definition of the PW.PROCESS.DEFINITION for arbitrary looping. The field PATTERN.CONSTR needs to be defined as ROUTE.TO (indicating this construct will route the flow to an already executed activity)

The enquiry PROCESS.STATUS can be launched to view the status of each activity within a process. This enquiry will display the current status of each activity and provide option to execute any activity in the list. The following screen shot shows the output of PROCESS.STATUS enquiry which lists the activities that are completed and pending in a process.

Note:  You can follow the PW Designer topic for the steps to design and deploy the process.

(c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 66 of 85 - (c) Temenos Systems 2013 18/07/2013

Structured Looping Structured Looping (Repeat Variant) is similar to arbitrary looping but with a condition. A single activity or more than one activity can be repeated based on the condition given in the process.The activities will be executed repeatedly till the condition is  true. The condition will be attached in PW.PROCESS.DEFINITION in the form of routine to the field EVAL.CONDITION.  

 Above diagram illustrate flow of the Structured Looping. Activity1, Activity2 and Activity3 will be executed in sequence, the condition is evaluated and if the result is true, the process will be redirected to Activity1 followed by Activity2 and Activity3. The looping will stop if the condition becomes false. Validation for the Condition Routine: l

The routine must have an entry in PGM.FILE with TYPE as 'S' and it has to be prefixed with '@' while attaching to the field.

l

The routine has no incoming arguments but must have an outgoing argument to return TRUE or FALSE.

The screen shot of a sample Condition routine is given below.

Process Workflow User Guide- Release R13.00 -Page 67 of 85 - (c) Temenos Systems 2013 18/07/2013

The routine should be attached to the field EVAL.CONDITION in the multivalue set of the fields PATTERN.CONSTRUCT and ROUTE.TO in PW.PROCESS.DEFINITION.  The value of the field PRE.REQ.CONSTR should be defined as a combination of PATTERN.CONSRT and UNIQUE.NAME for the activity which needs to be executed if the condition fails. The following is the screen shot of PW.PROCESS.DEFINITION for Structured Looping.

Process Workflow User Guide- Release R13.00 -Page 68 of 85 - (c) Temenos Systems 2013 18/07/2013

 The below screen shot shows the output of Enquiry PROCESS.STATUS for the above defined process.

Process Workflow User Guide- Release R13.00 -Page 69 of 85 - (c) Temenos Systems 2013 18/07/2013

It is also possible to define a structured looping process with complex pattern incorporated in the designer using BPMN symbols as shown in below screenshot.

The activity to which the process need to be routed to is defined in the field ROUTE.TO.ACT. Note that the route to activity must belong to the same process. The default status to be assigned to the activity once routed to is defined in the field ROUTE.ACT.STATUS.

The routine name should be specified in EVAL.CONDITION field .

The activities created using the designer needs to be deployed into T24. The following screenshot shows a sample definition of the PW.PROCESS.DEFINITION for structured looping. The field EVAL.CONDITION holds a value “@STRUCTURE” to denote the routine name. The field PATTERN.CONSTR needs to be defined as ROUTE.TO (indicating this construct will route the flow to an already executed activity)

The enquiry PROCESS.STATUS can be launched to view the status of each activity within a process. This enquiry will display the current status of each activity and provide option to execute any activity in the list. The following screen shot shows the output of PROCESS.STATUS enquiry which lists the activities that are completed and pending in a process.

Process Workflow User Guide- Release R13.00 -Page 70 of 85 - (c) Temenos Systems 2013 18/07/2013

Note:  You can follow the PW Designer topic for the steps to design and deploy the process. (c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 71 of 85 - (c) Temenos Systems 2013 18/07/2013

Recursion The Recursive looping pattern allows an activity in a process to be executed recursively based on a condition. Each time the activity is repeated, the condition is evaluated and recursive loop continues till the result is TRUE.  Once the result becomes FALSE, the loop stops and next activity gets triggered.  The following diagram depicts the flow of Recursive Looping.

The condition for the recursive loop is defined in the field RECURSION.EVAL.CONDITION. This field accepts a valid routine name prefixed with '@' symbol and the routine has to be defined in PGM.FILE with TYPE as 'S'.  The screen shot of a sample condition routine is given below.

Process Workflow User Guide- Release R13.00 -Page 72 of 85 - (c) Temenos Systems 2013 18/07/2013

The above screenshot has a sample process definition for recursive looping. There are two activities CREATE.CUSTOMER and CREATE.ACCOUNT in the process definition.  The activity CREATE.ACCOUNT is executed repeatedly until the attached routine returns FALSE. The enquiry PROCESS.STATUS can be launched to view the status of the activities in a process. Once the recursion activity is triggered the status of each recursive activity will be RECURSION.PENDING until the recursion is complete and when the recursion is over the status will change to COMPLETED.  The below screenshots shows a sample output of a recursion process.

Process Workflow User Guide- Release R13.00 -Page 73 of 85 - (c) Temenos Systems 2013 18/07/2013

Recursion in progress for ACCOUNT.OPENING activity.

The recursion process is completed and the status for all the activities is COMPLETED.

It is also possible to define recursion process using Basic BPMN Shapes “Looping Task” incorporated in the designer.

The routine name should be specified in the field RECU.EVAL.COND .

The activities created using the designer needs to be deployed into T24. The following screenshot shows a sample definition of the PW.PROCESS.DEFINITION for recursion . The field RECU.EVAL.COND holds a value “@RECURSION” to denote the routine name.

The enquiry PROCESS.STATUS can be launched to view the status of the activities in a process. Once the recursion activity is triggered the status of each recursive activity will be RECURSION.PENDING until the recursion is complete and when the recursion is over the status will change to COMPLETED. 

Note:  You can follow the PW Designer topic for the steps to design and deploy the process.

Process Workflow User Guide- Release R13.00 -Page 74 of 85 - (c) Temenos Systems 2013 18/07/2013

(c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 75 of 85 - (c) Temenos Systems 2013 18/07/2013

Parallel Split The Parallel Split construct allows PW to execute two or more activities in parallel within a process boundary. The parallel activities can be defined using a single definition instead of creating separate definition for each activity in PW.PROCESS.DEFINITION. At the time of execution all the activities marked as parallel will be triggered simultaneously.  The below figure describe the behaviour of the process engine for Parallel Split pattern.

  According to the above diagram, once the process is initiated Activity 1 will be triggered followed by Activity2. Activity4,Activity5 and Activity6 will be run in parallel and only if all the three activities are complete the next activity will be initiated. Note: If the parallel split construct has N number of branches, and all the branches defined in the construct need to be completed for the subsequent activity to be initiated, which is known a Synchronization Pattern. 

The following screen shot shows the PW.PROCESS.DEFINITION record for parallel split. The activities defined in FLOW.ACT will execute in parallel.

Process Workflow User Guide- Release R13.00 -Page 76 of 85 - (c) Temenos Systems 2013 18/07/2013

The field PATTERN.CONSTR should be defined as PARALLEL.FLOW and the activities that needs to be run in parallel needs to be defined in the field FLOW.ACT.In the above example, the activity CREATE.CUSTOMER will be triggered first when the process is initiated. The activities CREATE.ACCOUNT and CREATE.FUNDS.TRANSFER will be executed simultaneously. The activity CREATE.ARRANGEMENT will be triggered after the completion of both the parallel activities.  

Process Workflow User Guide- Release R13.00 -Page 77 of 85 - (c) Temenos Systems 2013 18/07/2013

The parallel activities can be executed in any order, once all the activities are completed, the process will trigger the next activity automatically.  The above screen shot shows the output of enquiry PROCESS.STATUS which displays the status of each activity in a process with its activity id and owner.

It is also possible to define a process with parallel split incorporated in the designer. You can also define multiple lanes thus defining different activity owners.

The activities created using the designer needs to be deployed into T24.

The following screen shot shows the PW.PROCESS.DEFINITION record for parallel split. The activities defined in FLOW.ACT will execute in parallel.

The field PATTERN.CONSTRUCT should hold a value “PARALLEL.FLOW” to denote the process as parallel split construct. The activities that needs to be triggered parallel are specified in the field FLOW.ACT. All the activities defined in this multi-value field will be ready for execution once the pre requisite activity specified reaches a completed status. The user than has an option to chose among the activities that needs to be executed in a particular order.

The parallel activities can be executed in any order, once all the activities are completed, the process will trigger the next activity automatically.  The above screen shot shows the output of enquiry PROCESS.STATUS which displays the status of each activity in a process with its activity id and owner. Note:  You can follow the PW Designer topic for the steps to design and deploy the process.

(c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 78 of 85 - (c) Temenos Systems 2013 18/07/2013

Switch construct Switch Construct provides an exclusive choice pattern feature to the PW Process.  The process will be able to route to a specific branch where multiple branches are attached with a single activity based on a condition.  Similar to a case construct in programming languages. In addition with this Simple Merge provides a convergence of two or more branches into a single subsequent branch such that the thread of control is passed to the subsequent branch. The following diagram illustrates the behaviour of process engine for switch construct with simple merge.

In the above diagram, after the execution of Activity1, the given condition is evaluated and depending on the result either Activity2 or Activity3 or Activity4 would be executed. On the completion of any one of the activities Activity5 will trigger automatically. The below screen shot shows the PW.PROCESS.DEFINITION record for Switch Construct.

Process Workflow User Guide- Release R13.00 -Page 79 of 85 - (c) Temenos Systems 2013 18/07/2013

 The field PATTERN.CONSTR should be set to SWITCH and the routine to check the condition should be defined in the field EVAL.CONDITION. Each of the branch activity should be defined in the field CASE.ACTIVITY. If the routine attached at the field EVAL.CONDITION routine returns NULL then the activity defined in DEF.ACTIVITY field will be executed. Note CASE.ACTIVITY is a multi value field used to specify multiple activities, where DEF.ACTIVITY is a single value field.  Based on the value returned by the routine in EVAL.CONDITION, the activity whose multivalue position matches with the result will be executed. In case, the routine returns NULL or there is no activity that matches the result, then the activity at DEF.ACTIVITY field will be triggered.  The following screen shot illustrate a sample routine for switch construct

Process Workflow User Guide- Release R13.00 -Page 80 of 85 - (c) Temenos Systems 2013 18/07/2013

The above routine returns two parameter where the first parameter has either TRUE or FALSE, and the second parameter has a numerical value or NULL.  Based on the value in the field PATTERN.CONSTRUCT either first or second parameter is used, for Switch Construct the second parameter value is used to select the activity from the list.

The above screen shot illustrate the output of enquiry PROCESS.STATUS.    (c)

Temenos Systems 2013

Process Workflow User Guide- Release R13.00 -Page 81 of 85 - (c) Temenos Systems 2013 18/07/2013

Process Workflow Glossary

Process Workflow User Guide- Release R13.00 -Page 82 of 85 - (c) Temenos Systems 2013 18/07/2013

ACTIVITY : A single step within a process. An activity represents an item of work, which is allocated to a person and/or a team. It may be triggered by any other step within the process (or may be the first step in the process). In turn it can trigger one or more further steps in the process. An activity is always linked to a single record within T24 (note, the same record may be used in different activities – for example, when a customer record is returned to later in a process to add extra data). An activity is always in a particular status (any number of statuses can be defined in T24). Depending on this status, it may be considered ‘open’ (activity may be revisited, status may change) or closed (activity is complete, no further change may occur). Depending on the status of this activity, further activities, or even new processes, may be launched – or the overall process could be closed. The status of an activity is determined by a RULE. An activity may be ‘auto’ or ‘manual’. An auto activity can be completed automatically by the system – for example, create a new record where all the data in this record can be mapped from elsewhere in the process – or manual, where a user has to make decisions and populate the record accordingly.

Process Workflow User Guide- Release R13.00 -Page 83 of 85 - (c) Temenos Systems 2013 18/07/2013

Process : The overall task, which comprises of multiple steps (Activities). Any procedure within a bank which requires more than one step may be considered a process – for example, enrolling a customer may be a process, as there may be an authentication step, an information gathering stage, steps for issuing cards and documentation, an opportunity to offer supplemental products etc. Even a task as simple as input and authorization may be considered as a process. A process may involve only one person, or multiple people from different departments (or the same department). It may involve several distinct records, or the same record which is updated multiple times at different stages. Depending on the flow, not every step in the process may be required to be acted upon. The Process Workflow module handles this process : it identifies which activities need to be acted upon, by whom, and in which order. It handles the ‘to do’ lists for individuals and groups, and also manages the mapping of data between applications  so that data never needs to be rekeyed.

Process Workflow User Guide- Release R13.00 -Page 84 of 85 - (c) Temenos Systems 2013 18/07/2013

Launching User: A process may be launched from a number of points within (or even from outside) T24. The ‘Launching User’ is the individual who causes the process to start. The launching user may also be the user who performs the first activity – they do not however have to be this user.

Process Workflow User Guide- Release R13.00 -Page 85 of 85 - (c) Temenos Systems 2013 18/07/2013