TLM Recs 2.7 SP1

TLM Reconciliations Version 2.
7 SP1
Release Note
TLM Reconciliations 2.7 SP1 Release Notes
DISCLAIMER
SmartStream Technologies makes no representations or warranties regarding the contents of this document. We
reserve the right to revise this document or make changes in the specifications of the product described within it
at any time without notice and without obligation to notify any person of such revision or change
COPYRIGHT NOTICE
2000 -2009 Copyright of SmartStream Technologies. All rights reserved. No part of this publication may be
reproduced, stored in a retrievable system or transmitted, in any form or by any means, electronically,
mechanically, photocopying, recording, or otherwise, without prior written permission from SmartStream
Technologies.
INTELLECTUAL PROPERTY WARNING
The contents of this document and the software it describes are the intellectual property of SmartStream
Technologies. The ideas contained in this document must not be disclosed to any third party.
TRADEMARK NOTICE
TLM is a registered trademark of SmartStream Technologies. All rights reserved.

Other trademarks recognised and property of their respective owner.
DOCUMENT INFORMATION
Edition: 18 November 2009
Contents
1
Introduction .................................................................... 5
New Features and Enhancements ................................ 5

2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
2.15
2.16
2.17
2.18
New SmartStudio application ............................................................................... 5

2.1.1 WebConnect Studio ................................................................................. 5
2.1.2 Design Studio functions not migrated to WebConnect Studio ................. 6
2.1.3 Matching Studio ....................................................................................... 7
New single WebConnect menu structure ............................................................. 7
2.2.1 Dashboard availability controlled by roles ............................................... 8
User Maintenance in WebConnect ....................................................................... 8
Role Maintenance in WebConnect ..................................................................... 10
New Configuration Transfer utility .................................................................... 12
2.5.1 Deprecated features ................................................................................ 12
New Dynamic Compare custom control............................................................. 13
2.6.1 SmartSchema Properties used ................................................................ 14
Configurable Custom Date Formats ................................................................... 14
New Expandable Attribute Custom Control ....................................................... 14
Viewing a list of currently open dashboards ...................................................... 15
Grid enhancements ............................................................................................. 16
2.10.1 Enhanced filtering ................................................................................ 16
2.10.2 Switching to edit mode......................................................................... 16
2.10.3 Summary row ....................................................................................... 16
2.10.4 Fast-cut ................................................................................................. 16
2.10.5 Grid Column enhancements ................................................................. 17
2.10.6 New shortcut keys for fast-cutting grid data ........................................ 17
Business Logic enhancements ............................................................................ 18
2.11.1 Bulk editing for non-item universes ..................................................... 18
2.11.2 Business Logic Progress Updates......................................................... 18
2.11.3 Attaching documents to non-case universes......................................... 18
2.11.4 New Convert Case tool ........................................................................ 18
2.11.5 New Message Routing Tools ............................................................... 19
Enhanced search capabilities .............................................................................. 20
2.12.1 Searching across multiple item fields ................................................... 20
2.12.2 Specifying tolerances ........................................................................... 20
2.12.3 Child search prompt enhancement ....................................................... 21
2.12.4 Filter for sign functions ........................................................................ 21
Additional authorisation for outgoing case documents ...................................... 21
Server enhancements .......................................................................................... 22
2.14.1 Cash net items released to history ........................................................ 22
2.14.2 Start time of the current job used in scope rules .................................. 22
2.14.3 Parallel processing of duplicate jobs prevented ................................... 22
2.14.4 Specifying a currency for a column tolerance ...................................... 23
2.14.5 Move the Last-Prop BANK update to the start of the workflow job
processing ........................................................................................................... 23
Global Stock Aliases .......................................................................................... 24
2.15.1 New SYST setting ALLOW_GLOBAL_ALIAS ................................. 24
New SYST setting EDIT_NET_VALUE_DATE .............................................. 24
New SYST setting TRIAL_BAL_SET_LIMIT ................................................. 24
New value for ITEM_EDIT_REQS_NOTE SYST setting ................................ 24
Deliverables .................................................................. 25
3.1
3.2
TLM Platform Deliverables................................................................................ 25

TLM Recon Deliverables ................................................................................... 25
3.3
New Documentation ........................................................................................... 25
Level of Testing ............................................................ 25
Installation .................................................................... 25
Open Source Code used .............................................. 26
Issues Resolved in This Release ................................ 27

7.1
7.2
7.3
7.4
7.5
WebConnect ....................................................................................................... 27
Design Studio ..................................................................................................... 62
SmartData Services ............................................................................................ 63
Recon Services ................................................................................................... 64
SmartStudio ........................................................................................................ 90
Known Issues ............................................................... 91

8.1
8.2
8.3
8.4
WebConnect ....................................................................................................... 91
Design Studio ..................................................................................................... 93
SmartData Services ............................................................................................ 94
Recon Services ................................................................................................... 95
1 Introduction
This Software Release Note covers all system modifications for 2.7 SP1 of the TLM Reconciliations product.
The release note lists all issues that have been fixed for this release and is aimed at Technical Administrators. It
does not aim to go into technical depth about specific changes or to be the basis for system testing.
Note: Some of the components in this release are at a patched level, and are therefore supplied with a separate
Release Note. Please refer to those Release Notes for information of any additional new features or fixes that
have been implemented in those patches.
2 New Features and Enhancements

2.1
New SmartStudio application
This release introduces the new SmartStudio application. This application has been developed using the Eclipse
RCP framework, and is a container application that all SmartStream configuration and administration
applications will ultimately be migrated onto.
Each application that will be contained by SmartStudio will be available as a perspective. The perspective that
you are using determines the layout of your desktop. You can create new perspectives by changing the layout
and availability of the panes, and saving them as a new perspective. You can have only one perspective open on
the SmartStudio desktop at one time.
SmartStudio has its own online Help application, which can be opened as a pane within the SmartStudio desktop
by pressing <F1>, or can be launched in a separate window by selecting Help > Help Contents from the menu.
2.1.1
WebConnect Studio
The first application that has been migrated into the SmartStudio application in this release is WebConnect
Studio. WebConnect Studio contains most of the functions that were previously available in the Design Studio,
namely the configuration of the following:
1. dashboards and controls
2. constraints
3. searches
4. search, access, population, and constraint rules
5. options and constraints on existing workflow and TLM Control tools
6. the WebConnect menu structure (see New single WebConnect menu structure on page 7 for details)
Each configurable object is known as an artifact and is displayed within the Artifacts pane. You select the type
of artifact that you want to be displayed in the pane, and you can filter the list of these artifacts further by name
or by type. You double-click on the artifact that you want to work with to open it in the workspace. For
example:
(The menu structure is a single item and is excluded from list in the Artifacts pane. It is accessed using a
separate button.)
If a user is currently working with a particular artifact, that artifact is locked, and a message is displayed by the
artifact showing which user has locked it.
The information displayed on the desktop differs depending on the type of artifact that you are configuring. The
image above shows the Configuration page for a grid. There is also a Design page, where you can reposition and
resize the grid and the dashboard on which it is placed, as well as a Preview page, which allows you to see what
the grid dashboard will look like in WebConnect.
You can create new dashboards, controls, constraints, searches, and search, access, population, and constraint
rules, and when clicking the New button or selecting File > New from the menu, a wizard is launched that takes
you through the initial stages of the artifact creation. The Configuration page for that artifact is then opened in
the workspace for you to complete the configuration.
See the new WebConnect Studio Guide for full details of how to use the WebConnect Studio to create and
configure the various artifacts.
2.1.2
Design Studio functions not migrated to WebConnect Studio
There is a small number of functions that have not been migrated from Design Studio to WebConnect Studio.
These are as follows:
1. User creation and maintenance a new custom control has been created that can be accessed from
WebConnect. See Dashboard availability controlled by roles on page 8 for details of this function. This
function also remains in the Design Studio client.
2. Role creation and maintenance this function remains in the Design Studio client.
3. System settings, including screen legends and system messages - these functions remain in the Design
Studio client, and are also available in the Recon Admin client.
4. Form views these are no longer supported. If you previously used form views, when you upgrade to
version 2.7, the default view will be used as the default layout, and all other form views will be disregarded.
2.1.3
Matching Studio
The Matching Studio, a new component of SmartStudio, is currently in Beta and is primarily focused at
Customers who have licensed non-item matching. If you have requirements for a matching service that allows
tables other than Item to be matched then please contact your local SmartStream Sales representative to obtain
details of this new set of capabilities.
As well as non-item matching, the roadmap for Matching Studio is for it to completely replace Recon Admin for
item based matching configuration. Customers who use Recon Admin are invited to preview Matching Studio
and provide feedback to SmartStream Product Management. Details of how to configure these artifacts are
provided in the Matching Studio Plugin appendix in the Business Processing Guide. Please undertake this
preview in non-production environments as this Studio is not yet Production ready.
2.2
New single WebConnect menu structure
The WebConnect menu is now a single menu structure for the whole deployment, which is created using a new
Menu Structure configuration function in WebConnect Studio. This new function also introduces the ability to
configure cascading menus, that is, you can create submenus at the top level, and then submenus within
submenus. Submenus at any level can contain one or more dashboards.
The following image shows an example of a Menu Structure at configuration time. The folder icons
represent submenus (Cash, Securities, Input, Scratch pads), the dashboard icons
represent dashboards that
you have configured, and the special command icons
represent the reserved dashboards and special
commands:
The following image shows an example of the above Menu Structure at runtime:
The full list of special commands is as follows:
Trial Balance
Currency Value Adjusted Balances
Overdraft Interest Analysis
Asset Position Proofing
Generic Manual Input
Help Contents
About
Password Change
Logout
If a dashboard has not been added to the menu structure it will not be available to any users, unless it is a child
of a parent dashboard that has been added to the menu.
See the new WebConnect Studio Guide for full details of how to configure the menu structure.
2.2.1
Dashboard availability controlled by roles
Because there is now a single menu structure for the whole deployment, access to each dashboard and special
command on the menu is controlled by assigning one or more roles to each dashboard and special command. If
a user has not been assigned to any of the roles specified for a dashboard or special command, that dashboard or
special command is not visible to that user. If a dashboard or special command that is present on the menu has
no roles assigned to it, it is not visible to any users.
2.3
User Maintenance in WebConnect
You can now access the user maintenance functions directly through WebConnect. This means that you no
longer have to launch Design Studio to configure and update new WebConnect users. The following user
maintenance functions are now available from the User Maintenance option on the WebConnect main menu:
Adding and deleting users (only WebConnect-only users)

Modifying user details
Changing users Access and Limits
Changing users Lead User Authority
Changing users passwords
Assigning licensed messages
Assigning users to roles
When you select the User Maintenance option, a filter field is displayed. For example:
You can enter some filter criteria, or leave the fields blank to return all users. On submission of the filter, all the
users that satisfy the filter are presented to the user in a grid view. For example:
To access the maintenance functions for a user, right-click on the user that you want to change, or to create a
new user right-click anywhere n the grid. The user maintenance functions are displayed on a context menu. For
example:
10
The windows that are displayed for each function are similar to the existing windows for these functions in
Design Studio and Recon Admin,.
You modify (or view) any existing user by selecting View. A window similar to the Insert window is displayed,
and you can modify all data except the User ID, Creation Date and User Type.
You can create new WebConnect-only users by selecting the Insert option, and completing the fields on the
Insert window.
You can delete only WebConnect-only users, and only if the user is not logged in and is not a lead user of other
users.
You can modify the password only for WebConnect-only users. You cannot modify your own password from
this window, as this is done from the separate Change password function on the WebConnect main menu.
You can change the lead user authority, import the lead users shortcuts, change the access and limits, and
assign or unassign licensed message for any user.
Note: The WebConnect User Maintenance function requires that TLM Control is installed on your system, and
is therefore not available by default. To enable this function you must import the dashboard package into your
database and import the TLM configuration file into TLM Control. See the User Administration Guide for
details of how to do this.
2.4
Role Maintenance in WebConnect
You can now access the role maintenance functions directly through WebConnect. This means that you no
longer have to launch Design Studio to configure and update roles for WebConnect users.
When the user and role maintenance functions are installed, the new role maintenance functions are then
available from the Role Maintenance option on the WebConnect main menu. You can use them to perform the
following tasks:
View the list of roles in the system and their details
Create and configure new roles
Delete roles
Modify roles including Update universe access, change associated tools
When you select the role maintenance dashboard, a filter is displayed. For example:
11
You can enter search criteria, or leave the rows blank to return all roles. On submission of the filter, all the rows
that satisfy the filter are displayed on a grid dashboard. For example:
To access the maintenance functions for a role, right-click on the role that you want to change, or to create a
new role right-click anywhere in the grid. The role maintenance functions are displayed on a context menu. For
example:
The windows that are displayed for each function are similar to the existing windows for these functions in
Design Studio. For example:
12
Note: The WebConnect Role Maintenance function requires that TLM Control is installed on your system, and
is therefore not available by default. To enable this function you must import the dashboard package into your
database and import the TLM configuration file into TLM Control. See the User Administration Guide for
details of how to do this.
2.5
New Configuration Transfer utility
Configuration Transfer (CT) is the next generation of the Configuration Import utility (CI). The CT GUI has
been developed using the Eclipse RCP framework, and is also supplied with a command line utility from which
you can export and import configuration data.
CT offers the same functions as CI, with the addition of the following new functions and enhancements:
Performance is much improved over CI, particularly in terms of speed and memory usage.
With CT you can create reusable templates that are used to define the artifacts that will be added to the
export file.
You can export all of the configuration data from a database.
From the GUI, you can create a backup of all of the configuration data that is associated with your
active menus or shortcut groups.
From the GUI, you can clear all of the configuration data from your database. (Note that Users and
Roles are not cleared.)
As with CI, Configuration Transfer is independent of the TLM version against which it is being run.
2.5.1
Deprecated features
There are a couple of features that were available in CI that are not available in CT, namely:
You cannot edit packages that you have exported. However, if you used a template file to create the
export package you can edit the template and run the export again to create a new package.
2.6
The Read-only import option is no longer available, which means that if you import the same artifact
into a database again, that artifact will be overwritten.
New Dynamic Compare custom control
A new custom control is supplied with this release that enables you to compare multiple data records, for
example for a manual match.
To enable the Dynamic Compare control you must create a dashboard containing the custom control with the
URL "/secure/dynamicCompare.do", and configure that dashboard as a child of a grid dashboard.
To launch the Dynamic Compare control you must select at least 2 rows in the parent grid and then select it
from the list of child dashboards. The Dynamic Compare control then displays a grid that compares the data
values in a record side by side. For example:
Notes on the displayed data:

1. The following icons are used to indicate the state of each comparison test:
2.
3.
4.
5.
- the values are the same.

- the values are not the same
- the values were not compared (because property 212 was present on the attribute).
The rows for which the comparison has failed are displayed in bold/italic.
Totals are shown in the rows that have attributes with property 65 set.
The business logic tools are borrowed from the parent grid.
Use the record selectors to invoke business logic tools. Any constraints on the business logic tools are
considered. The selected records are submitted for processing as a single group.
13
14
2.6.1
SmartSchema Properties used
The following properties are used by the Dynamic Compare control to populate the Compare and Totals
columns:
Property ID
Level
Description
Object
Determines whether the attributes for that object are added or subtracted while
calculating totals.
65
Attribute
If present, a net total is calculated for the attribute.
212
Attribute
If present, the attribute is not compared, however it is still displayed on the

control.
2.7 Configurable Custom Date Formats

You can now define system-wide custom formats for date values in WebConnect, using a new SYST setting
called DATE_FORMAT. You can configure different formats for different locales. If a custom format is defined
for a users locale, that custom format is used for that users session. If there is no custom format defined for a
users locale, WebConnect defaults to use the standard Java "SHORT" format, as before.
To enable the custom formats, the syst_value of DATE_FORMAT must be set to 1, and the date format must be
defined in the SYST_STRING as follows:
<locale>=<format using d, M and y characters>
For example:
en_GB=dd-MMM-yyyy
Multiple date formats can be specified and separated with a comma. For example:
en_GB=dd-MMM-yyyy,en_US=MMM-dd-yy
Only the date part of the format is configurable; there is no support for configuration of the time of day format.
2.8 New Expandable Attribute Custom Control

To complement the existing mechanism for viewing the message of an expandable attribute, a new custom
control has been introduced. This enables a user to view the message in a standard dashboard. To configure the
custom control, create a dashboard containing the expandable attribute custom control with the URL
/secure/showexpandableattribute.do, and configure that dashboard as a child of a grid dashboard. The grid
should contain at least one expandable attribute within its view. If there is no expandable attribute or there is no
message and the custom control dashboard is launched, it will be blank. If there is more than one expandable
attribute in the view only the first will be displayed.
The following image shows the Expandable Attribute custom control dashboard:
15
The Inbound Message Display expandable attribute column in the parent grid could be hidden in the view, and
it would still populate the Expandable Attribute dashboard.
The existing mechanism for viewing expandable attributes, by clicking on the icon, is still available:
2.9
Viewing a list of currently open dashboards
You can now press F12 to display a list of any dashboards that are currently open in WebConnect. For example:
A tick is displayed next to the currently displayed dashboard, and you can click on another dashboard in the list
to bring that dashboard to the front.
The list includes any dashboards that are open in a different worksheet, in which case the list is separated by a
horizontal line, as shown above.
16
2.10 Grid enhancements

The following sections describe enhancements that have been made to grid controls.
2.10.1 Enhanced filtering

For columns that contain less than 20 distinct values, the filter field now lists the values that you can filter by,
for example:
(This drop-down filter was previously only available when filtering by image decode).
For column that contain more than 20 distinct values, a standard edit box is displayed instead of a drop-down
filter.
2.10.2 Switching to edit mode

You can now single-click on any editable cell to switch it into edit mode (upon which the cell is highlighted in a
different colour) and enter the required data into the cell, overwriting the original cell contents without having to
press <F2> (as was required in previous versions).
If you want to edit the original value without overwriting it, you can still do so by single-clicking on the active
cell to highlight the original contents, and then using the mouse to position the cursor where you want to edit the
text, or to select and drag a portion of the text within the cell.
You can also use a number of keyboard shortcuts to navigate the grid whilst editing, including <Tab>, <Enter>
and the arrow keys, which are described in the WebConnect Operations Guide.
2.10.3 Summary row

The summary row now provides a more complete description of the total rows presented in a grid, including the
original data row count, the number of rows filtered out and the number of aggregate rows added as appropriate.
2.10.4 Fast-cut
You can now select more than one row, and then use the new Fast-cut Selection and Fast-cut selection to New
Group options on the context menu to fast-cut all the selected items. The fast-cut target is configured in the
same way.
Fast-cut options for single rows have also now been added to the context menu.
17
2.10.5 Grid Column enhancements

A number of new settings have been introduced to SmartStudio to enhance the way in which grids are displayed
in WebConnect.
2.10.5.1 Configurable tooltips for column headers

Previously, tooltips displayed for column headers in WebConnect were always derived from the column
headings. A new Tool-Tip setting is now available in the Grid View Properties pane in SmartStudio, which
enables you to specify an alternative tooltip for each column in the view.
Additionally, you can now leave column headings blank, which is useful when you want to reduce the width of
the columns in a grid view. If you choose to do this, you can still display the column heading to the user by
configuring the columns tooltip. For example:
If you do not configure a columns tooltip in SmartStudio, the default column heading is used.
2.10.5.2 Flexible column widths

The following new column width settings have been added to SmartStudio, to allow greater control over the
way columns are sized, and to enable the configuration of both fixed-width and auto-fit columns in the same
grid view:
Use System Default enables you to specify the required width of the column. If the
COLUMN_WIDTH_POLICY SYST switch is off, the column width takes the value specified for each
column. However, if this SYST switch is on, the width specified is ignored and is instead set to the
widest data value in the column (ignoring headings).
Fit-to-data (ignore headings) the width of each column is set to the widest data value in the column
(ignoring headings). You can also specify minimum and maximum values for the width.
Fit-to-data (include headings) the width of each column is set to the widest data value in the column
(including headings). You can also specify minimum and maximum values for the width.
Fixed width enables you to specify a width for the column.
2.10.6 New shortcut keys for fast-cutting grid data

New keyboard shortcuts have been provided to fast-cut single items within and between dashboards.
After selecting the required item, the <+> shortcut can be used to fast-cut to a group marked by the insertion
point, and the <*> shortcut can be used to fast-cut to a new group.
18
2.11 Business Logic enhancements

The following sections describe the improvements that have been made to business logic functions in this
release.
2.11.1 Bulk editing for non-item universes

Bulk editing on grid data is no longer restricted to the item universe, and can now be performed on data in any
universe.
2.11.2 Business Logic Progress Updates

The browser polling interval during business logic processing can now be configured by a new SYST parameter
BL_UPDATE_DELAY. The value is a string comprising a semi-colon separated list of integers. Each integer
represents an interval in milliseconds. The first time the browser polls it will wait for the first specified interval,
then the second time it will wait for the second interval and so on. Once the end of the list is reached the last
interval will be used for subsequent polling intervals.
This setting enables the system administrator to reduce the potentially large number of HTTP request/response
cycles for long running business logic and consequent load on the network and HTTP server.
The default value is set to '1000;1000;1000;3000;3000;3000;5000' so that very short processes will still
complete in a few seconds. This string represents seven intervals of duration: 1, 1, 1, 3, 3, 3 and 5 seconds. Any
subsequent polling will therefore be at intervals of 5 seconds.
2.11.3 Attaching documents to non-case universes

You can now add a document attach function to a TLM Control User Interaction step, which enables users to
attach documents to any universe.
2.11.4 New Convert Case tool

A new business logic tool, Convert Case, has been added to enable you to manually change an existing case to a
different case type. For example:
19
Items belonging to the case being converted must be at or below the level of the new case type.
2.11.5 New Message Routing Tools

The following new business logic tools are now supplied:
WebConnect Message Routing Delete
WebConnect Message Routing Insert
WebConnect Message Routing Edit
This means that you can now create a Message routing dashboards. The following procedure outlines the steps
required to create a message routing dashboard:
1. Using SmartSchema, ensure that the Message Routing universe is present and that the Message routing
attributes each have the property Dashboards Editable selected.
2. Using Design Studio, or WebConnect Role Maintenance, create a role for users responsible for creating or
modifying Message Routing records. Ensure that the tools listed above are allocated to this rule, and that all
of the attributes in the message routing universe are allocated as editable attributes. Then allocate this role
to the relevant users.
3. Using SmartStudio, create a search rule at the Message Routing level, containing the following logic:
Message
Message
Message
Message
Message
4.
5.
Routing
Routing
Routing
Routing
Routing
Message Feed equal to Prompt for Specific Value

and From Message Feed Type equal to Prompt for Single Decode
To Message Feed Type equal to Prompt for Single Decode
Action equal to Prompt for Single Decode
Description equal to Prompt for Specific Value
Then create a search that uses this rule.

Create a Message Routing Dashboard. This should contain a grid which is configured with the following
information:
Universe: Message Routing
Datasource: the search that you created in step 4.
A view that contains the appropriate attributes and objects.
Business logic tools: add WebConnect Message Routing Delete.
In the Save Options, for the Edit tool select WebConnect Message Routing Edit, and for the Insert tool
select WebConnect Message Routing Insert.
6. Add the dashboard to the Menu.
The dashboard that you have created should look something like the following:
20
To modify a Message Routing record in WebConnect using this grid, double-click on a cell in the grid, modify
the cell contents and click on Save button. To insert a new Message Routing record, right-click anywhere on the
grid and select WebConnect Message Routing Insert.
For details of how to create dashboards, grids and searches, see the TLM WebConnect Studio User Guide.
2.12 Enhanced search capabilities

SmartStudio now contains the following new features to enable you to configure more flexible searches.
2.12.1 Searching across multiple item fields

You can now configure search rules to search for a single input value across multiple item fields, by using the
new Use Previous Prompts Value attribute in the right-hand side of your expressions.
For example, if you want to search for an input value entered into an Item Reference field, within Item
Reference fields 1, 2 and 3, you can do so as follows:
2.12.2 Specifying tolerances

You can now specify upper and lower tolerances on float, date, datetime and integer values, that are entered in a
search field. To enable tolerances on searches, a new similar to operator has been introduced.
For example, in the expression configuration below, a lower tolerance of 5 days and an upper tolerance of 1 day
is defined for the expression, to ensure that the amounts returned from the search are no more than 5 days earlier
and 1 day later than the date input:
The upper and lower tolerances can be expressed as explicit or percentage values, unless they are for date or
datetime attributes, in which case explicit values must be used.
In WebConnect, a tooltip is displayed when the user hovers the mouse over an input field for which a tolerance
has been configured, to show the tolerance values that have been specified for the field. For example:
21
2.12.3 Child search prompt enhancement

In SmartStudio, a new child dashboard setting, Dont Suppress if no data, is now available when the Suppress
Child Prompts option is selected. When enabled, this setting overrides the Suppress Child Prompts option in
situations where the drill-down will not return any data. In this case, the search prompt would be displayed so
that the user can change the values, before running the search again. Depending on the search criteria, the
resulting dashboard might now be populated or it might be empty.
2.12.4 Filter for sign functions

Two new functions, Filter for sign and Filter for opposite sign, can now be applied to amount values in the righthand side of search rules in SmartStudio. These functions enable child dashboard searches, for example,
triggered from net totals on aggregate rows, to use the sign of the net value to locate the missing items. That is,
the items that can complete a match with a resulting net of zero.
For example, you would apply Filter for opposite sign in a situation where a group of items with a net amount of
-100 requires a drill-down to a grid that displays all Outstanding items, where Item Amount = 100, and Item
Type is Our Cash Credit.
Alternatively, in a situation where a group of items with a net amount of 200 requires a drill-down to a grid that
displays all outstanding items where Item Amount =200 and Item Type is Our Cash Debit, you would apply
Filter for sign to your rule.
2.13 Additional authorisation for outgoing case documents

WebConnect previously provided an option to specify that outgoing case documents should be authorised before
sending, that is, after creation, that document would then have to be authorised by a second user. This release
introduces the option to configure a second level of document authorisation.
If verification is required for case documents, it is still configured in Recon Admin using the Auth Required
checkbox on the case document template.
When the document creator issues the document, WebConnect first checks the Auth Required flag on the
document template. If the document requires verification, WebConnect then checks the value of the new SYST
setting CASE_DOC_AUTH_LEVELS, which specifies the number of times the document must be authorised
before it is sent, as follows:
22
SYST value
Description
User creates document, no authorisation required.
User creates document. Must be authorised once by another qualified user. This is the default.
User creates document. Must be authorised by two different qualified users.
If the Auth Required flag is not set, or the Auth Required flag is set but the SYST value is 0, the document is
queued to be sent.
If the SYST value is greater than 0, the document is set to awaiting authorisation. The document then gets
queued for authorisation. Authorisation can be performed only by users with permissions to authorise case
documents, using case dashboards. Each document authorisation must be performed by a person who has neither
created nor already authorised the document. When 2 levels of authorisation are specified, if a document has
been authorised once but requires another authorisation, it is marked as partially authorised in the case history,
and remains on the queue for a second authorisation. When the document has been authorised the required
number of times, it is queued to be sent.
2.14 Server enhancements

2.14.1 Cash net items released to history
The Workflow engine has been enhanced to allow net items to progress through the productised Cash release
logic. Previously they were identified by their non-zero match_no, and placed on the chosen queue as an Active
queue entry. Now they are progressed through the release processing.
An additional initial check has been added to the match_no check to see whether there are any interest
parameters set up for the account (on the Financial Parameters tab). If the Credit Potentials option is Off, and the
No Debit potentials option is On, net items are released. If either of the settings requires an interest calculation,
the net items are not released.
When net items are released, a final net match record is created with a new match number, however, no new net
item is created. Each net item involved in the match goes to history, but retains its original match_no and
sec_match_no rather than linking directly to the new match record.
Any amount discrepancy remaining on the match is accumulated onto the charge amount that is held on BANK,
as for standard cash matches.
2.14.2 Start time of the current job used in scope rules

A new Job Start Time reserved attribute has been added to the TLM schema to allow a match job to pick up
data based on the time that the current job started. This attribute is only available to scope rules, and is
interpreted by the workflow engine as the time the current workflow queue job was started.
2.14.3 Parallel processing of duplicate jobs prevented

Previously, if the workflow server was already processing a job with a non-zero lock_flg, an identical job with a
lock_flg of 0, which means that any server engine can process it, could be placed on the workflow queue for
processing, which means that duplicate jobs could be processed in parallel.
This has now been modified so that the new job is not inserted with lock_flg of 0, but with a waiting lock_flg
of 500+N, where N is the workflow server instance that is processing the first job. This means that only the
specified server instance can process it, and it will only do so once it has finished its current job, therefore
preventing duplicate jobs being processed in parallel.
For example, say you submit a new job for an item with the following information:
Corr_acc_no = 100000088
Passlist_id = 10075
23
Event_date= 01/01/2009
Workflow_list_id = 0
Lock_flag= 0
The logic checks for any entries with the same corr_acc_no, passlist_id, event_date, workflow_list_id.
If there are no entries, the entry is inserted with lock_flag = 0

If there are entries, the logic reads the lock_flag values and does one of the following:
If there is an entry already with lock_flag = 0, nothing is inserted
If there is an entry with a waiting flag (lock_flag > 500), nothing is inserted
If there is only one entry and it has an in-progress lock_flag (for example, 102 for engine 2 processing),
a new waiting entry is inserted for the same engine instance (502).
2.14.4 Specifying a currency for a column tolerance

In Recon Admin Pass Details, when configuring a population, a currency can now be associated with a tolerance
in the Column properties. The currency is available only when an amount-type column is specified. For
example:
Where a currency is specified, the tolerance is converted from the specified currency into the currency of the
items being matched, using the current exchange rates. This means that, for example, a tolerance of 10 USD
when applied to items in a GBP account converts $10 into the equivalent value in GBP, and uses the outcome of
that conversion as the tolerance amount.
Where no currency is specified, the tolerance is not converted. This means that, for example, a tolerance of 10
when applied to items in a USD account groups items together that are within $10 of each other, and when
applied to GBP account groups items within 10.
A new database column has been added to the PASC table to store the currency for the pass column. The
Configuration Import utility (CI) has been updated to enable migration this information.
2.14.5 Move the Last-Prop BANK update to the start of the workflow job
processing
The workflow server records the start date and time of any match run to the Bank record associated with the
match job. Previously, the Bank record was updated with the start time at the end of job processing.
To allow other jobs to see the time that a currently running job started, to avoid processing data loaded before
that time, the bank table update is now performed when processing starts.
24
2.15 Global Stock Aliases

An enhancement has been made to the asset register logic to allow the use of global security aliases alongside
territory code-based aliases. Essentially, this enhancement allow aliases with blank territory-codes to be
considered global so that they can be seen by all Sets, regardless of whether they are linked to territories, while
continuing to allow territory-based alias lookup for Sets linked to specific territories.
If a territory code is assigned to the Set, the look-is now broken down into separate searches, each of which is
only carried out if nothing is found for the preceding stage. These stages are as follows:
1. Look for matching known alias (positive stock_id) with the same territory_code
2. Look for matching known alias (positive stock_id) with blank territory_code
3. Look for matching unknown alias (negative stock_id) with matching territory_code
2.15.1 New SYST setting ALLOW_GLOBAL_ALIAS

A new SYST setting, ALLOW_GLOBAL_ALIAS, has been introduced to control whether a global look-up is
used, or whether the lookup is restricted to the relevant territory code. The default value of this SYST setting is
0, which means that global lookup is not used.
2.16 New SYST setting EDIT_NET_VALUE_DATE

A new SYST setting, EDIT_NET_VALUE_DATE, has been introduced to enable users to specify whether the
value date on net items that are created by release workflow can be edited. The default value of this new setting
is 1, which means that the data value can be edited.
2.17 New SYST setting TRIAL_BAL_SET_LIMIT

A new SYST setting: TRIAL_BAL_SET_LIMIT has been introduced to specify the maximum number of sets
that can be included in a trial balance search. This is to prevent excessively large searches being run that would
affect the application server performance. The default value for this setting is 1000.
If a Trial Balance search will be calculating Trial Differences for more accounts that the maximum, even if
some sets are subsequently filtered out, the user is prompted to change the search criteria.
2.18 New value for ITEM_EDIT_REQS_NOTE SYST setting

A new value of -1 has been introduced for the ITEM_EDIT_REQS_NOTE SYST setting. This SYST setting is
used to control how the note field is used in conjunction with WebConnect productised item save tool. A value
of -1 represents that the note is suppressed, and should therefore be used in situations where you do not want the
note field to be displayed to the user.
25
3 Deliverables
3.1
TLM Platform Deliverables
File Name
Design Studio\setup.exe
TLM Design Studio.msi
SmartStudio 2.8#P10.exe
SmartStudio 2.8#P10.msi
Control\ tc_setup.zip
install_smartdata
smartdataservices2_7_1_35.tar
TLM SmartDataServer 2.7 SP1.exe
WebConnect.war
Utilities
Configuration Transfer
Customer Branding
Security Administrator
SmartSchema
3.2
Version
2.7.0.45
2.7.0.45
2.8.0.140
2.8.0.140
1.2.1.20-1
2.7.1.35
2.7.1.35
2.7.1.35
2.7.1.P06
1.0.0.35
1.0.22.0
2.4.0.13
4.1.1195.0
TLM Recon Deliverables
File Name
Recon Admin\setup.exe
TLM Recon Admin.msi
install_recon
TLM Recon Admin Server 2.7 SP1.exe
recon2_7_1_44.tar
Utilities
AAS Client
3.3
Version
2.7.0.148
2.7.0.148
2.7.1.44
2.7.1.44
2.7.1.44
3.3.0.286
New Documentation
Description
This Software
Release Note
WebConnect Studio
Guide
File Name
TLM Recs 2.7 SP1.pdf
Notes
WebC27WCSG.pdf
User
Administration
Guide
Configuration
Transfer Guide
SmartData27UsrAdm.pdf
Contains information on how to create dashboards,

constraints, rules, and so on, which are now configured
using the new SmartStudio application.
Contains User and Role maintenance information and user
access and limits.
CT 1.0 User Guide.pdf
Contains instructions for the use of Configuration Transfer

(CT), which is the next generation of the Configuration
Import utility (CI).
4 Level of Testing
All issues that are listed in the section Issues Resolved in This Release have been tested.
All new features have been tested, and system-wide regression tests have also been performed.
5 Installation
If you require any assistance with the installation of this software, contact your Account Manager or regional
Support Desk to arrange for a Professional Services engagement.
26
6 Open Source Code used

The following table lists the open source code used in this product:
Antlr
Ehcache
JFreeChart
AOP Alliance
Emma
Joda-time
Apache Commons
gen-java
JSON
Apache Derby
GWT
JSON-RPC
Apache Jakarta
ICU
JSON-RPC-Java
Apache log4j
Jakarta Commons
JUnit
Apache POI
Jakarta Log4j
Libcurl
Apache Struts
Jakarta Oro
Log4j
Apache Xerces
Jakarta Regexp
Quartz
ASM
Jakarta Struts
Saxpath
BIRT
Janino
SigTest
Blowfish
Java Beans Activation Framework
Simple-JNDI
Castor
Java Universal Network/Graph

Framework
Spring
cglib Code Generation Library
JavaMail
util.concurrent
Clickstream
Javassist
Xalan-Java
colt
Jaxme 2
Xerces
dom4j
JCommon
Xml Pull Parser 3rd Edition (XPP3)
drools
JDOM
xmlenc
Eclipse Rich Client Platform (including

Nebula)
JDOM Jaxen
xstream
27
7 Issues Resolved in This Release

This section lists the issues that have been raised by customers that have been fixed in this release. Issues found
internally by QA that have also been fixed are not included in this list.
The Likely Impact field in the tables below denotes the nature if the change, and the amount of testing that is
recommended post implementation, as follows:
Low - Minor change limited to a single component. Only minimal, targeted testing required.
Medium - Relatively major change affecting a single component, or minor change affecting multiple
components. Basic test of affected components recommended.
High - A wide ranging change which has system-wide effects or involves the major refactoring of a key
piece of functionality. Full system-wide functional test recommended.
7.1
WebConnect
Issue No
WBC-788
Description
WebConnect Trial Balances does not allow a user to search
with 'Set Group' as the sole search parameter
Priority
P3
Problem Reported
Currently WebConnect - Trial Balances does not allow a user to search with 'Set Group' as the sole search
parameter. It requires at least one of Set ID, Category, Currency, Security Code, Message Feed or Set Type to
be populated. This is a validation restriction in the code. WebConnect should be modified to allow the 'Set
Group' search field to be used as the sole search criteria. The validation message should also be updated.
Component
Likely Impact
Incident No
Affected
62651
Problem Solution Details
Set Group can now be selected without selecting any other criteria.
Issue No
Description
WBC-854
Casing issues
Problem Reported
It is not possible to carry out a range of casing tasks.
Component
Likely Impact
Affected
Priority
P2
Incident No
59132

Issues fixed.
28
Issue No
WBC-1416
Description
The unlink business logic tool does not remove a missing
balance that was added when linking securites
Priority
P3
Problem Reported
The missing balance value on a message feed was not updated correctly on an unlink operation. When two
security transactions items in Webconnect were matched and linked, a missing balance was correctly created on
the asset header (this could be seen in Trial Balance). When the items were recalled and unlinked the missing
balance should have been removed but wasn't.
Component
Likely Impact
Incident No
Affected
GUI
Low
61775
The balance processing code has been modified with a new formula to calculate the new missing balance when
items are unlinked. The missing balance should now be set correctly after an unlink operation.
Issue No
WBC-1512
Description
Grid returns to start after executing tool on two rows at the
end
Priority
P3
Problem Reported
When selecting the last two rows on a grid and executing test_constraint, the grid returns to the start when you'd
expect it to stay at the end.
Component
Likely Impact
Incident No
Affected
GUI
Tested and working as expected.
Issue No
Description
Priority
WBC-1563
Auto populate Feed Id based on Set ID
P3
Problem Reported
Auto-population of the Feed ID - if the Set ID has been input and there is only 1 ledger or statement, the Feed
ID should automatically populate. Where there are multiple Feed ID's the Feed ID would be input manually.
This is a feature of SSR that is required in TLM
Component
Likely Impact
Incident No
Affected
GMI
Feed ID is auto-populated based on Set ID.
62165
29
Issue No
Description
Priority
WBC-1564
Set ID should be validated upfront
P3
Problem Reported
Set ID is not validated when input. This is one of the last checks that take place, but it should be the first. Any
mandatory fields that are not populated are flagged as an issue first.
Component
Likely Impact
Incident No
Affected
GMI
62165

Implemented custom selector for Header Set Id field. On click of the selector, a popup will display the header
set id and the feed Id for the corresponding message type. On selection of the required row in the selector
popup, the values will be populated in the GMI screen for the corresponding fields. Also, if there is a currency
field in the message header and the user has entered any data in the currency field, then the header currency field
will be populated from the default currency of the Header Set Id.
Issue No
Description
Priority
WBC-1565
GMI is slow on input of many item rows
P3
Problem Reported
Poor response times when manually inputting items. As more items are input, WebConnect gets slower. This is
particularly noticeable when entering a source code, as TLM tries to create a new line at the same time.
Component
Likely Impact
Incident No
Affected
GMI
62165

Changed DropDownMenu for IE 6. Don't Display the new empty row in the item section. User can use
navigation keys to reach the new row.
Issue No
Description
Priority
WBC-1567
Amount fields should have comma as thousand separator
P3
Problem Reported
In the Item Amount field, commas should separate the thousands. This works for the credit, debit and net
balance, so this is inconsistent.
Component
Likely Impact
Incident No
Affected
GMI
Medium
62165
Handled the addition of a thousand separator character for decimal numbers.
30
Issue No
Description
Priority
WBC-1665
Business logic not correctly netting (signs inverted)
P2
Problem Reported
The amount netted on screen is opposite to the amount netted in the execution of the business logic.
Component
Likely Impact
Incident No
Affected
Low
62025

Sign determined to be incorrect for this schema arrangement. Mirroring lead to sign being inverted irrespective
of side and that schema action was not factored in. This issue has been resolved.
Issue No
Description
Priority
WBC-1671
Header Set ID should not be validated from the cache.
P3
Problem Reported
There is an issue with caching of static data in WebConnect/JBoss where WebConnect displays a validation
failure message when validating Set ID and Message Feed. Validation only works when JBoss is restarted. It
appears that only the first newly created Set & Message Feed is recognised following the start-up of JBoss.
Component
Likely Impact
Incident No
Affected
GMI
Low
62325
The Header Set ID is no longer validated from the cache and the App Server need not be restarted for the new
accounts to be effective.
Issue No
WBC-1736
Description
Text of the previous note that the user added remains in the
text prompt
Priority
P3
Problem Reported
When a user adds a note to an item, the text of any previous notes that the user added remains in the text prompt.
This is considered to be an audit risk.
Component
Likely Impact
Incident No
Affected
GUI
The persistence of note messages between note submissions is now a configurable option.
62519
Issue No
WBC-1804
Description
Delete functionality does not delete the row from
ASSET_BALANCE table.
31
Priority
P3
Problem Reported
The delete functionality for message backout works but causes the Gems server shut down when the data is
deleted or reloaded, and as such, the Asset_Balance table must be deleted and the data reloaded from the back
end.
Component
Likely Impact
Incident No
Affected
GUI
61912

Tested and working as expected.
Issue No
Description
WBC-1849
GMI should allow messages with no items
Problem Reported
GMI should allow messages with no items.
Component
Likely Impact
Affected
GMI
Low
Removed the mandatory check for item in the server and UI code.
Priority
P3
Issue No
Priority
WBC-1888
Description
swin.b_last_used should be read from KeyCacheImpl instead
of reading directly from database.
Incident No
62693
P2
Problem Reported
swin.b_last_used should be read from KeyCacheImpl instead of reading directly from database
Component
Likely Impact
Incident No
Affected
GMI
Medium
62604
WebConnect now caches a chunk of message_nos and provide it to GMI for message_no from this chunk. This
will avoid the GEMS server from reading the same message_no.
32
Issue No
Description
Priority
WBC-1895
Add 'Select' and 'Fast-cut' options to context menu.
P2
Problem Reported
Add Select and fast-cut options to the context menu so that the user can still access these options when they
scroll across the screen, without having to scroll back to the left hand side.
Component
Likely Impact
Incident No
Affected
GUI
Low
62888
The options Select Row, Select Group, Select Break Group, Select Aggregate Group, Deselect, Fast-cut and
Fast-cut to New Group have been added to the context menu. The presence of these options is dependent on the
Grid configuration (Show Row Selector, Show Group Selector and Suppress Cut and Paste), and the View
configuration (Show Aggregate Group Selector, presence of aggregate-on-change, etc.). The availability of
options in the menu is dependent on the status of the highlighted (active) row.
Issue No
WBC-1909
Description
Allow editing of boolean flags in casing desktop through item
maintain.
Priority
P3
Problem Reported
A bug on the case edit event where a blank field is displayed when editing the Close When History" field.
Component
Likely Impact
Incident No
Affected
GUI
62955

Occurred when a string decode has been setup on the boolean (integer) fields, when saving it would try to put
the string value into the integer field. Now coded to find the encoded value and this is the value that will be
saved rather than the string decode.
Issue No
Description
Priority
WBC-1916
Inefficiency in application of edit event filters.
P1
Problem Reported
Inside the WebConnect work flow engine the code that applies source and target filters to selected items for edit
events is inefficient.
Component
Likely Impact
Incident No
Affected
62355
Modified the edit event filter logic to retrieve rule data in one go (or split based on parameters) when building
context for the application of filters.
33
Issue No
Description
Priority
WBC-1938
Rounding issue in netting field in GMI
P3
Problem Reported
There is a rounding issue in the netting field in GMI. The Net Balance field in GMI shows 6 decimal places and
when there are large balances keyed in, the net balance will sometimes show 0.000001, which suggests to the
user that the page does not balance and can be misleading. This is a display issue with the WebConnect GMI
screen and does not prevent the page from loading or cause the page to go to Message Maintenance.
Component
Likely Impact
Incident No
Affected
GMI
Low
62929
Issue has been fixed. The value of balanceType is now passed to the user interface. In the UI(js) code, it is
decided whether the decimal will be 3 or 6 places.
Issue No
Description
Priority
WBC-1940
Fast cut into empty scratchpad fails
P3
Problem Reported
After a successful release from the Scratch Pad, any further items that are "cut" from Item Search are removed
from Item Search (correctly) but do not go in to the Scratch Pad. Selecting Scratch Pad as the Fast-Cut target
does not rectify this.
Component
Likely Impact
Incident No
Affected
62766
Fixed fast cut into empty scratchpad (when scratchpad has previously had rows in it that have been removed)
Issue No
Description
Priority
WBC-1947
CPU slow for dashboard refresh
P2
Problem Reported
Following execution of a workflow tool (that is configured to update rows on screen) the JavaScript that
performs the update in the browser can sometimes take a long time to execute. The time taken to update the grid
can be significantly longer than the time taken to open it in the first place.
Component
Likely Impact
Incident No
Affected
Low
Improved performance of code to update grid rows following tool execution.
63043
34
Issue No
WBC-1970
Description
GMI: Currency is not required as the currency is already
populated in the Set ID
Priority
P3
Problem Reported
Issue: GMI- Manual input form forces user to type in currency - this is not compulsory in SSR and is not
required to be compulsory in TLM. Currency is not required as the currency is already populated in the Set ID
Component
Likely Impact
Incident No
Affected
GMI
Low
63160
On selection of the chooser option for the Set ID, if the user has not input the header currency field, then the
header currency field will be populated from the default currency of the Header Set Id.
Issue No
WBC-1997
Description
Priority
Primary Key fields not correctly ordered for Case Transaction
P2
Universe Key
Problem Reported
When executing the TLM Control process from WebConnect, TLM Control is rejecting the message because
the key fields are in a different order in the constructed message compared with the SmartMessage definition.
Component
Likely Impact
Incident No
Affected
Control Interface
63435

Corrected order of primary keys in CaseTransactionKey.
Issue No
Description
Priority
WBC-1999
Base currency conversion performance issue
P3
Problem Reported
Our Item Search Enquiry dashboard is performing extremely slowly (14 minutes to return 5000 items). It is
displaying the below Target Currency attribute.
Component
Likely Impact
Incident No
Affected
GUI
63152

Now only reloads exchange rates once for each grid (rather than for each row in the grid).
Issue No
Description
Priority
WBC-2008
Default category selection when only one category is available P2
Problem Reported
Default category selection is required on launch of GMI when a logged-in user has only one message category
available.
Component
Likely Impact
Incident No
Affected
GMI
63166

When only one message category is available, on launch of GMI it will select this category by default and
populate the GMI screen for corresponding first message type.
Issue No
WBC-2009
Description
Disabling the display of an interaction dialogue for non-zero
amount differences when configured for no warnings
35
Priority
P2
Problem Reported
WebConnect has always displayed the release interaction dialogue for non-zero amount differences. The
warning limits options in Recon Admin will control the display of a "threshold exceeded" discrepancy but not
the "amount difference" discrepancy. This is different to the behaviour of the TLM GUI and will be changed
accordingly.
Component
Likely Impact
Incident No
Affected
GUI
62914

An interaction dialog is displayed for released items with a zero amount difference when other discrepancies
have been identified.
Issue No
WBC-2031
Description
Receiving an error saying Item Amount not complete for the
Ledger Credit grid on Load & Continue.
Priority
P3
Problem Reported
In GMI, an 'Our Cash Settlements' input was completed, and an error was received after clicking the 'Load and
Continue' button, stating that the item amount was not complete for the ledger credit grid on load and continue.
Component
Likely Impact
Incident No
Affected
GMI
64567

The suppressed onchange event for mandatory numeric field is invoked after formatted value is set to the field.
Issue No
WBC-2033
Description
Priority
Enhance the WebConnect Message Maintenance dashboard to
show if the page balances, and the Net Input / Remaining
P3
Totals, and a total of debit/credit entries.
Problem Reported
A Message Maintenance dashboard has been built but the functionality is different to that of SSR.A view that
displays the following is requested:
The validation of the total of items on a rejected statement/ ledger page, the opening and closing balance, the net
input, and the remaining totals.
A total of debit and credit entries without the need for manual calculation using filters.
Component
Likely Impact
Incident No
Affected
GUI
The required functionality was implemented for GMM-GMI.
63574
36
Issue No
WBC-2140
Description
Workflow rule is not setting reserved attribute values for
processing
Priority
P2
Problem Reported
Workflow in WebConnect isn't validating dates correctly, for example, when comparing Entry date with System
date..
Component
Likely Impact
Incident No
Affected
GUI
63508

WebConnect was not correctly setting the value for the reserved attribute. This has now been resolved.
Issue No
WBC-2336
Description
OutOfMemoryException thrown opening message
maintenance dashboard
Problem Reported
It is likely that the WebLogic server is running out of memory.
Component
Likely Impact
Affected
GUI
Priority
P2
Incident No
100231

Reverted to using a text edit when editing setId (form & bulk edit). Added validation when changing setId in
forms, bulk edit and editing directly in the new grid.
Issue No
WBC-2390
Description
Support UPD_CASE_ITEMS_SUMM flag for accept/reject
amount and reference
Priority
P4
Problem Reported
Regardless of whether the syst_value is set to 0,1, or 2, users are still prompted to accept or reject amount and
reference, which is not expected behaviour.
Component
Likely Impact
Incident No
Affected
GUI
100628

Respect the UPD_CASE_ITEMS_SUMM SYST setting as described.
Issue No
WBC-2414
Description
Check for Bank Account lead currency does not spot empty
lead currency
Problem Reported
Position items cannot be matched in thin client. Matching in thick client works OK.
Component
Likely Impact
Affected
GUI
Ensure a blank lead currency is handled correctly.
Priority
P2
Incident No
100836
37
Issue No
Description
Priority
WBC-2434
Unable to attach documents to Cases
P2
Problem Reported
The user is unable to attach documents to Cases. Log in as user "attach" (password "attach") User "attach" has
access through WebConnect to "Case Summary (Web)" A blank search on this returns a number of Cases. When
an unresolved case is selected from the list the option to attach a document becomes enabled and when selected
opens a new window. The user is allowed to browse to a file and then needs to add a note before selecting OK.
The user should receive a report to state that the document has been successfully attached however, an error is
reported: "There was a problem attaching the specified document, please contact your system administrator."
The WebConnect.log states "Error while Attaching Document" and "Received Null Lob Id from Cache"
(Attached) NB The environment should be noted as this is working on hora08... this is using Linux, JBOSS 4.2
with unicode switched on.
Component
Likely Impact
Incident No
Affected
Medium
103242
This occurred only on JBoss running 2.6 onwards, it was caused by WBC-1399. Have modified the database
write so the error doesn't occur.
Issue No
Description
Priority
WBC-2436
Trial Balance fails for large number of sets
P3
Problem Reported
An error in the log seems to be caused by a bug whereby, when the currency or asset feed search returns in
excess of 1000 sets, the item table search fails because the Oracle driver cannot handle more than 1000
predicates in the SQL and this is not handled correctly. Additionally, when the logs are showing
OutOfMemoryError this means the amount of data loaded is too much for the memory allocated to the
application server. You can increase the heap size for the application server but a search of this size is always
going to be very slow.
Component
Likely Impact
Incident No
Affected
GUI
Low
100848
The Trial Balance search was failing for some very large searches. Specifically, if the number of distinct sets in
the search was in excess of 1000, the search would fail with an error. The search query has been fixed so that the
Trial Balance can load this quantity of data. Note, however, that searches are this size are very slow and will
require significant memory resources from the application server.
Issue No
WBC-2509
Description
Ensure fast-cut operation moves active row, so that grid
doesn't scroll back to previous active row
Priority
P2
Problem Reported
Currently, if you fast-cut the active row on a grid it moves the active row to the next row in the grid. However,
if you fast cut a row other than the active row it scrolls the grid back to that active row after the fast-cut. The
fast-cut operation should effectively make the chosen row active before the cut is done and then let the logic
move the active row to the next row, just as if the user had clicked on the row before fast-cutting.
Component
Likely Impact
Incident No
Affected
101269
In the case of a fast cut, the active row is now set explicitly to be the row corresponding to the fast cut button
clicked on.
38
Issue No
WBC-2515
Description
Provide a means of viewing the charge amount on a
productised (released) cash match in the audit trail
Priority
P2
Problem Reported
Currently, there is no way of directly viewing the amount difference on a released match. The audit trail shows
if a net item was produced and also displays an entry for any interest amount raised. However, it doesn't directly
show any charge-amount raised if no net item was created. We should consider creating an extra display node in
the audit display, under a released match entry, that can spot when a charge amount has been created from the
match (non-zero charge_amt on TRNS) and display that amount with the associated currency, in the audit alongside any interest node.
Component
Likely Impact
Incident No
Affected
GUI
100990

Display charge amount in audit trail (node appears labelled 'Amount Difference' if applicable).
Issue No
Description
Priority
WBC-2554
Add Notes Custom Control is failing due to code merge issue P2
Problem Reported
The Add Notes Function is not working in 2.6Sp1. This is due to a merge issue when the CCD User
Maintenance code was checked in 2.6Sp1. The root cause of this issue is present in CustomSubmitAction.java.
Component
Likely Impact
Incident No
Affected
CCD
101454

Place the code snippet in the place it was before, and remove it from individual places except for group
submission. At the end of code specific to group submission ensure that gridRow is null so that common code is
not executed for group submission.
Issue No
Description
Priority
WBC-2581
Confirmation Limits not being used correctly for net items
P2
Problem Reported
When a user Logs into TLM 2.6 WebConnect as a non-Admin user and releases two items, amounts of which
exceed the users limit set in Recon Admin, the user has to enter their Supervisor userid/password. The User
credit Netting Limit (of the Supervisor) being read in such a case is not in accordance with the setting in Recon
Admin and thus is an issue and needs to be corrected. Essentially, if a release requires confirmation and it is
selected for netting, the confirmation limits then used are the charge confirmation limits rather than the net
confirmation limits. A proper check of the netting option needs to be made to determine which set of limits to
use.
Component
Likely Impact
Incident No
Affected
101428
The release of cash items is now handled correctly in cases where the confirmation of a supervisor's net limits is
required.
Issue No
WBC-2609
39
Description
Priority
Edited rows disappear after refresh if they no longer meet the
P2
search criteria
Problem Reported
It should be possible to see rows that have been edited after a refresh even if the changes made would cause the
row to no longer be returned.
Component
Likely Impact
Incident No
Affected
101888
Rows that have been edited now remain visible after a refresh even if the changes made would cause the row to
no longer be returned.
Issue No
WBC-2621
Description
Enable selectors in the bulk edit dialog that take precedence
over dropdowns in forms.
Priority
P2
Problem Reported
Enable selectors in the bulk edit dialog that take precedence over dropdowns in forms, so that an attribute which
has a dropdown can be overridden with a selector definition. This needs to include validation if the field is a text
box, to prevent incorrect source codes from being entered into the system.
Component
Likely Impact
Incident No
Affected
101887
Enabled selectors in the bulk edit dialog that take precedence over dropdowns in forms.
Issue No
Description
WBC-2622
Allow fast-cut of multiple items.
Problem Reported
Need the functionality required to fast-cut multiple items.
Component
Likely Impact
Affected
Priority
P2
Incident No
101614

It is now possible to fast cut a selection of rows in a single operation.
Issue No
Description
Priority
WBC-2623
Allow date entry without separators e.g. 101208 for 10/12/2008 P2
Problem Reported
Allow date entry without separators e.g. 101208 for 10/12/2008
Component
Likely Impact
Incident No
Affected
101881
Users can now enter dates with or without separators e.g. 101208 or 10/12/2008 are equivalent.
40
Issue No
WBC-2624
Description
Don't show ellipses (...) in grid data where column width is
configured to be "very narrow".
Priority
P2
Problem Reported
Dashboard grids need the ability to only display a single character regardless of the length of the field. Currently
columns display (...) when the data is continued. By design, some of our dashboards only display the first
character of a field (O for Outstanding, H for History, etc.)
Component
Likely Impact
Incident No
Affected
101886
Grid cells that are too narrow to display their contents in full will not show ellipsis (...) if that would result in the
content not being displayed.
Issue No
Description
Priority
WBC-2643
Audit Trail fails to display for some NET items
P2
Problem Reported
When opening the audit trail for certain NET items, a SQL Exception in thrown which is likely due to a bug in:
AuditTrailOtherDAO.populateChargeAmountDetails(). The code is attempting to load a column called:
system_currency. This column is only present in the results some of the time (because different SQL queries use
this code). This column name should be removed entirely and replaced with a call to the
SystemParameterService to load the syst parameter for system currency.
Component
Likely Impact
Incident No
Affected
GUI
Low
102042
A previous patch fix has uncovered an error with the database search. This error caused the audit trail to fail for
NET items when the system base currency was loaded. The database query has been fixed so that the audit trail
will work for all items.
Issue No
WBC-2655
Description
A release that exceeds a user's charge limit is subsequently
evaluated against confirmation limits in all cases.
Priority
P2
Problem Reported
If a release exceeds a user's charge limit and the decision is made to check the "net item" box in the interaction
dialogue, rather than re-evaluating against the user's net limits, the release always progresses to authorising with
supervisor limits. In this case, it should be possible to perform release against the user's net limits.
Component
Likely Impact
Incident No
Affected
101428
A release that exceeds a user's charge limits may now be evaluated against net limits following the checking of
the net item option in the interaction dialogue, rather than proceeding to supervisor authorisation in all cases.
Issue No
WBC-2675
Description
Set ID is not populated for all messages in GMMI when it is
opened via GMM.
41
Priority
P3
Problem Reported
If you select a message from the GMM grid, Set Id is present for that message. When you open the message in
GMMI, Set Id is populated as a blank message. This issue is consistent with all messages.
Component
Likely Impact
Incident No
Affected
CCD
101878

WBC-2679 : WebConnect cache is updated if it doesn't contain the requested Account ID. WBC-2675 : Now
Set ID field is populated correctly when using GMM-GMMI
Issue No
WBC-2679
Description
Set ID is not displayed for a newly created account in GMMI
when it is opened via GMM.
Priority
P3
Problem Reported
After creating a new account for a message type, the accounts Set ID is not displayed when the message is
opened in GMMI via GMM. The Set ID is only displayed when WebConnect is restarted.
Component
Likely Impact
Incident No
Affected
CCD
101878

WebConnect cache is updated if it doesn't contain the requested Account ID. WBC-2675 : Now Set ID field is
populated correctly when using GMM-GMMI
Issue No
Description
Priority
WBC-2738
Allow six digit date entry in GMMI
P2
Problem Reported
GMMI screen allows user to enter dates in six digit format e.g. 251208 instead of 25/12/2008 but this is not
useful since the six digit format can't be validated on the server. The front end should rewrite valid six digit
dates before submission to the server.
Component
Likely Impact
Incident No
Affected
GMI
101881

GMMI allows to enter date in six digit format e.g. 251208 and the front end rewrites a valid six digit dates to
required 25/12/2008 format.
42
Issue No
WBC-2739
Description
Allow six digit date entry in form control, item edit form,
analytics search prompts and business logic interaction
Priority
P2
Problem Reported
The form control, item edit form (bulk edit), analytics search prompts and business logic interactions allow user
to enter dates in six digit format e.g. 251208 instead of 25/12/2008 but this is not useful since the six digit
format can't be validated on the server. The front end should rewrite valid six digit dates before submission to
the server.
Component
Likely Impact
Incident No
Affected
GUI
101881

Six digit date entry is now supported in form control, item edit form, analytics search prompts and business
logic interaction.
Issue No
Description
Priority
WBC-2756
Create custom control to display the expandable attribute.
P3
Problem Reported
The current process for viewing data associated with expandable attributes has been found to be cumbersome
and in some cases does not work at all. A simpler solution is required, maybe by making use of a separate
dashboard.
Component
Likely Impact
Incident No
Affected
101873
The solution has been to push the current functionality of displaying expandable attribute messages into it's own
custom control. This new custom control can be configured within design studio (url:
/secure/showexpandableattribute.do) and assigned to the grid control, which contains the expandable attribute,
as a drilldown. This allows the user to then drilldown from a row in the grid to view its associated expandable
attribute message.
Issue No
WBC-2792
Description
When entering data in GMI for generic message types, the
"net remaining" text box at the bottom of the screen is not
shown.
Priority
P3
Problem Reported
WebConnect 2.6 SP1 issue: When entering data in GMI for generic message types, the "net remaining" text box
at the bottom of the screen is not shown.
Component
Likely Impact
Incident No
Affected
GMI
102807

Added a support for balance type Dual Balance, Generic Currency and Generic Asset to show "net remaining"
text box at the bottom of GMI dashboard.
Issue No
WBC-2696
43
Description
Priority
The fast-cut destination grid scrolls to the top of the record set
P3
every time fast-cut is used.
Problem Reported
When cutting rows to a different grid the target grid scrolls to the active row (typically the first row for a
scratchpad grid). This means that the newly cut rows are not necessarily visible. The newly cut rows should
always be visible.
Component
Likely Impact
Incident No
Affected
GUI
102328

When cutting rows from one grid to another, the target grid will scroll so that the last row cut is visible.
Issue No
Description
Priority
WBC-2736
LDAP configuration allows user to log in with blank password. P2
Problem Reported
LDAP can legitimately allow a user to log in with a blank password. WebConnect should be updated so that a
user cannot log in with a blank password. The workaround is to configure LDAP to disable anonymous binds.
Component
Likely Impact
Incident No
Affected
GUI
102355

Users can no longer log in using a blank password through LDAP authentication.
Issue No
Description
Priority
WBC-2740
Default highlight of selected row is very difficult to see.
P2
Problem Reported
Issue raised previously under SI 100487 and partially addressed via WBC-2401. Problem still exists, as the fix
did not address the default darker/more visible 'tramlines' - only that they are configurable. Change default
current row highlighting from WHITE to BLACK.
Component
Likely Impact
Incident No
Affected
101137
Changed default row highlight colour to black.
44
Issue No
WBC-2776
Description
Allow character months in date format & control over 2-digit
years
Priority
P2
Problem Reported
Due to the international nature of our business, we are looking to have control over the display format of dates
in WebConnect. We are proposing a format of "DD-MMM-YY".
Component
Likely Impact
Incident No
Affected
GUI
102379

Added facility to define system-wide custom formats for date values, configured by an entry in the syst table. It
is possible to configure different formats for different locales. If a custom format is defined for a user's locale
then that custom format is used for that user's session. If there is no custom format defined for a user's locale
then WebConnect will default to use the standard Java "SHORT" format as before. To enable the custom
formats an entry is added to the syst table with the following SQL: insert into syst
(syst_name,description,syst_title,syst_type,syst_string) values ('DATE_FORMAT','WebConnect - custom date
format','WebConnect - custom date format',1,') Then the customs formats can be set using SQL similar to this:
update syst set syst_string='en_GB=dd-MMM-yyyy,en_US=MMM-d-yy' where syst_name='DATE_FORMAT'
The configuration string specifies the locale and the format separated by an = sign. Specifications for multiple
locales must be separated by a comma. The locale and format are specified in a similar way to the standard Java
Locale and DateFormat. Only the date part of the format is configurable (there is no support for configuration of
the time of day format) and only the d, M and y pattern letters are supported. ref:
http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html ref:
http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html
Issue No
WBC-2808
Description
Priority
After invoking the GMMI window from Message Maintenance
and cancelling the input, refreshing the Message Maintenance P2
window causes the search to run indefinitely.
Problem Reported
After invoking the GMMI window from Message Maintenance and cancelling the input, refreshing the Message
Maintenance window causes the search to run indefinitely.
Component
Likely Impact
Incident No
Affected
CCD
102864

The main cause of this issue that custom control was not built correctly in UI tier and it is fixed in
gmmGmmi.jsp.
Issue No
WBC-2811
Description
Priority
Remove the loading of all set IDs which causes problems in the
P2
case where there are too many to handle.
Problem Reported
Remove the loading of all set IDs which causes problems in the case where there are too many to handle. The
worst of this was fixed by WBC-2336, this will go the whole hog.
Component
Likely Impact
Incident No
Affected
GUI
Removed the loading of all set IDs per user.
101633
Issue No
WBC-2815
Description
Net items that have gone on through (un-audited) workflow
processing cannot be recalled
45
Priority
P2
Problem Reported
Clone of issue on 2.6SP1. In WebConnect, item matches that create net items that have gone on through (unaudited) workflow processing cannot be recalled. 1. Release two items that will create a net item (due to an
amount discrepancy). 2. Run a workflow tool against the net item that has a single UNAUDITED event (e.g. an
unaudited edit event on Reference 1). This will update the net item softlock but not the audit ID. 3. Recall the
original item match. 4. WebConnect will attempt to recall the net item and will fail with the message: 'This
group may not be recalled as you are attempting to recall the items matched against the lead item in a different
order from that in which they were released.' This occurs because the net item recall is using the
'event_group_id' instead of the 'audit_id' to test if the item can be recalled. This error has been present in
WebConnect since 2.6.
Component
Likely Impact
Incident No
Affected
Low
101302

WebConnect was not able to recall net items that had undergone unaudited workflow since creation. The recall
process was incorrectly using the item softlock instead of the audit ID to determine if the item could be recalled.
The recall process has been fixed to correctly recall net items.
Issue No
Description
Priority
WBC-2833
Document template fails to parse currency field
P3
Problem Reported
When user manually create the document : YOU BUY currency is being shown correctly as item.currency_2
which is SGD for this item but YOU SELL currency is not being reflected in the document .
Component
Likely Impact
Incident No
Affected
GUI
102384

The currency that was being used was taken from the bank row or message header row associated with the item,
rather than the item currency itself. The fix is to explicitly overwrite the currency with the item currency to
ensure this is the value that is used.
Issue No
WBC-2845
Description
Summary row to include break down of data and aggregate
rows
Priority
P2
Problem Reported
The summary row needs to be modified to include total values of both data row and aggregate rows, where
applicable.
Component
Likely Impact
Incident No
Affected
GUI
102380

The summary row now provides a more complete descriptions of the total rows presented in a grid, including
the original data row count, the number of rows filtered out and the number of aggregate rows added as
appropriate.
46
Issue No
WBC-2850
Description
Priority
Include the option to maintain grouping following modification
P2
to sorting
Problem Reported
Currently, all grouping is removed upon the first user initiated change to sorting configuration. In some cases it
may be desirable to keep the grouping behaviour of a grid's view while adding, removing, reordering or
reversing the sorting behaviour on one or more columns.
Component
Likely Impact
Incident No
Affected
GUI
102578

It is now possible to maintain the grouping of rows following the modification of a grid's sorting configuration.
This optional behaviour may be enabled globally through the setting of a -DmaintainGroups=true parameter
when launching WebConnect.
Issue No
Description
Priority
WBC-2923
Add case note on case edit failing - transaction issue
P3
Problem Reported
Select a row in a case grid and edit. On save changes, add a note. An exception is thrown. IllegalStateException:
Trying to change transaction TransactionImple < ac, BasicAction: -3f5791e4:7a8:49917202:57 status:
ActionStatus.RUNNING > in enlist! This occurs on JBoss4.2.3.
Component
Likely Impact
Incident No
Affected
GUI
103380
Add note to case on edit should now work when running on JBoss
Issue No
Description
Priority
WBC-2932
Enforce uppercase based on schema for Choosers and forms. P3
Problem Reported
Enforce uppercase based on schema for Choosers and forms.
Component
Likely Impact
Incident No
Affected
GUI
Low
103336
Within forms ensured fields take into considering the specified font case as defined on their associated
attributes. If upper case is required, then user input will be transposed appropriately. This fix also resolves the
issue relating to the chooser, in that text copied from an upper case field into the chooser filter, will now be in
the expected format.
Issue No
WBC-2942
Description
Date range difference not correctly calculated for workflow
rule
47
Priority
P3
Problem Reported
We have a workflow rule that tests the values passed in a group from WebConnect, to ensure that settlement
dates fall within a certain range of each other. Prior to this test we have ensured that the group contains only two
items with settlement dates of 19/11/2008 and 25/11/2008. I have substituted the rule CSH SETT DATE GAP <
4 by one which tests that all settlement dates are the same. With this test in place the group failed this workflow
step. It seems that the range test simply does not work. I have checked that there are no non-working days set up
over the period between 19/11 and 25/11. With the rule changed to a range of 2 days, our test case still passes.
In other words TLM thinks that there are 2 or fewer days between 19th and 25th of November.
Component
Likely Impact
Incident No
Affected
GUI
102435
Corrected the date range difference algorithm to ensure the correct max and min dates are used.
Issue No
Description
WBC-2945
Not supporting under limit and over limit checking
Problem Reported
The warning screen for under charge limit matches is not displaying.
Component
Likely Impact
Affected
GUI
Low
Coded to support Under/Over limits for interest and charges.
Priority
P3
Incident No
102764
Issue No
Description
Priority
WBC-2947
Audit trail fails to open correctly on Sybase
P2
Problem Reported
When an item is passed through my initiation event, NO AUDIT TRAIL comes up for the item. When you click
on audit trail the audit trail box appears saying Associated Items, and there is nothing displayed.
Component
Likely Impact
Incident No
Affected
GUI
103468
Handle ID by correct data type.
Issue No
Description
Priority
WBC-2948
Not netting positions items correctly during release workflow P2
Problem Reported
Set up a release workflow that will test the net of an Our Positions item and a Their Positions item. One value
should be subtracted from the other based on schema sign, however they are added.
Component
Likely Impact
Incident No
Affected
GUI
102874
Securities items' sign should be inverted if a ledger account, and inverted again if a mirrored account. This then
provides the correct multiplier for netting calculations.
48
Issue No
Description
Priority
WBC-2959
Document template fails to parse currency field
P3
Problem Reported
When user manually create the document : YOU BUY currency is being shown correctly as item.currency_2
which is SGD for this item but YOU SELL currency is not being reflected in the document . Fix went in to 2.7,
but SQL is not Oracle compliant.
Component
Likely Impact
Incident No
Affected
GUI
102384
The currency that was being used was taken from the bank row or message header row associated with the item,
rather than the item currency itself. The fix is to explicitly overwrite the currency with the item currency to
ensure this is the value that is used. Ensure SQL is Oracle compliant.
Issue No
Description
WBC-2978
GMI Dashboards should raise when clicked on
Problem Reported
The GMI Dashboard should raise when clicked on.
Component
Likely Impact
Affected
GUI
Low
GMI Dashboard now raises when clicked on
Priority
P3
Issue No
Description
WBC-2979
Analytics Dashboards should raise when clicked on
Problem Reported
The Analytics Dashboards should raise when clicked on.
Component
Likely Impact
Affected
GUI
Low
Analytics Dashboards now raises when clicked on
Priority
P3
Issue No
WBC-2984
Incident No
101882
Incident No
101882
Description
Priority
The 'retain note text' system setting is not respected by the edit
P2
tool
Problem Reported
When the SYST setting 'RETAIN_NOTE_TEXT' is set to true, the note dialogs on the business logic tools will
remember and display the last entered note. It has been observed that the note dialog on the productised edit
save tool on grids does not remember and display the last entered note.
Component
Likely Impact
Incident No
Affected
GUI
Low
103135
Added the 'Retain Note Text' system parameter functionality to the edit save tool. The note dialog on a save will
now 'remember' the users last note.
49
Issue No
Description
Priority
WBC-3163
Validation of long decimal numbers does not work correctly
P2
Problem Reported
The validation in the bulk edit form of long decimal numbers sometimes incorrectly fails the 'decimal place'
check . To reproduce: 1. Create a 'security positions' item grid with an edit save tool. 2. Add the attribute : 'Item
On Loan Quantity' (ID 665) to the view. 3. Open grid and select a row. 4. Open bulk edit form (using right-click
edit option) and enter '12345678901' (i.e. 11 digits) into the 'Item On Loan Quantity' field. 5. Submit changes
and you should get an error "Invalid value for field: Item On Loan Quantity" even though the decimal places
have not been exceeded. This issue is related to the conversion from a Long to a Double to a BigDecimal in
GenericAttributeValidator.
Component
Likely Impact
Incident No
Affected
GUI
Low
104061
The attribute validation has been modified to prevent stripping of trailing zeros on a number value when the
number is in scientific notation.
Issue No
Description
Priority
WBC-3175
Tool constraint using lead user fails on dashboard open
P3
Problem Reported
If in case of the Delete tool I use Constraint Management and in the constraint Rule Detail I specify e.g.: Lead
User ID = 'LDLATNE1' then instead of the dashboard in WebConnect I can see an error message. I have tried to
change the constraint rule and instead of Lead User ID use Current User ID. In this case I can see the dashboard.
Component
Likely Impact
Incident No
Affected
GUI
Low
104230
Ensure the user id is available for tool constraint evaluation.
Issue No
WBC-3196
Description
Priority
GMMI : An input string like 01-02-03 is being interpreted as a
P3
date in the year 0003 rather than the year 2003
Problem Reported
An input string like 01-02-03 is being interpreted as a date in the year 0003 rather than the year 2003 in GMI.
This issue occurs in WebConnect 2.6SP1.
Component
Likely Impact
Incident No
Affected
GMI
102379
Now GMI and GMM/GMMI handle custom date format correctly.
50
Issue No
WBC-3202
Description
When the user try & load a message for the same day as a
previous currency_balance (& there are no missings), GMI
does not give the option to carry on & submit.
Priority
P3
Problem Reported
When the user try & load a message for the same day as a previous currency_balance (& there are no missings),
GMI does not give the option to carry on & submit. It prevents the input when the user get the 'No missing'
message', where the user should be allowed to submit message.
Component
Likely Impact
Incident No
Affected
GMI
Low
104135
When the user gets the 'No missing' message', rather than preventing submission, the user is allowed either to
submit message or to cancel it.
Issue No
Description
Priority
WBC-3245
WebConnect times out releasing two items
P3
Problem Reported
Matching two o/s cash items (ls_types 2 and 4) where one of those is a NET item results in excessive query on
OIRC / OIRD to ascertain the interest applicable to the match. The superfluous query appears to come from the
fact that all underlying items from the NET item are included in this calculation when I do not believe this
should be the case i.e. only use the current items in match group and their value dates.
Component
Likely Impact
Incident No
Affected
GUI
103260
Currency rates are now resolved more efficiently.
Issue No
WBC-3279
Description
Unable to recall create data event items created as part of
release workflow
Priority
P3
Problem Reported
Unable to recall any items that have been created using a Create Data event through Release workflow.
Component
Likely Impact
Incident No
Affected
GUI
Low
104714
Corrected code to execute as a batch statement, and ensure all items are processed.
Issue No
WBC-3290
Description
Securities transaction items not being netted correctly in
release workflow
51
Priority
P2
Problem Reported
Release two items, one a Their Sells Ledger and one Our Deliveries Ledger. Rule tests abs net item deal
quantity > 0. Select two items that do net to 0. However the rule passes. WebConnect is failing to apply the
correct sign based on side and sign.
Component
Likely Impact
Incident No
Affected
GUI
Medium
104257
The side/sign logic has been rewritten for release items. All release items should net to the correct values
regardless of item type. The sign used is determined by the schema property 5 (Action). This fix affects all cash,
security and generic items in the productised release process.
Issue No
Description
Priority
WBC-3294
Implement a tolerance on balance checks for GMI
P2
Problem Reported
Customer has raised an issue for out of sequence in GMI, wherein the user gets a warning message when there is
a very minor difference between Opening Balance and Latest Closing Balance. We will insert a tolerance value
for the difference.
Component
Likely Impact
Incident No
Affected
CCD
Low
104580
While comparing opening balance and closing balance a small tolerance value will be considered for equality.
This has resolved the problem reported.
Issue No
Description
Priority
WBC-3297
SSO login can still present change password screen
P3
Problem Reported
When a WebConnect user passwords expire, the change password prompt appears through WebConnect,
however when the user tries to update they are presented with a blank screen. Password management is suppose
to be completed via Recon Admin for this type of user and as such the change password option should not be
presented.
Component
Likely Impact
Incident No
Affected
GUI
Low
104908
Do not allow change password in SSO or when using Web Services authentication.
52
Issue No
WBC-3302
Description
Create Data Event Workflow Not Recalled Following Cash
Release
Priority
P3
Problem Reported
Productized recall tool does not recall a create data event item fired as part of release workflow. This is
following a cash release.
Component
Likely Impact
Incident No
Affected
GUI
Low
104716
Items created via a release workflow containing a create data event now get recalled successfully.
Issue No
WBC-3315
Description
Create case event not finding correct amount for currency
conversion
Priority
P3
Problem Reported
Firing a create case event with item currencies that are not in the base currency throws an exception.
Component
Likely Impact
Incident No
Affected
GUI
Low
104563
Add the amount attribute to the required attributes for the create case event, as this may be needed for
converting to base currency to determine the lead item. This attribute may not already have been added if none
of the four Create Case amounts are this amount attribute.
Issue No
Description
Priority
WBC-3326
The Edit Case tool does not refresh child dashboards
P2
Problem Reported
The 'Edit Case' productised tool does not trigger the (correctly configured) child dashboards to refresh when a
edit is saved. Stale data is left on the child dashboards. As the form edit and other business logic tools do trigger
refreshes, I think the productised edits tool should do so as well. Scenario: 1. Create a Case Summary dashboard
with a Case Details child dashboard (see Case Summary on WC_Reg_Test) 2. Configure a 'Edit Case' save tool
on the case summary dashboard. 3. Load dashboard and open child. 4. Edit a field in the parent dashboard and
save it. 5. Observe that the parent grid row refreshes but the child control does not. See incident details for more
detail.
Component
Likely Impact
Incident No
Affected
GUI
Low
104254
Child dashboards are now refreshed after edits in the parent grid have been saved.
53
Issue No
Description
Priority
WBC-3366
SSO URL allows multiple launches of WebConnect
P3
Problem Reported
It's possible to launch WebConnect multiple times (for a single user and session) in a SiteMinder environment
using bookmarks, favourites, or links. In this particular case a URL in an e-mail. i.e.
http://******:8080/WebConnect/login/siteminder.jsp The presence of more than one application window can
cause various problems and WebConnect should guard against it happening.
Component
Likely Impact
Incident No
Affected
GUI
Low
104908
Modified SiteMinder JSP to prevent it launching a WebConnect application window if the user is already
logged on.
Issue No
WBC-3382
Description
Attempting to save a case edit causes an UpdateException
during row refresh
Priority
P2
Problem Reported
From the incident: After editing a case, it is not possible to save it. In the log file I can see the following error:
Incorrect syntax near 'C'. It looks like that something (where?) is missing between ( C.event_id =
EVDE.event_id ) (C.case_no=4408271)
Component
Likely Impact
Incident No
Affected
GUI
Low
105183
The saving of case edits has been made more robust with regard to the subsequent refresh of row data from the
database.
Issue No
WBC-3406
Description
Web Services authentication does not support '$' and '&' in
the username or password
Priority
P3
Problem Reported
Authenticating via web services does not support having a dollar sign or an ampersand character in the
password.
Component
Likely Impact
Incident No
Affected
GUI
Low
104866
Parse $, &, < and > characters in password by parsing/escaping before creating XML message.
54
Issue No
Description
Priority
WBC-3435
MAXIROWS not respected on Sybase
P2
Problem Reported
Sybase driver does not respect call to setMaxRows.
Component
Likely Impact
Incident No
Affected
GUI
Medium
105156
The Sybase driver is not respecting the call to set the maximum number of rows to return, so all are being
brought back and processed (causing memory issues in WebConnect). Updated the code to only process the
maxi rows number of rows returned. Setting maxi rows is still in place as this is respected by SQL Server and
Oracle. Still allows unlimited rows to be processed for Corona.
Issue No
Description
Priority
WBC-3459
Close when history not respected on create case event
P2
Problem Reported
In FX Confos, the status of the trades will be changed to HISTORY upon manual match /force match, and the
CASE STATUS should also be auto set to 'RESOLVED'. However the case status remained as
"UNRESOLVED" , even though in the create case event , it has been set to "Close when History".
Component
Likely Impact
Incident No
Affected
Low
105218
Use the status field for checking whether to resolve the case.
Issue No
WBC-3666
Description
Workflow rule with abs net amount fails to resolve correctly
(Trunk)
Priority
P3
Problem Reported
Create a Workflow Rule on a Generic Cash Rec where "abs net Item Amount less than '0.01'", and trigger it
against an item with amount 0.13 JPY, it passes,
Component
Likely Impact
Incident No
Affected
GUI
Low
105818
Ensured that the syst setting "USE_BANK_CURRENCY" is applied during rule processing
Issue No
WBC-3692
Description
Priority
The SmartStudio client can take several minutes to start-up on
P2
a slow network.
Problem Reported
On an unreliable and/or latent network the schema loading phase can take several minutes.
Component
Likely Impact
Incident No
Affected
SmartStudio
Low
105759
Performance improvements have been made which should affect the loading of SmartStudio clients on slow
networks.
Issue No
WBC-2955
Description
Users are able to submit a Trial Balance search that can
include a large number of Sets that effectively brings
production to a halt.
55
Priority
P3
Problem Reported
Original quoted problem was "Users are able to submit a Trial Balance search without any parameters being
entered that effectively brings production to a halt." "Customer is requesting some mechanism to prevent such
searches from commencing, such as mandatory search parameters in the Trial Balance prompt, or even just
some default text in the Set ID box that must be overwritten." In fact the trial balance search does insist that you
must fill in a Set, Group, Currency, Category or Set-type, but some of those parameters can cover a very large
number of Sets. Default text would not work & would just be an annoyance to other users.
Component
Likely Impact
Incident No
Affected
GUI
Low
103428
A maximum number of sets will be specified in the SYST setting: 'Trial Balance set search limit'. The default
value is 1000. If the SYST value is missing then it is unrestricted. If a Trial Balance search will be calculating
Trial Differences for more accounts that the maximum (even if some sets are subsequently filtered out), then the
user will be prompted to change the search criteria.
Issue No
WBC-2961
Description
Provide a means to configure the browser polling interval
between business logic progress updates.
Priority
P2
Problem Reported
When a user instigates server-side business logic execution, the browser periodically polls for progress updates.
The polling interval is hard-coded to one second. This results in a large number of http request / response cycles
for long running logic and consequent load on the network and http server. Some control over this load could be
provided if the polling interval could be configured to adapt to the logic's execution time.
Component
Likely Impact
Incident No
Affected
GUI
103642
The browser polling interval during business logic processing can be configured by a new entry on the SYST
table (syst_name = 'BL_UPDATE_DELAY'). This entry is a string comprising a semicolon separated list of
integers, e.g. '1000; 3000; 5000; 10000'. Each integer represents an interval in milliseconds so the example
string represents four intervals of duration 1, 3, 5 and 10 seconds. The first time that the browser polls it will
wait for first specified interval, then the second time it will wait for the second interval and so on. Once the end
of the list is reached the last interval will be used for subsequent polling intervals.
Note that the minimum interval that the browser will wait is 1000ms. If an interval shorter than this is
configured, the minimum will be used.
56
Issue No
WBC-2982
Description
The bulk edit tool does not validate the existence of entered
values for certain attributes
Priority
P2
Problem Reported
When edits are saved on a grid, some attributes (e.g. currency, source code) are checked against the database to
ensure a valid value has been entered (such as a real currency code). However, this check is not performed when
a bulk edit is performed against a number of rows. As a result the user does not find out that a large edit is
invalid until they press the save button. It is proposed that the bulk edit form will perform these validation
checks and reprompt the user for a correction if any entered values fail validation.
Component
Likely Impact
Incident No
Affected
GUI
Low
101883
Added business tier validation to the bulk edit form so that user-entered values for decode attributes or attributes
with existence-checking properties (e.g. Currency, Source Code) will be validated against the permitted values.
This was already happening when the grid was saved but will now also happen the bulk edit form is submitted.
Issue No
WBC-3166
Description
Improve the performance Analytics : Currency Value
Adjusted Balances
Problem Reported
Patch the CVAB performance enhancements from 2.5SP1 to HEAD.
Component
Likely Impact
Affected
GUI
Low
The performance of CVAB analytics screen has been enhanced.
Issue No
WBC-3212
Description
Allow net item value date to be non editable in release group
summary interaction
Priority
P2
Incident No
103683
Priority
P3
Problem Reported
Customer requires the ability to toggle whether the net item being created in release has an editable value date.
This will be driven by a new syst switch.
Component
Likely Impact
Incident No
Affected
GUI
Low
104327
Now allows net item value date to be non editable in release group summary interaction.
Issue No
WBC-3249
Description
Syst flag to toggle writing 0 instead of 10 for Resolution or
Note CAST records
57
Priority
P3
Problem Reported
Make use of SYST-based export settings in WebConnect to decide that any Resolution CAST records or Note
CAST records are written with status = 0 instead of 10 - that will allow a custom version of transmit to pick the
records up & deliver the appropriate messages to PEGA. Case resolution must be consistent no matter how the
case is closed - manually, Case resolve event or auto-close as items go to history.
Component
Likely Impact
Incident No
Affected
GUI
Low
104326
Write 0 to CAST if X_EXPORT_TYPE not STANDARD for Case Resolve.
Issue No
Description
Priority
WBC-3250
Audit of Cancelled Case toggle status by X_EXPORT_TYPE P3
Problem Reported
As per auditing of Resolution, need to be able to toggle status to 0 (case status outbound message waiting) based
on X_EXPORT_TYPE_STANDARD syst switch.
Component
Likely Impact
Incident No
Affected
GUI
Low
104326
Audit of cancelled case status toggled by X_EXPORT_TYPE.
Issue No
Description
Priority
WBC-3277
Extend SSO logout options
P3
Problem Reported
If the GSSO_LOGOUT syst value does not match a header received from the SSO application, assume that this
contains an absolute URL for the logout page. If this syst value is blank, then default to a WebConnect logout
page. This will contain no links or buttons, simply a message stating the user has logged out.
Component
Likely Impact
Incident No
Affected
GUI
Low
104708
Logout URL can be passed in header, or looked up in syst, or default to a WebConnect logged out page.
Issue No
WBC-3321
Description
Priority
Exported Cases should allow same functionality as Unresolved
P2
cases
Problem Reported
Unresolved or pending cases allow: - doc attach - add note - add items to case - cancel case Unresolved cases
allow: - resolve case - download document - delete document Exported cases to allow the same, independent of
CASEREFAMEND syst switch.
Component
Likely Impact
Incident No
Affected
GUI
Low
104326
Exported cases to allow same functionality as unresolved cases independent of CASEREFAMEND flag.
Editability of exported cases still driven by CASEREFAMEND flag.
58
Issue No
Description
Priority
WBC-3486
Tool refresh on items with currency convert attributes is slow P3
Problem Reported
Fire a release tool on a number of items that include a currency convert attribute. The post tool update policy is
to refresh the grid. This checks the for the latest currency rates for every selected row. This should only be done
once.
Component
Likely Impact
Incident No
Affected
GUI
Low
105032
Only refresh the currencies for convert currency attributes once for a grid refresh (as opposed to every row).
Issue No
Description
Priority
WBC-3491
Debug on large release is causing an inefficiency
P3
Problem Reported
When the ReleaseGroupBuilder provides a ReleaseGroup via getReleaseGroup(), it logs a debug message at the
end of the method. The debug message uses toString() on the release group which in turn calls toString() on its
(cash) items. The items use the string of their release group as part of their string so we get this cyclic
dependency. As far as I can make out, the offending code has been around since about 2004. Unfortunately, the
debug message is build even if debug logging is disabled due to a missing if(log.isDebugEnabled()) check
beforehand (this happens a lot in the code and should be guarded as described). So we can do a number of
things: 1 - Ensure that debug strings are only constructed if debug logging is enabled (this would at least restrict
the occurrence of the problem). 2 - Break the cyclic dependency between CashItems and CashReleaseGroups in
their toString() methods. 3 - Dig a bit deeper to find out why we've only now had this problem (perhaps the
items and the group are being associated with each other a bit earlier causing the runaway message at this point).
To actually stop the problem for now (i.e. action point 2) would be trivial.
Component
Likely Impact
Incident No
Affected
GUI
Low
105909
The verbosity (i.e. depth) of debug messages during the release of potentially deep netting item trees has been
restricted and now not constructed at all when debug logging is disabled.
Issue No
WBC-3699
Description
Priority
When an event code is added to one item, the event code for
subsequent recalls should not pre-populate with the last event P2
code selected. (2.7SP1)
Problem Reported
Customer has the following requirements: 1. When an event code is added to one item, the event code for
subsequent recalls should not pre-populate with the last event code selected. 2. It is a requirement for the event
code chosen to appear in the audit trail. 3. It is acknowledged that the event code can be seen by viewing the
notes on a item, but the business would like the event code to be displayed in the main body of the audit trail.
Component
Likely Impact
Incident No
Affected
GUI
Low
106419
RETAIN_NOTES syst setting now retains or discards the last entered event code as well as the last entered note.
Note that if retention of note and event code is not required, then the relevant SYST_VALUE must be set to 0.
59
Issue No
Description
Priority
WBC-3481
gmmGmmiError.jsp file is missing in GMM-GMI.
P3
Problem Reported
Customer has raised this issue because they were getting the following error message (due to incorrect
configuration). > JSPG0036E: Failed to find resource /secure/cust/gmmi/gmmGmmiError.jsp. The request is
forwarded to this file when any exception is thrown in GMMGMMIAction.java. There is not implementation
available for gmmGmmiError.jsp in GMM-GMI.
Component
Likely Impact
Incident No
Affected
GMI
Low
105140
Error handling is provided in GMM, to handle breaking of functionality when no input is provided to input
parameter 'messageNumber' while configuring the custom control.
Issue No
WBC-2949
Description
Priority
Siteminder: Remove the domain name if included in the logon
P2
userid.
Problem Reported
While doing the integration with siteminder at customer site, we encountered a problem Vanguard supplies the
user information to various applications. Basically, customer has two ways we to send the Siteminder response
the SmartStream application. 1. The Standard Header. (HTTP_SM_USER). This will pass the domain/userid
(example: customer\uaqm). The domain is part of the passed user information based on "Windows Integrated
Authentication" and also "NT Lan Manager" (NTLM) architectures. We cannot change how this is passed,. 2.
The Custom Header. (Custom_Header). In addition to the Standard Header, customer has the ability to create
and send a "Custom header" that contains only the USERID. This is the method that SmartStream should use if
they cannot process the Standard Header and extract the USERID. The custom header is used when the
standard header is not feasible, or it does not supply the information required by the receiving application.
Siteminder does not read custom header if there is standard header already available. But WebConnect does not
support the standard header with domain names. PS requesting to remove the domain information if it available.
Component
Likely Impact
Incident No
Affected
GUI
103173
If the username request header contains a domain element (delimited from username with a slash), then strip the
domain element.
Issue No
Description
Priority
WBC-3037
Support Delete Message in Case Transmission universe
P3
Problem Reported
The tool can be selected via the thick client, but is not currently supported by WebConnect.
Component
Likely Impact
Incident No
Affected
GUI
103899
Delete Message tool now supported in WebConnect.
60
Issue No
WBC-3199
Description
Re-instate use of existing CASEREFAMEND switch to allow
exported cases to be edited by users
Problem Reported
Respect CASEREFAMEND syst parameter.
Component
Likely Impact
Affected
GUI
Low
Allow edit of exported cases via CASEREFAMEND syst switch.
Issue No
WBC-3208
Description
Allow NET Item value date to be derived from earliest value
date of released items
Priority
P3
Incident No
104326
Priority
P3
Problem Reported
"Currently the value date on net items is derived from the lead item. An option is required to derive this from the
earliest value date - controlled by a SYST switch"
Component
Likely Impact
Incident No
Affected
GUI
Low
57477
Use the earliest value date from the group of items in the release for the net item if SET_EARLIEST_NET is on.
Issue No
WBC-3342
61
Description
Priority
HVB Hunt - Introduce configurable tolerance on amount fields
P2
in TLM searches
Problem Reported
The SSR Hunt function automatically applied a small tolerance to searched for amounts. WebConnect must
provide a means of optionally allowing a tolerance to be applied to any amount fed into a search at the
individual search prompt level. It must be possible to specify separate 'above' and 'below' tolerances for integers,
amounts (decimals), dates, and dates with times when used in search rules. Backwards compatibility must be
maintained, ie existing rules must work as presently. CI must be able to migrate the rules containing this
configuration SmartStudio must offer configuration for this feature. The tolerances will not editable by the user
at runtime. Exisitng range functiionality can be used to achieve runtime editing if required. The same units
should be used for both the above and below tolerances, ie. If percentage is used for the low tolerance then it
must also be used for the high tolerance. It should be possible to determine whether a tolerance is being applied
by lookinig at the prompt screen. For example by showing a different operator than '='. The allowed values of
the tolerances must be appropriate for the attribute's datatype. ie. Integer attributes will only allow integer
tolerances Amounts will allow decimal tolerances Dates will allow integer tolerances (number of days) Dates
with times should allow a choice of the unit of the tolerance. Either Days, Hours, Minutes or Seconds Strings
will not allow tolerance comparisons Attributes with decodes, or decode by procedure, will not allow tolerance
comparisons. The underlying values of these fields are not visible to the user, so allowing a tolerance would
likely result in non-decodable values. Percentage tolerances must be allowed for integers and amounts, but not
for dates or datetimes. No currency conversion will be performed for any of the comparisons. The tolerance
feature should also work where a range of values if involved, ie. The 'Prompt for Range of Values' RHS
reserved attribute is used. The tolerances may be applied to expressions where the right hand side is either a
literal, a prompt, or the value of another attribute Use Case 1 : The user opens a dashboard and is presented with
a search prompt. A single prompt field is present for the attribute Item Amount. The user enters the value
150.00. The rule has been configured to search for values close to the entered value. There is a below tolerance
of 10, and an above tolerance of 100.50. The generated search will return values >= 140 and <=250.50 Use Case
2 : The user opens a dashboard and is presented with a search prompt. A single prompt line is present for the
attribute Item Amount with a From and To value The user enters the values 100.00 to 250.50 The rule has been
configured to search for values close to the entered value. There is a below tolerance of 10, and an above
tolerance of 100.50. The generated search will return values >= 90 and <=351 Use Case 3: The user opens a
dashboard and is not shown a search prompt. The search rule is configured to show rows where Item Amount is
close to the value of Item Extra Amount 1. There is a below tolerance of 10, and an above tolerance of 100.50.
The generated search will return values where Item Amount >= (ItemExtraAmount1 - 10) and Item Amount <=
(ItemExtraAmount1 + 100.50)
Component
Likely Impact
Incident No
Affected
102476
Configurable tolerance on amount fields in TLM searches implemented.
Issue No
Description
Priority
WBC-2903
Unable to attach documents to Cases
P2
Problem Reported
Unable to attach documents to Cases Receive an error in WebConnect when trying to attach a document to a
case. It looks as it might be a db related error as per error logs attached. (cannot locate next id)
Component
Likely Impact
Incident No
Affected
103242
Fixed in 2.7SP1 by WBC-2434
62
7.2
Design Studio
Issue No
Description
DST-626
Save Option box is blank for case Desktop changes
Problem Reported
When you make a change on the case desktop, the save option box that appears is blank.
Component
Likely Impact
Affected
GUI
Low
Use the existing message from the emsg table.
Priority
P1
Incident No
5008
Issue No
Description
Priority
DST-635
Memory leak when opening dashboards multiple times
P2
Problem Reported
When repeatedly opening dashboards which pass parameters, a small but persistent memory leak is observed.
The memory leak appears to be around 5MB after 100 iterations.
Component
Likely Impact
Incident No
Affected
GUI
Low
51469
The code has been changed to prevent memory leakages.
Issue No
DST-636
Description
Asset Transactions Manual Input amounts and currencies
validation is incorrect for zero amounts
Priority
P1
Problem Reported
If an amount field is zero, it generally means that the field is blank. It is a requirement that for non zero amounts
that a linked currency field is populated with a valid currency. However, currencies for zero amounts are not
currently allowed. This extra validation is excessive and should be removed.
Component
Likely Impact
Incident No
Affected
GUI
Low
51128
The validation has been updated so that currencies are permitted for zero amounts.
Issue No
Description
Priority
DST-642
Cases not closed when using close when history
P2
Problem Reported
If a case has been created with Close when History turned on and then manual progression is used with an edit
event to set item to History, the case remains open.
Component
Likely Impact
Incident No
Affected
GUI
Low
40503
Close cases if case has "Close when History" on and manual progression is used to send an item to history.
7.3
63
SmartData Services
Issue No
SDS-265
Description
Add syst parameter for whether to highlight selected rows in
the grid.
Priority
P2
Problem Reported
WebConnect is being enhanced to support highlighting rows that have been selected by the selection mechanism
(WBC-1998). Need to add a system parameter, HIGHLIGHT_SELECTION, defaulting to true to support this.
Component
Likely Impact
Incident No
Affected
Metadata
63449

Was already present when branched
Issue No
Description
Priority
SDS-357
Support configurable custom date formats for WebConnect
P3
Problem Reported
A new syst parameter has been added for 2.7 'DATE_FORMAT'. To enable the custom formats in WebConnect
an entry should be added to the syst table with the following SQL: insert into syst
(syst_name,description,syst_title,syst_type,syst_string) values ('DATE_FORMAT','WebConnect - custom date
format','WebConnect - custom date format',1,' ') The custom date formats can then be set using SQL similar to
this: update syst set syst_string='en_GB=dd-MMM-yyyy,en_US=MMM-d-yy' where
syst_name='DATE_FORMAT'
Component
Likely Impact
Incident No
Affected
Database Schema
Low
102379
Added new SYST switch to static data (syst.csv)
Issue No
SDS-248
Description
Priority
Static data entries required for SYST for database specific IN,
P2
WHERE clause limits and BATCH size
Problem Reported
Static data entries required for SYST for database specific IN, WHERE clause limits and BATCH size. For
Oracle, they are as follows: Oracle_BATCH_limit|0|Oracle_BATCH_limit|01/01/1900|0|15|
|Oracle_BATCH_limit|-4|50 Oracle_IN_limit|0|Oracle_IN_limit|01/01/1900|0|15| |Oracle_IN_limit|-4|10
Oracle_WHERE_limit|0|Oracle_WHERE_limit|01/01/1900|0|15| |Oracle_WHERE_limit|-4|10 There is also
SQL Server, Sybase, and Db2 to consider. SQLServer_IN_limit SQLServer_WHERE_limit
SQLServer_BATCH_limit Sybase_IN_limit Sybase_WHERE_limit Sybase_BATCH_limit Db2_IN_limit
Db2_WHERE_limit Db2_BATCH_limit
Component
Likely Impact
Incident No
Affected
Services
Medium
H62355
Added database specific switches for in, where and batch
64
7.4
Recon Services
Issue No
RES-613
Description
Priority
Workflow server crashes when running multiple pass
initiations that contain a mixture of standalone edit events and P2
createdata events
Problem Reported
Workflow server crashes when running multiple pass initiations that contain a mixture of standalone edit events
and createdata events. The order of the events and passes need to be as follows to observe the crash: Within the
context of a single initiation Prior pass has an edit event as it's last event. Subsequent passes that do not fire
events do not impact replication Next pass that does fire events fires createdata event first In this scenario the
toolbox editevent code was attempting an invalid memory access.
Component
Likely Impact
Incident No
Affected
Toolbox
Low
62137
Ensure that order of events being fired does not cause workflow server to attempt an invalid internal memory
access. Specifically ensure that edit event in a previous pass followed by a create data event in a subsequent pass
does not attempt to access 'stale' internal workflow server memory.
Issue No
RES-671
Description
Gems reports memory allocation error when it is trying to
allocate zero bytes on an AIX O/S
Priority
P3
Problem Reported
Memory alloc error entity keys This comes from GEMS when it is trying to allocate a piece of memory in
preparation for attaching items to the initiation. In this case there are NO ITEMS and GEMS is therefore asking
the O/S for 0 bytes of memory. In most other environments this returns a pointer to an area of memory which
has no data and there are no issues. However on certain environments this has recently been found to return a
NULL pointer which does cause the above message to appear. The problem is in Gemsload.sc in the function
populateItemKeys(). The rest of the issues all occur because of the first issue. Extract from log below
======================= (I) Message:0 *** Started feed
/dtlm02/tlm/tlm1.2/var/ft/swift_out/20080506194438234237.SWF, KB FD_PURESWF Memory alloc error
entity keys Log file is not open UNABLE TO ATTACH ITEM LIST - NO ITEMS
======================= Customer comment below for ref only In the swift file, the Sequence B of
MT535 is not provided, so the NoOfItems is 0 in this case. Therefore we got the "Memory alloc error entity
keys" message in the log file. The error checking of the function calloc does not consider the case that
NoOfItems is 0 (or <0) the return can still be NULL.It should be a warning rather than an error.The log file is
misleading.
Component
Likely Impact
Incident No
Affected
Low
Stop allocation of memory when none is needed
H62794
65
Issue No
Description
Priority
RES-754
Limit the length of strings extracted from tag 86
P2
Problem Reported
There is a function in GEMS which takes information from tag 86 of an MT940 and maps it to various item
fields. There is no restriction on the length of the string extracted apart from the length of tag 86 itself. This can
lead to overflows when attempting to load the string to the item table.
Component
Likely Impact
Incident No
Affected
GEMS
63820

Check the length of the item columns being mapped. If the string is longer than the length permissible, then
restrict its length.
Issue No
RES-766
Description
Priority
In AAS an error in the stored procedure executing any extract
will have its error message truncated to four or eight
P2
characters
Problem Reported
When the stored procedure returns its error string to the RunExtractSP(char * pszRet) function we have code of
the following form: int RunExtractSP(char * pszRet) { call to stored proc here which returns string szRet
sprintf(gszTempStr,"%d:%s", iRet, szRet); strncpy(pszRet, gszTempStr, sizeof(pszRet)); return iRet; } Because
pszRet is a pointer to a character, sizeof(pszRet) is 4 or 8 bytes (machine dependent). Therefore pszRet will only
get the first 4 or 8 characters of szRet copied into it.
Component
Likely Impact
Incident No
Affected
Archive Server
64058
Change code so that it outputs the whole of the error message produced by the database in the extract phase of
any job.
Issue No
RES-792
Description
GMI - when header field asset code is populated but not item
asset code, gems isn't writing this from message header to
subfield_8 on item
Priority
P2
Problem Reported
When the header field asset code is populated but not item asset code, gems isn't writing this from the message
header to subfield_8 on item (item asset code). When both fields are populated, item.subfield_8 also gets
populated.
Component
Likely Impact
Incident No
Affected
GEMS
Copy header stock code to each of the items for messages loaded from GMI.
64541
66
Issue No
RES-803
Description
Priority
Allow 'Message Header' attribute to be viewable in dashboard
P3
grids
Problem Reported
The 'Message Header' attribute (attribute_id 457) should be given the Dashboard Views Displayable property
(property_id = 68). This will allow users to drill from Item rows into the associated Message-header record
when required. In particular, this will provide a work around for when a client wants to be able to search for
Message-Headers that link to items with specific amounts - they will be able to search for the items first & then
drill into the related header, rather than searching for both (as you could in SSR message maintenance).
Component
Likely Impact
Incident No
Affected
Database Schema
Low
100385
Modified static data recon.zs_attribute_sheet to add this property.
Issue No
Description
Priority
RES-804
Header Feed ID not being included in kb generation
P2
Problem Reported
Header_feed_id is not being included when a new generic kb is created, due to the presence of attribute property
45.
Component
Likely Impact
Incident No
Affected
51848
Fixed in previous versions - refdata carried over to 2.7
Issue No
RES-914
Description
When a message has no items GEMS does not check if it is a
duplicate
Priority
P2
Problem Reported
Duplicate pages loading into TLM 2.5 1. A statement page containing an opening and closing balance and
transactions is loaded into TLM. The closing balance is marked as final. 2. A second statement page arrives in
the same file for the same subaccount with the same statement number/page and has 0 opening and closing
balances and no transactions In TLM, the second page loads and causes a missing balance. SSR used to mark it
as a possible duplicate page and put it on the operator intervention queue.
Component
Likely Impact
Incident No
Affected
GEMS
Low
64600
Move duplicate page checking outside of check for items on the message
Issue No
RES-918
Description
Workflow rules which involve currencies are not working
correctly
67
Priority
P2
Problem Reported
It is in the operation of any workflow rule (which is in this case evaluated as part of the 'Release Workflow')
which has a RHS which involves a currency. For example, our rule in question has the following expression:
where abs net item position value less than or equal to '1 aud' What this rule will do is evaluate the net item
position value for the match group and take its absolute value. This will then be compared to 1 AUD. Now for
this comparison to take place the LHS and RHS have to be in the same currency. What the code does is convert
the RHS of this rule so that the '1 AUD' is replaced by an equivalent expression in the common curency (which
is either base or bank currency). In this case the common currency is bank currency for the set, which is XAU.
The conversion rate from XAU to AUD is to be found in the crat table: 1 base_currency = crat.rate X
crat.currency therefore 1 AUD = 0.00185 XAU This gets rounded to 3 dp, which means that the '1 AUD' part of
the rule is replaced with '0.002 XAU'. This can then be compared to the abs net of the item position value for the
group, which is also in XAU. For our group the abs net item position value is 0.75 XAU. Therefore this is
greater than 0.002 XAU, so we expect the rule to fail. However there is a bug where the common currency is not
defined before the workflow rules are read in by the call to read_match_lifecycle_rulelists(), which is done
inside proprule(). The common currency is actually defined inside load_items(), which comes later. Note that
pass quality rules are OK because they are read in after load_items() - only workflow rules are affected. This
bug means that the RHS side of the rule, instead of being convered from '1 AUD' into '0.002 XAU', becomes '1
XAU', causing incorrect evaluations of our groups against this rule.
Component
Likely Impact
Incident No
Affected
Workflow
Low
100282
Move the piece of code which reads in the common currency so that it comes before the reading in of the
workflow rules.
Issue No
RES-921
Description
Arcxport is creating and dropping tables once per chunk per
job. On Oracle this is creating a performance bottleneck.
Priority
P2
Problem Reported
The tables in question are as follows: ARC_TEMP_QD_1 ARC_TEMP_QD_2 ARC_TEMP_QD_3
ARC_TEMP_QD_4 ARC_TEMP_QD_5 ARC_TEMP_QD_6 The integer at the end of the table name
corresponds to the server instance number. We could reduce the number of times they are created and dropped.
At the moment they are created and dropped once per chunk per job. We could change this so that they are
created and dropped once per job, or even get each instance of advarc to create its table once at startup and drop
it when it closes down.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
63356
Change advarc and arcxport so that each instance of advarc will create and drop one table at startup and
shutdown respectively. Therefore instance 1 of advarc will create and drop table ARC_TEMP_QD_1 and so on.
Previously, each instance of arcxport (which is called by advarc) was creating and dropping one of these tables
once per chunk of each job - this could have been hundreds or thousands of times per job.
68
Issue No
RES-932
Description
Priority
The Audit Category is not correctly identifying groups which it
P2
may totally archive
Problem Reported
The Audit Category should be able to archive complete groups from the audit_trail if all that is left over after the
removal of orphans are unimportant rows. By unimportant we mean any rows which have event_type not in
(12,15,20,21,25). However, the current implementation is unable to spot such groups. This results in complete
groups not being archived when they should be. This has implications for the appearance of the audit_trail table
in an archive database, since we advise the use of the Audit Pass to transfer header rows to the archive database
after a Transaction Pass has been run with 'Include Audit Data' not ticked.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
100775
Modify the 'Audit' category so that it can correctly spot groups within the audit trail which may be completely
archived.
Issue No
Description
Priority
RES-966
AAS can purge more rows from netm than it extracted
P2
Problem Reported
This comes about because of a simple typo in the p_stla_PurgeMatch() stored procedure. The code currently has
IF @v_netm_extract > 0 BEGIN DELETE netm FROM arc_trns a, netm n WHERE a.corr_acc_no =
n.corr_acc_no AND a.sec_match_no = n.netm2 SELECT @v_count = @@ROWCOUNT EXEC
p_stla_UpdateRowcountPurge @p_job, 'netm', @v_count END where it should have IF @v_netm_extract > 0
BEGIN DELETE netm FROM #arc_trns a, netm n WHERE a.corr_acc_no = n.corr_acc_no AND
a.sec_match_no = n.netm2 SELECT @v_count = @@ROWCOUNT EXEC p_stla_UpdateRowcountPurge
@p_job, 'netm', @v_count END i.e. it uses arc_trns where it should be using #arc_trns. This bug means that the
purge will be deleting rows from netm which join to the whole of the arc_trns table - i.e. all rows from all jobs.
The #arc_trns table only contains rows from the current job and chunk.
Component
Likely Impact
Incident No
Affected
Low
100840
Replace arc_trns with #arc_trns in the p_stla_PurgeMatch() Sybase stored procedure
Issue No
RES-968
Description
If you have a very long list of workfolders, an Investigations
Category AAS extract job can fail with oracle error -6502
Priority
P2
Problem Reported
In TLM-3065 we made a change to advarc so that it could handle a list of workfolders which is longer than 4000
characters in length. The same change must also be made to the oracle stored procedures p_stl_ExtractCase()
and p_stl_DeleteCase().
Component
Likely Impact
Incident No
Affected
Archive Server
Low
100418
Increase the size of an array used by the oracle stored procedures to hold a list of workfolders.
Issue No
RES-969
69
Description
Priority
AAS fails to extract data for a Transaction' pass with 'Include
P2
Audit Data' and 'Investigation' ticked.
Problem Reported
The bug comes about when you have a 'Transaction' pass with 'Include Audit Data' and 'Investigation' ticked. If
it turns out that there are items to be extracted but no cases for those items, the code doesn't clear down an array
as it should do and it tries to insert the audit trail rows for the extracted items twice into arc_audit_trail. This
causes a primary key violation. The error message you get is something like: DoExtract szRet <1:ORA-00001:
unique constraint (.) violated <b>>
Component
Likely Impact
Incident No
Affected
Archive Server
Low
100418
Clear down array in code so that if there are no cases on extracted items in a 'Transaction' pass, no primary key
violation occurs in the arc_audit_trail table.
Issue No
Description
Priority
RES-970
Index created without specifying tablespace
P3
Problem Reported
The upgrade script TLM2100a.sql drops and re-creates the index for lifecycle_itemsixa but does not specify a
tablespace so it attempts to build it on the default tablespace (in this case users) which is too small and therefore
fails. An amendment should be made to the TLM2100a script so that it creates the index on the correct
tablespace.
Component
Likely Impact
Incident No
Affected
Database Schema
Low
101768
Added explicit table space to index.
70
Issue No
RES-1006
Description
Priority
Arcxport can fail to insert a row directly into an archive
database if the database has regional settings which mean that P2
the decimal point is a comma rather than a full-stop
Problem Reported
If arcxport is unable to insert a complete chunk of data into the archive database it has to do row-level inserts.
Each insert would be of the form insert into archive_xxxx (col1, col2, ..., colN) values (val1, val2, ..., valN) This
insert statement is in the form of a string which we put together ourselves., using data values selected back from
the database into a result set. The problem is that if the regional settings of the oracle database are such that
floating point numbers use a comma instead of a full-top to represent the decimal point, a number such as
1234.56 becomes 1234,56 which looks like two fields in the above insert statement. For oracle, the decimal
character is determined by the NLS_NUMERIC_CHARACTERS setting To make sure that we always use a
full-stop instead of a comma we need to do alter session set nls_numeric_characters = ". " Probably the best
place to do this would be in arcxport.init(), immediately after the call to dbconnect(): if (
dbconnect(strProg.szServerName, strProg.szDbName, strProg.szUserName, strProg.szPassword, 0) ==
FAILURE ) { fprintf(stdout, "FAILED TO CONNECT TO <%s> , <%s>\n", strProg.szServerName,
strProg.szDbName); exit(-12); } #ifdef ORACLE exec sql alter session set nls_numeric_characters = "."; #endif
This ensures that the change is only for the current session of arcxport.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
102364
To make sure that we always use a full-stop instead of a comma we need to do alter session set
nls_numeric_characters = ". " for each arcxport database session.
Issue No
RES-1016
Description
It is possible for two initiation events to use the same
workflow_list_id value
Priority
P2
Problem Reported
The error the customer is getting is as follows: RULE FAILED:NO INITIATION ITEM What is happening is
they have a scope rule which tries to make use of a 'Right Hand Side Initiation Attribute'. For this to work you
must have an attached item in the entity_list table, and theirs has been deleted. The deletion occurs because the
workflow server incorrectly inserts two rows in workflow_queue (with links to entity_list) with the same
workflow_list_id value (which equates to two groups on entity_list with the same list_id value, so they appear
as a single group). When the first job gets processed to completion by the workflow server it deletes all rows
from entity_list for its value of list_id - and this also deletes the items which are really for the second job. When
the second job is started we see the above error at the point the code looks for the (now missing) attached
item(s).
Component
Likely Impact
Incident No
Affected
Workflow
Low
101629
Fix bug in the workflow server which allows successive initiation events to have the same workflow_list_id
values.
71
Issue No
Description
Priority
RES-1022
Currency server does not load FIXed length data
P2
Problem Reported
If the following parameters are used in the Currency server then no data is loaded. 'CURRENCY_PARAM' sFIX -cp1 -cl3 -rp5 -rl15 -dp20 -dl30 -ep4 -el1 -vp50 -vl1 -fp51 -fl8 -dfYYYYMMDD This is because the data
was not being correctly split up.
Component
Likely Impact
Incident No
Affected
Low
104264
Split the data correctly when using the FIXed length parameters
Issue No
RES-1051
Description
Workflow crashes when there are two rows with same
stock_code, territory_code & +ve stock_id in stol
Priority
P3
Problem Reported
Stock aliases can be set up for ledger, statement or both sides. Workflow does not check the stol_type so it does
not distinguish between these values. If one has been set up for statement and one for ledger then Workflow
crashes because it was only expecting a single row. It needs to be changed to take the side of the item into
account Problem occurs in query at position SN_WORKFLOW_40 Note that just before this position in code
there is s call to set_side_sign(comflds.ls_type); This will set comflds.side (Ledger/Statement) that can be used
in changing the query to include selecting on stol.stol_type See SPR17584 and associated propose code for
details of how this was fixed in SSR 7640.
Component
Likely Impact
Incident No
Affected
Workflow
62177
Fixed as a side-effect of territory code enhancements.
Issue No
RES-1068
Description
GEMS errors if generic cash messages loaded with different
currencies
Priority
P2
Problem Reported
When a message_feed is created, a currency_header for the currency of the message_feed/account is generated.
When you load a message to a generic cash account, GEMS will create a curency_header for the currency of the
message if it does not exist. After two different currency_headers exist, GEMS will error on the next message
loaded to that message_feed as there will be two rows returned for a single variable (singleton select error),
when trying to determine the currency to use for the message.
Component
Likely Impact
Incident No
Affected
GEMS
Low
102865
Don't get the currency from currency_header but use the message currency or, if not specified, the bank
currency for calculations
72
Issue No
RES-1095
Description
The deletion of rows from match_queue_header can produce
on ora-1555 error on large databases
Priority
P2
Problem Reported
This concerns AAS when it is running the following SQL: DELETE match_queue_header WHERE (queue_id,
proposed_match_no, corr_acc_no) IN ( SELECT DISTINCT qd.queue_id, qd.proposed_match_no,
qd.corr_acc_no FROM arc_item ai, queue_detail qd WHERE qd.corr_acc_no = ai.corr_acc_no AND qd.gin =
ai.gin AND ai.job_number = :b1) They are getting oracle error ORA-1555 (snapshot too old). This happens
because the statement is not chunked-up, so the transaction can get arbitrarily large. The customer says that they
have 120 million rows on match_queue_header and 230 million rows on queue_detail. Why don't we do this in
chunks? The comment in the code says: "Unfortunately we cant do the MQH count on a chunk basis else we
end up counting QD items against a header more than once." This statement is true for the code which does the
extract, but it is not true for the code which does the deletion. If we have two items having the same (queue_id,
proposed_match_no) values but which are in different chunks, they will not cause the same row on
match_queue_header to be counted twice because the second deletion will have nothing to delete. Also, there is
no need to have a reference to match_queue_header.corr_acc_no in this statement, since it adds nothing.
Therefore we should move the statement back inside the chunk processing and modify it as follows: DELETE
match_queue_header WHERE (queue_id, proposed_match_no) IN ( SELECT DISTINCT qd.queue_id,
qd.proposed_match_no FROM arc_item ai, queue_detail qd WHERE qd.corr_acc_no = ai.corr_acc_no AND
qd.gin = ai.gin AND ai.job_number = :b1 and ai.chunk_number = Y) The original jira AAS-474 has been
retrofitted into the main code stream for the oracle stored procedure (in revision 1.103), but we have yet to do it
for Sybase and SQLServer. This jira is for AAS-474 to be retrofitted onto the AAS_TLM branch for Sybase and
SQLServer. The original changes for AAS-474 were as follows: Component Revision stl_advarc_package.sql
(oracle) 1.41.6.4 stl_advarc_procs.sql (sybase) 1.36.6.5 stl_advarc_procs.sql (sqlserver) 1.8.6.4
Component
Likely Impact
Incident No
Affected
Archive Server
100772
Modify delete statement so that its transaction is always bounded by the chunk size.
Issue No
RES-1107
Description
AAS fails to archive a NET item that was released [without
(and with) matching it against another item]. Therefore the
originating items are not archived
Priority
P2
Problem Reported
When archiving cash net items (items that are created when you match two items which do not net to zero) , the
Sybase and SQLServer versions of the AAS stored procedures do not work properly. This results in none of the
items (i.e. the net items or the items which were matched to produce the net items) in the net chain being
archived.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
104318
Fix the Sybase and SQLServer version of the AAS stored procedures so that cash net matches are correctly
archived.
Issue No
RES-1110
73
Description
Priority
In some circumstances existing case numbers may not be reset
P2
within workflow
Problem Reported
In the following circumstances, workflow can retain information on existing cases A group of positions items
are matched. A create case event is triggered. There is an existing case for the same case type & case amounts.
The case type has close when reraise flag set. Either the case type does not have reraise same stock set or some
other part of the workflow stops the case from being raised. In these circumstances, workflow may try to close
cases in error if the next case raised is a non-positions case. It may try to close the same case again for
subsequent non-positions cases until the next positions case resets the value.
Component
Likely Impact
Incident No
Affected
Toolbox
Low
105686
Ensure that the existing case number is reset in every path through the case create code
Issue No
RES-1132
Description
Priority
stlmqi_s on AIX not able to connect to a queue manager using
P2
the MQ server libraries
Problem Reported
stlmqi_s is able to connect to a queue manager using either the MQ server libraries (if installed) or the client
libraries. On AIX these libraries are as follows: server library: libmqm.a client library: libmqic.a The code for
stlmqi_s uses the unix dlopen() function to load the appropriate library at runtime, and we have given the wrong
name for the library to search for. We have "libmqm.a(mqm.o)" as the library to search for, where it should be
"libmqm.a(libmqm.o)".
Component
Likely Impact
Incident No
Affected
STLMQI
Low
104895
Change the code for stlmqi so that it can correctly find the MQ server library libmqm.a(libmqm.o) at runtime on
AIX.
Issue No
RES-1133
Description
Duplicate insert error when loading vabl records in a generic
sub-account
Priority
P2
Problem Reported
Occasionally when loading messages to a generic cash sub-account, GEMS exits with a duplicate insert error.
Component
Likely Impact
Incident No
Affected
GEMS
Low
106367
Clear out cached value balance information at the end of every message to force a reread of the value balance
dates
74
Issue No
RES-1136
Description
Cash value balances are not calculated in GEMS if
item.amount is zero
Priority
P3
Problem Reported
If there is a generic schema where the cash amount is put into a field other than item.amount then the value
balances may not be set up. This is happening because there is a check that item.amount is non-zero before
calling the vabl processing functions with the generic amount.
Component
Likely Impact
Incident No
Affected
GEMS
Low
104416
Change check to ensure generic amount is non-zero instead of item.amount.
Issue No
RES-1137
Description
Priority
If there are more than 20 edit (or population) events operating
P1
upon an item in a workflow, the workflow server can crash
Problem Reported
Code produces spurious messages in the logs of the form: WORKFLOW01 Thu Jun 4 14:15:09 2009
INSUFFICIENT MEMORY TO INCREASE ((*item_: ((*item_update_data)->item+itemPos)->editEventSize =
< WORKFLOW01 Thu Jun 4 14:15:09 2009 INSUFFICIENT MEMORY TO INCREASE ((*item_: 40> For
each item in the edit event the code checks to see if that item has been processed by any earlier edit events in the
workflow. If the item has been processed by an earlier edit event and this one is going to update a different
attribute, it is at this point where we check to see if we need to do a realloc to get more memory to hold more
edit events for the item. If we have already used 20 edit events (really 20 updates to distinct attributes), we need
to do a realloc. Because we are checking the wrong pointer, it is possible to think that the realloc fails when it
doesn't. This results in the edit event being aborted, and the next time we process an edit event the code can
crash.
Component
Likely Impact
Incident No
Affected
Workflow
Low
104773
Fix bug in code to make sure that when there are > 20 edit (or population) events in a workflow, the code does
not crash.
Issue No
RES-1144
75
Description
Priority
WebConnect should support the SSR approach to determining
P2
the lead item for a cash release
Problem Reported
Patch change onto HEAD. WebConnect should support the option of using the SSR approach to determining the
lead item for a cash release. This should be controlled by a SYST switch (defaulting to the existing TLM Online
approach). The existing TLM online approach is to use the largest single item as the lead item. The approach
used in SSR is as follows: 1. Accumulate the absolute amounts for the ledger-side and the statement-side for all
items in the match. 2. Determine which side (ledger or statement) has the largest absolute amount. 3. Use the
lead item (i.e. item with largest amount) from that side.
Component
Likely Impact
Incident No
Affected
Database Schema
Low
104944
The WebConnect release tool has been modified so that the setting of a SYST switch (NET_ITEM_SIDE_SSR)
will cause WebConnect to use the SSR method to determine the lead item in the release group (and therefore net
item type). The SSR method is as follows: 1. Accumulate the absolute amounts for the ledger-side and the
statement-side for all items in the match. 2. Determine which side (ledger or statement) has the largest absolute
amount. 3. Use the lead item (i.e. item with largest amount) from that side. The existing TLM online approach is
to use the largest single item as the lead item. This will still be the default setting.
Issue No
RES-1145
Description
Allow the users to recall net matches if the net item produced
is still outstanding, but has seen other activity.
Priority
P2
Problem Reported
One of the issues for customer is the inability to recall net matches if the net item produced is still outstanding,
but has seen other activity. In 2.6 we would have the option of the do-not-audit flag, but that is not available in
2.5SP1. This task is to build some switchable logic (i.e. SYST switch controlled) into Recall, so that in the
situation where it knows it is recalling a Cash net match, it will only check the 'flag_2' status of the associated
items (i.e. 'history' for the matched items and 'outstanding' for the created net item) instead of checking the
'event_group_id'. This way, the match can be recalled even if the net item has been edited or processed through
a workflow tool, as long as it is still outstanding.
Component
Likely Impact
Incident No
Affected
Database Schema
Low
104944
A new SYST switch has been added to WebConnect that allows users to override the net item audit checks. If
the SYST switch (ALWAYS_RECALL_NET) is switched on then the cash release recall process will ignore
any subsequent audited actions on a net item created from the match. As long as the net item is still outstanding,
the match will be recalled.
Issue No
Description
Priority
RES-1149
GEMS can crash if it finds a space in a security code
P2
Problem Reported
If there's a space in a security code at the fifth position and the rest of the security code is less than 12 characters
long then GEMS can crash
Component
Likely Impact
Incident No
Affected
GEMS
Low
106293
Check string long enough before trying to process the twelfth character
76
Issue No
RES-1158
Description
It is possible to get two different negative stock_ids for the
same stock
Priority
P2
Problem Reported
"Unknown stocks are loading with a different stock_id to existing stock_ids. Customer doesn't use aliasing, all
stocks remain unknown, but if the stock exists it should be matched with that stock_id."
Component
Likely Impact
Incident No
Affected
GEMS
Low
100165
"Modify transaction handling when creating stocks"
Issue No
RES-1163
Description
Priority
AAS can get a primary key violation when running a
Transaction pass if there are any matches which have non-zero P2
sec_match_no
Problem Reported
The customer data has securities inheritance matches which means that you can have more than one match
sharing the same sec_match_no. This brings with it the possibility that the same item can get extracted twice.
There is some code which is supposed to spot any such duplicates and remove them but this code is failing,
resulting in the duplicates making it through to the arc_item table. This causes a primary key violation and so
the code crashes. The duplicate check fails because it uses a binary chop routine which assumes that the data is
ordered. It turns out that this assumption is false, so the algorithm fails. The fix is to replace the binary chop
algorithm with a simpler linear one, but only to actually check for duplicates when sec_match_no > 0. Since this
is relatively rare in most cases the use of the slower linear search should be more than offset by the fact that we
don't have to do it at all most of the time.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
102993
Change AAS stored procedure so that it really does remove duplicate extracted items before trying to insert
them into the arc_item table.
Issue No
RES-1166
Description
AAS fails to extract data when running an Audit pass on
oracle because the group being archived has many (>~ 10,000
rows) in it
Priority
P2
Problem Reported
Inside the code which handles the extract and delete jobs for an Audit pass, there is code which puts together a
string which either contains a NOT IN() or an IN() clause. In both cases if there are many rows in the audit_trail
group being archived, this clause may have more than 1000 terms in it. There is a limit of 1000 expressions in
any IN() clause in Oracle (at least in 10g), so we must make sure we never hit this limit. Also, the string
containing the SQL can have a maximum size of 32767 characters, so we must also make sure that we do not
exceed this length.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
103775
Make sure that the IN() or NOT IN() clause being used by the code is limited to 1000 expressions, and that the
string containing the SQL is limited to 32767 characters.
Issue No
RES-1176
Description
GEMS copies stock_code to all items on a MT536 but it only
copies the stock description for productised schemas
77
Priority
P2
Problem Reported
In an MT536 message the stock information is held at the message level. In productised messages, both the
stock code and the stock description are copied to all items. In generic messages only the stock_code is copied
Component
Likely Impact
Incident No
Affected
GEMS
64702
Copy the stock description as well as the stock code for generic messages
Issue No
RES-1177
Description
Priority
Gems fails to map all data from a feed file using kb mapping
'as "%[^\0]" if the column data contains the characters @ % ^
P2
or [. These characters are not mapped in to the system and all
data after them is also not mapped.
Problem Reported
Gems fails to map all data from a feed file using kb mapping 'as "%[^\0]" if the column data contains the
characters @ % ^ or [. These characters are not mapped in to the system and all data after them is also not
mapped. Problem needs fixing in gems in two places: gemskit.sc HandleSpecialChars() Here we need to catch
any instances of format %[^\0] and replace with %[^\001] before the main part of the function that replaces
these escape character sequences. gems.sc SplitFields() This needs to modify the line that generates the format
specifier TmpFormat variable to use the same octal escaped non printing character as above (i.e. \001).
Therefore line sprintf(TmpFormat, "%s%s%c]", Field[FieldIdx].As[i], "%[^", GemsChar); becomes
sprintf(TmpFormat, "%s%s%c]", Field[FieldIdx].As[i], "%[^", '\001' );
Component
Likely Impact
Incident No
Affected
GEMS
Medium
59546
Ensure gems can load data fields that contain characters @, %, [ and ^. Previous operation truncated the data at
when encountering one of these characters
Issue No
Description
Priority
RES-1178
Always populate number of items on a message as in SSR
P2
Problem Reported
Original Enhancement Request: A Message Maintenance dashboard has been built but the functionality is
different to that of SSR. Can a view be built that would include the following user's request: (3) We need to
have the function to be able to view details lines on all pages (or a selection of ) in one view. The currently
functionality will only let us view detailed lines on specific selected rows. This is not considered practical as it
mixes information from different universes. The fallback position is to ensure that number of parts is always
populated correctly on message_header so that the customer can see if there are any items on the message
Component
Likely Impact
Incident No
Affected
GEMS
Low
63686
Ensure number of parts is always set even if the message goes to Operator Intervention because of an early error
78
Issue No
RES-1187
Description
Priority
The delete job on oracle for a Transactions category job which
is archiving 'Not matched' items is only deleting the first chunk P2
of data
Problem Reported
Inside the p_stl_DeleteItem() stored procedure for oracle we have the variable v_item_row never being reset
after the first chunk has been processed. This results in the WHILE v_item_row < ITEM_BANK_TAB.LAST
LOOP test immediately exiting for any chunk other than the first one. This causes only one chunk's worth of
data to be loaded into the ARC_ITEM_TAB array, and from there into the arc_item table, which is used to do
the join to the item table to delete the data.
Component
Likely Impact
Incident No
Affected
Low
100600
Reset the v_item_row variable to make sure that all chunks of data are deleted from the job.
Issue No
RES-1189
Description
arcxport can put together a badly-formed piece of SQL when
dealing with the note table
Priority
P2
Problem Reported
The SQL being put together by arcxport is as follows: insert into archive_note
(corr_acc_no,gin,datetime,note_type,seq,match_no,note_code,notetext,notetext_2,notetext_3,notetext_4,user_id
,user_id1) values (100005853,43,'28/12/2007 11:55:tool01',3,1,0,'','testing workflow tool','','','','IIMCOB','')
Server: Msg 241, Level 16, State 1, Line 1 Syntax error converting datetime from character string. From this we
can see that there is a date field which says '28/12/2007 11:55:tool01', and this is clearly invalid.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
104800
There is an uninitialised char[512] variable in the code, and this is probably the cause of the error. This variable
should be initialised (set to blank) each time it is used.
Issue No
RES-1192
79
Description
Priority
Jobs in AAS are not clearing up data from the arc_xxxx tables
P2
once they have been purged
Problem Reported
When an job in AAS has been both extracted and purged, AAS is supposed to remove any rows from the
arc_xxxx tables for that job. To identify jobs which it can clear up it uses the following cursor select
arc_queue.job_number,category,investigations_flag,lock_flg,audit_purge from arc_queue,arc_can where
status=20 and (lock_flg = 0 or lock_flg = :iserver_lock) and arc_queue.job_number=arc_can.job_number The
problem here is that at the end of the extract phase there is a bug which prevents the required row from being
inserted into the arc_can table, so the above cursor finds no jobs to clear up. The bug which causes this is at the
end of the DoExtract() function, where the following function call: iRet = IfSuspend(); overwrites the iRet
variable, which makes the code behave incorrectly. In particular, it does not call the function CreateArcCan() to
create the row in arc_can for the job. The fix is to make the iRet variable not depend on the result of the call to
IfSuspend(), although we must handle the return value from IfSuspend() appropriately. This code is there to
handle what happens if the user has manually set a job to 'suspend' or 'abort' when the extract was running. If
this is the case, the job does not move onto the next phase, it should be set to 'suspended' or 'aborted' as
appropriate.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
104637
Fix code which is there to handle what happens if the user has manually set the job to 'suspend' or 'abort' when
the extract was running.
Issue No
RES-1201
Description
Priority
A match group consisting only of ls_type of (180, 190, 179, 191)
may find the same unresolved or exported case via the stock_id
P2
of the lead item and via the individual items in the match. If
this is so we get an error if the same case is closed twice.
Problem Reported
We are talking about the case_resolve() function in eventproc.sc in the TLM2.100 code stream. We are calling
case_resolve and the iCase variable is zero. We have a match group which consists entirely of ls_type = 180 and
190 items. As far as I can tell, this means that the posonly variable evaluates to true. Therefore what happens is
we try to find all cases given by the resolve_hold_case cursor: Immediately after this we try to find all cases
which involved the individual items in the match group, using the resolve_item_case cursor: Any cases which
are found by these cursors are loaded into separate arrays which are later stepped through and the cases
resolved. The problem seems to be that we are getting the same case being found by both of these cursors, and
this causes the resolve_one_case() function to fail when it tries to resolve the same case a second time.
Component
Likely Impact
Incident No
Affected
Workflow
Low
61751
Failing to resolve a particular case because it is already resolved is not a failure - maybe, rather than failing
because it can't find the unresolved case it should read the case, including the status, & just return success if it is
already resolved - only fail if it fails to find the case at all.
80
Issue No
RES-1202
Description
SQL Error -207 AT 1414 ErrorText<Invalid column name
'do_not_audit'.>|
Priority
P2
Problem Reported
1 running a Static pass called Static_test (all tables direct to Archive DB) ARCXPORT01 Tue Nov 04 14:30:32
2008 : No rows inserted into table #arc_keys from table entt| ARCXPORT01 Tue Nov 04 14:30:32 2008 : Start
of exportStaticTableToDatabase ARCXPORT01 Tue Nov 04 14:30:32 2008 : About to process table
EVENT_DETAIL| ARCXPORT01 Tue Nov 04 14:30:32 2008 : szColumnList =
event_id,attribute_id,data_string1,data ARCXPORT01 Tue Nov 04 14:30:32 2008 :
_string2,event_desc,event_name,event_type,object_id,do ARCXPORT01 Tue Nov 04 14:30:32 2008 :
_not_audit| ARCXPORT01 Tue Nov 04 14:30:32 2008 : Dropped table #arc_keys| ARCXPORT01 Tue Nov 04
14:30:32 2008 : Loaded 29 rows into table #arc_keys from table event_d ARCXPORT01 Tue Nov 04 14:30:32
2008 : etail| ARCXPORT01 Tue Nov 04 14:30:32 2008 : Loaded 29 rows into table #arc_chunk for table
event_d ARCXPORT01 Tue Nov 04 14:30:32 2008 : etail| ARCXPORT01 Tue Nov 04 14:30:32 2008 :
Executing query delete archive_event_detail from archi ARCXPORT01 Tue Nov 04 14:30:32 2008 :
ve_event_detail arc, #arc_chunk loc where arc.event_id ARCXPORT01 Tue Nov 04 14:30:32 2008 : =
loc.event_id| ARCXPORT01 Tue Nov 04 14:30:32 2008 : 27 duplicate rows deleted from table
archive_event_det ARCXPORT01 Tue Nov 04 14:30:32 2008 : ail| ARCXPORT01 Tue Nov 04 14:30:32 2008
: Executing query insert into archive_event_detail (even ARCXPORT01 Tue Nov 04 14:30:32 2008 :
t_id,attribute_id,data_string1,data_string2,event_desc ARCXPORT01 Tue Nov 04 14:30:32 2008 :
,event_name,event_type,object_id,do_not_audit) (select ARCXPORT01 Tue Nov 04 14:30:32 2008 :
loc.event_id,loc.attribute_id,loc.data_string1,loc.da ARCXPORT01 Tue Nov 04 14:30:32 2008 :
ta_string2,loc.event_desc,loc.event_name,loc.event_typ ARCXPORT01 Tue Nov 04 14:30:32 2008 :
e,loc.object_id,loc.do_not_audit from event_detail loc ARCXPORT01 Tue Nov 04 14:30:32 2008 : ,
#arc_chunk arc where arc.event_id = loc.event_id)| ARCXPORT01 Tue Nov 04 14:30:32 2008 : SQL Error 207 AT 1414 ErrorText<Invalid column name ' ARCXPORT01 Tue Nov 04 14:30:32 2008 : do_not_audit'.>|
Component
Likely Impact
Incident No
Affected
Archive Server
Low
106230
Modify archive_views script for Oracle and SQLServer so that archive_event_detail view includes the
do_not_audit column
Issue No
RES-1203
Description
AAS can cause a primary key violation in the IAMT table
when doing a purge or a delete
Priority
P2
Problem Reported
If more than one job extracts the same item (undesirable but perfectly possible), you can get a primary key
violation in the IAMT table when that item is purged or deleted by the second of these jobs. This is because the
code does not check that the item has already been deleted before doing the insert into IAMT.
Component
Likely Impact
Incident No
Affected
Archive Server
Low
106362
Only do an insert into the IAMT table when an item is actually being deleted.
Issue No
RES-1204
Description
If gems locks the bank table it is possible for the workflow
server to break the primary key on workflow_queue
81
Priority
P2
Problem Reported
ABORTED-SQLCODE -1 AT 92 ErrText = ORA-0: ORA-00001: unique constraint
(TLMDBO.WORKFLOW_QUEUE_IND_KEY) violated| For the primary key violation on workflow to occur
we need the following: 1. Gems submits a job to workflow_queue with a lock_flg of 0. 2. Server instance N
picks up the job and sets its lock_flg to 100+N. 2. While the first job has a status of 100+N gems submits a
second identical job to the workflow_queue with a lock_flg of 0. 3. Then, the first job goes to 500+N because
gems has locked bank for the account. 4. Workflow starts to process the second job so sets its lock_flg to
100+N. 5. Gems still has bank locked for the account so workflow tries to set lock_flg for the second job to
500+N and we get a primary key violation.
Component
Likely Impact
Incident No
Affected
Workflow
Low
63745
If workflow instance N is about to set lock_flg of a job to 500+N on workflow_queue, it should check to see if
there is an identical row already there. If there is, the second job should be deleted.
Issue No
RES-1207
Description
Pre-match aggregation in propose not coping correctly with
multiple grouping columns
Priority
P2
Problem Reported
The pre-match aggregation logic in propose is only ever using a single grouping column even if multiple
grouping columns have been defined. The logic is storing all the grouping data, but it allocates a new group-ref
array element each time (instead of concatenating the data) & then points the reference array to the last element,
losing the linkage to data from previous grouping columns for the same item.
Component
Likely Impact
Incident No
Affected
Workflow
Low
100341
Modify workflow code so it can correctly handle more than one grouping (non-matching) column within an
aggregate population row in a pass.
Issue No
Description
Priority
RES-1208
Aggregation of dates in populations isn't working
P2
Problem Reported
If you have a population in a pass which is an aggregate population and the column to aggregate on is a date,
you should be able to perform the following operations: COUNT MAX MIN PRINCIPAL There is a bug in the
code which means that even though the aggregation will be done, the result will not be substituted back into the
reference array.
Component
Likely Impact
Incident No
Affected
Workflow
Low
100341
Fix workflow code so that aggregation can be preformed upon date fields within aggregate-type pass
populations.
82
Issue No
RES-1210
Description
The workflow server fails if you have a reference mask
attached to a grouping column
Priority
P2
Problem Reported
The verbose logs show the following: <16:01:27.075:0> Combined Reference exceeds overall length <data
removed> The reference mask just extracts the first 10 characters from the reference. We can see that they are
using a reference mask on a grouping column. The mask will not produce multiple references. The fact that we
weren't incrementing this counter meant that we were always adding the reference to the same element of the
(grouprefarr+giGroupInd)->combref The structure was overfilling.
Component
Likely Impact
Incident No
Affected
Workflow
Low
103687
Increment counter in code to denote that a grouping column is in use, even when reference masks are being used
on that grouping column.
Issue No
RES-1220
Description
Priority
Productised cash accounts with redenominated currencies are
P2
producing balance mismatch errors
Problem Reported
If a message comes in on a productised cash account with redenominated currency, then GEMS is putting the
wrong currency on the balances. This was introduced in 2.6SP1 patch 9.
Component
Likely Impact
Incident No
Affected
Low
106389
Re-instate check for existing currency_header currency which was removed as part of earlier patch but put
check round it so it is only called for productised cash sub-accounts, instead of all cash sub-accounts
Issue No
RES-972
Description
Implement delayed initiations via the workflow_queue table
directly instead of going via job_schedule and using the
schedule server
Priority
P3
Problem Reported
In SPR49023 we implemented a solution which would allow initiations called by gems to be delayed by a userconfigurable amount of time. The solution involved gems inserting a row into the job_schedule table which
specified when the initiation was to be processed. At this time the schedule server would insert the job into
workflow_queue for the workflow server to process. Certain difficulties with this approach have since arisen, as
described in H62794 and H62900, leading to the following proposed solution: We will add a new column called
proposal_time to the workflow_queue table. The workflow server will henceforth only process jobs which have
a proposal_time which is blank or in the past. When gems is processing a delayed initiation it inserts the job
directly into workflow_queue, with proposal_time being equal to the current time plus the required delay. All
other functionality to do with gems firing automatic proposal of jobs is maintained with this new solution.
Component
Likely Impact
Incident No
Affected
GEMS
62900
We will add a new column called proposal_time to the workflow_queue table. The workflow server will
henceforth only process jobs which have a proposal_time which is blank or in the past. When gems is
processing a delayed initiation it inserts the job directly into workflow_queue, with proposal_time being equal
to the current time plus the required delay.
Issue No
RES-1015
Description
summary interaction
83
Priority
P3
Problem Reported
This will be driven by a new syst switch. EDIT_NET_VALUE_DATE Default to 1 (true).
Component
Likely Impact
Incident No
Affected
Database Schema
Low
104327
Added syst flag.
Issue No
Description
Priority
RES-1029
Modified indexes required on vadj
P2
Problem Reported
Performance problem with Currency Value Adjusted Balances dashboard requires new index on vadj. index
changes required amount to: ALTER TABLE VADJ DROP CONSTRAINT VADJ_IND_KEY; DROP INDEX
VADJ_IND_KEY; ALTER TABLE vadj ADD CONSTRAINT vadj_ind_key PRIMARY KEY (corr_acc_no,
value_date, gin) USING INDEX TABLESPACE tlm_index; CREATE INDEX vadjixa ON vadj (corr_acc_no,
short_no, vtype, value_date, currency) TABLESPACE tlm_index;
Component
Likely Impact
Incident No
Affected
Low
103683
Indexes altered on vadj and eadj
Issue No
RES-1032
Description
summary interaction
Priority
P3
Problem Reported
This will be driven by a new syst switch. EDIT_NET_VALUE_DATE Default to 1 (true).
Component
Likely Impact
Incident No
Affected
Database Schema
Low
104327
Added syst flag.
84
Issue No
RES-1049
Description
Add a new SYST setting to set a maximum number of Trial
Balance sets
Priority
P3
Problem Reported
Add the following SYST setting to the Smart Data: INSERT INTO syst (syst_name, syst_value, syst_mtype,
description, syst_title, syst_type) VALUES ('TRIAL_BAL_SET_LIMIT', 1000, 3, 'Maximum allowed accounts
in a Trial Balance search', 'Trial Balance set search limit', -4)
Component
Likely Impact
Incident No
Affected
Low
103428
A maximum number of sets can be specified in the new SYST setting: 'Trial Balance set search limit'. The
default value is 1000. If the SYST value is missing then it is unrestricted. If a Trial Balance search will be
calculating Trial Differences for more accounts that the maximum (even if some sets are subsequently filtered
out), then the user will be prompted to change the search criteria. This prevents excessively large searches being
run that will harm the application server performance.
Issue No
Description
Priority
RES-1054
Enh to GEMS for ISIN and field 35:
P2
Problem Reported
CUSTOMER ISSUE: We're having some problems in the load of swift files for securities positions. The
problem comes when the field :35B: contains errors in the file. This is a well-formed :35B: field :35B:ISIN
PTSMCAOE0000 SOMEC/94 :90B: [...] GEMS checks that there is a blank on 5th position on the field an loads
the next 12 chars (PTSMCAOE0000) on sfield_8 of database (ISIN). Then loads the following line on sfield_9
(ISIN description), all OK. sfield_8 = PTSMCAOE0000 sfield_9 = SOMEC/94 Now, this is what happens when
we receive a wrong file: :35B:SGO-SANTOS GUIM. OLIVEIRA :90B: [...] There is no ISIN, we receive the
description on :35B: and GEMS loads it on sfield_8. We think that GEMS should left sfield_8 with blank
instead of taking the description like an ISIN. It also loads the same on sfield_9 as description. sfield_8 = SGOSANTOS GUIM. OLIVEIRA sfield_9 = SGO-SANTOS GUIM. OLIVEIRA Another example, we receive a
file with the next: :35B:DOWA HOLDINGS CO.,LTD.SHARE SUBSCRI PTION RIGHT
(COUNTRY:JAPAN ) :90B: [...] In this case GEMS loads HOLDINGS CO. on sfield_8, we suppose that in this
case GEMS checks that there is a blank on 5th position and takes the next 12 chars as the ISIN. Then loads the
next two lines on sfield_9 as a description. Once again we think that GEMS should left the ISIN with blank as
there is no word "ISIN" on the field. sfield_8 = HOLDINGS CO. sfield_9 = PTION RIGHT
(COUNTRY:JAPAN ) Line of the file host affected: invswift
local:/opt/apps/cdc/tlm/var/ft/in/TITULOS_INVESTMENT invswift.trg:static norm BSCH_Ref_Internal
/opt/apps/cdc/tlm/var/ft/hold/TITULOS_INVESTMENT GEMS FD_PURESWF_MapISOSec nocr
tlmdbo@dtlmr/dbodes:
Component
Likely Impact
Incident No
Affected
GEMS
Low
104223
If msghdr.free_int is set to 1 (using split into If msghdr.free_int as "@1" in the kb file) then the stock code
mapping functions will look for specifically "ISIN " at the beginning of the the stock code line, instead of
looking for any four characters followed by a space
Issue No
RES-1173
Description
There are several ways in which the workflow server can exit
from the proprule() function with a -1 return value. We need
to distinguish between these.
85
Priority
P2
Problem Reported
There are several ways for the proprule to exit with a -1 return value. When this happens we always get a
message in the logfile of the form: BAD RETURN FROM PROPRULE: Account<xxxxxxxxx> h_return<-1>
We need to be able to say exactly which condition produced the error. To do this, simply make sure that all
conditions which produce this error always put something in the log. There are essentially only two mechanisms
which need to have this done - bank being locked, and workflow_queue not updatable.
Component
Likely Impact
Incident No
Affected
Workflow
Low
102385
Modify workflow code so that it outputs additional information about a common error message in the logs.
Issue No
RES-1174
Description
Add new functionality to bb.sc to output the contents of the
schema if there is a failure in the get_object_id() function
Priority
P2
Problem Reported
We have a customer who is getting many occurrences of the following error message in the upper-case
workflow logs: WORKSP0111 Mon Jan 5 11:04:32 2009 ERROR RETRIEVING OBJECT ID. : Pass <10050>
Pop <1> Item Gin <5441721> ls_type <90> WORKSP0111 Mon Jan 5 11:04:32 2009 BAD RETURN FROM
PROPRULE: Account<100000126> h_return<1> We have not been able to diagnose the cause of the error so
we have decided to add some new functionality to bb.sc which calls the existing function output_bb() whenever
there is an error inside get_object_id(). This function will output all schema-related arrays currently help in
memory.
Component
Likely Impact
Incident No
Affected
Toolbox
Low
102513
Add new code out output all schema-related data in memory at the time an error occurs in the get_object_id()
function.
Issue No
RES-1175
Description
Server Manager does not handle spaces in the default
installation path
Priority
P2
Problem Reported
The default installation folder is now specified as C:\Program Files\ etc The space causes the file C:\program to
be created in root directory. This causes Windows and Server Manager many problems when restarting or using
some of the Windows Services.
Component
Likely Impact
Incident No
Affected
Server Manager
Low
60254
N/A - Issues were already fixed in TLM2.6 under SDS-41
86
Issue No
RES-1185
Description
Default case counterparty to counterparty of lead item when
no extended customer data
Priority
P2
Problem Reported
When a case is created, default the case counterparty to match the counterparty on the lead item when there is no
customer extended data present. If there is cust_data, use the counterparty information from this instead.
Component
Likely Impact
Incident No
Affected
Toolbox
Low
61504
Set the counterparty to match the item counterparty and overwrite with customer extended data if present on a
third party case.
Issue No
RES-1188
Description
Priority
Edit components can be processed in an order which is
different to the order in which they are displayed on screen in P2
the edit event.
Problem Reported
The edit components for an edit event aren't being processed in the correct order. The first component is the one
involving filter 'VR-FNMA LOAN', which has id = 10014. The log shows that we are processing filter 10015
first, and this is filter 'VR-SERVICER LOAN', which is associated with the second component. If we run the
following SQL to see which edit components are associated with population event 10312, we get: select
olk.key_type, olk.object_list_id, ol.id, ec.item_filter_id, operator, position, source_attribute from
object_list_key olk, object_list ol, edit_component ec where olk.object_list_id = ol.object_list_id and ol.id =
ec.id and olk.object_list_role = 33 and olk.key_value in (10312) order by olk.key_value; which gives us
KEY_TYPE OBJECT_LIST_ID ID ITEM_FILTER_ID OPERATOR POSITION SOURCE_ATTRIBUTE ------------------------------- -------------- ---------- -------------- ---------- ---------- ---------------EDIT_EVENT_COMPONENT_LIST 15815 11348 10015 2286 2 5163 EDIT_EVENT_COMPONENT_LIST
15815 11349 10014 2287 1 5163 So even though the components list a position for each one, they seem to be
processed in order of ol.id rather than position. The logfile bears this out: <16:53:15.176:0> PROCESSING
EDIT EVENT: id = 10312 <16:53:15.176:0> In read_lists for role <33> <16:53:15.176:0> In add_new_list Index = <0> <16:53:15.176:0> Input List <15815> Key1 <10312> Key2 <0> Key3 <0> <16:53:15.176:0>
Array pointer is NULL <16:53:15.176:0> List <15815> added. Role <33> Key1 <10312> Key2 <0> Key3 <0>
<16:53:15.177:0> Get properties for list <15815> <16:53:15.177:0> List <15815> - First element - List
<15815> ID <11348> - No of elements <2> <16:53:15.177:0> Ordered list of lists (Role <33>)
<16:53:15.177:0> List <15815> Sequence No <99> Therefore what happens is we process the second
component first, followed by the first. The component which is actually processed first will always use
OP_EQUALS as its operator, since there is no prior component to supply the operator. Our problem is that the
second component to be processed takes its operator from the first component to be processed. In our case, the
first component to be processed is the second component as it appears in the event, and this has an operator of +
by default. It looks like this data was produced by CI having done an import of a workflow which was setup
somewhere alse. Whenever you create an edit event from scratch theh components seems to be ordered in the
same sense as object_list.id. Steve Flower said: We do need workflow processing to be able to process the
components in the same order that the user sees them on screen. The only really safe way to do this will be to
use the position to order the components - so I think workflow will need to change the way it reads the data,
though I think that is going to be a messy little change inside the list-reading routines.
Component
Likely Impact
Incident No
Affected
Workflow
Low
62157
Change the workflow/toolbox code so that the workflow server always processes edit components in the same
order as how they are displayed onscreen in the edit event.
Issue No
RES-1198
Description
Implement delayed initiations via the workflow_queue table
directly instead of going via job_schedule and using the
schedule server
87
Priority
P2
Problem Reported
Additional work required for delayed initiations. We will add a new column called proposal_time to the
workflow_queue table. The workflow server will henceforth only process jobs which have a proposal_time
which is blank or in the past. When gems is processing a delayed initiation it inserts the job directly into
workflow_queue, with proposal_time being equal to the current time plus the required delay. All other
functionality to do with gems firing automatic proposal of jobs is maintained with this new solution.
Component
Likely Impact
Incident No
Affected
GEMS
Low
62900
We will add a new column called proposal_time to the workflow_queue table. The workflow server will
henceforth only process jobs which have a proposal_time which is blank or in the past. When gems is
processing a delayed initiation it inserts the job directly into workflow_queue, with proposal_time being equal
to the current time plus the required delay.
Issue No
RES-1209
Description
Workflow engine's processing order is based on priority and
corr_acc_no. It should use the workflow propose time field to
allow for FIFO (first in, first out) processing
Priority
P2
Problem Reported
Enhancement for workflow processing to have workflow leverage the workflow propose time field to allow for
FIFO (first in, first out) processing, instead of processing by corr_acc_no. This should be the same whether the
data is automatically submitted or manually submitted for proposal.
Component
Likely Impact
Incident No
Affected
Workflow
Low
100111
At present the ordering criteria for jobs to be selected from workflow_queue is by lock_flg desc, priority,
corr_acc_no. This will be changed to lock_flg desc, priority, proposal_time asc
88
Issue No
RES-1169
Description
Enhancement Request for a new KB function to multiple the
original value by 100
Priority
P2
Problem Reported
PS would like to propose a simple solution for 8 decimal place matching without changing the global setting.
Basically, a factor (:92A::CUFC) is a number between 0 and 1. If this number is multiplied by 100, then we will
get a new number between 0 and 100, but only up to 6 decimal places. This new number could used for
matching/calculation/comparison and give the same matching output. The only thing we need is that
Development provide a very simple KB function that return the original amount times 100. Then GEMS could
call this KB function to convert the original amount to a new value and store the new value (up to 6 decimal
places) in an amount field while loading.
Component
Likely Impact
Incident No
Affected
GEMS
Low
104537
Add a new function Gms_MultiplyByFloat. This will multiply the value passed in by the value in
msghdr.free_float. The way to use this is to put a default value into msghdr.free_float and then map the value
required, calling the function. For example split into msghdr.free_float as "@100", item.amount_17 as "%lf"
using Gms_MultiplyByFloat
Issue No
RES-1183
Description
Could it be possible into AAS 3.2 adding a new "Date" for a
Transaction Pass for match type "Not Matched" to filter the
items to archive?
Priority
P2
Problem Reported
The problem is the following one: If we create a Transaction Pass for Matched Items, the system checks for the
trns.match_date and then goes through the items associated to every match selected in order to choose the data
that can be archived or not. The Client for several products is not using queues to match items, when a match is
generated only the match_no (set as the max(gin) ) is updated into the item table. That means they won't have
any entry into the table trns for those matches, that doesn't allow the possibility to archive those products
filtering for matching date. The only way in that case is to create a Transaction Pass with a "Not Matched"
match type, using the System Entry Date or the Statement Date at Item Level, that avoids the possibility to
archive for matched groups. For Example: Item1 : sys_entry_date = 20-10-2008, Match_no= 200 ,flag_2=1
Item2 : sys_entry_date = 20-02-2009, Match_no= 200, flag_2=1 Transaction Pass with a Date Range based on a
sys_entry_date into a Range from 20-09-2008 to 20-01-2009. If we run a job associated to the Transaction Pass
above on 22-02-2009, it will only archive item 1 and will keep item 2 on the Active DB. Could it be possible
into AAS 3.2 adding a new "Date" for a Transaction Pass for match type "Not Matched" to filter the items to
archive? Could it be possible to obtain it by changing the Stored Procedure (i.e. "p_stla_ExtractItem") or does it
have any other impact? As general question, in order to put some others criteria for archiving or changing the
existing ones, could it be possible by changing the stored procedures provided for the AAS system?
Component
Likely Impact
Incident No
Affected
Archive Server
103216
Allow the use of a new SYST setting to define a date column to drive the archiving process when we have
Match Type = 'Not Matched'.
89
Issue No
Description
Priority
RES-1186
Resolved cases are not working in the customers system
P2
Problem Reported
Resolved cases are not working in the customers system
Component
Likely Impact
Incident No
Affected
Toolbox
Low
104326
Change the 'Resolve Case' Event so that if we have an exported case for which the X_EXPORT_TYPE syst
setting is not set to 'STANDARD', set cast.status to 'WAITING' rather than 'ACKNOWLEDGED'.
Issue No
RES-1199
Description
Modify initiation events to insert the current 'Event Date'
attribute into workflow_queue.event_date instead of today's
date
Priority
P2
Problem Reported
The workflow server defines its 'Event Date' attribute to be equal to the current value of
workflow_queue.event_date. It is required that when a workflow server processes an initiation event, the value
of workflow_queue.event_date it inserts is also equal to the current 'Event Date' attribute, so that it is passed on
to successive initiaitons. However, initiation events currently insert today's date into
workflow_queue.event_date when they insert their row into workflow_queue. Therefore if a first initiation had
an 'Event Date' which was taken from the statement date of the message feed as processed by gems, this date
will be lost in any successive initiations called by initiation events if its 'Event Date' is different from today's
date. We will therefore modify the initiation event so that it inserts the value of the current 'Event Date' attribute
into workflow_queue.event_date.
Component
Likely Impact
Incident No
Affected
Workflow
Low
63629
Modify the initiation event so that it inserts the value of the current 'Event Date' attribute into
workflow_queue.event_date.
Issue No
RES-1200
Description
Priority
Enable the aas password file aas_archive_database.properties
P2
to reside on the database server
Problem Reported
There are two issues installing/running AAS 3.2 for TLM2.5 SP1. 1. Seems that the stl_advarc_package.sql
does not cater for Oracle LDAP connection strings when using the aas_archive_database.properties file to get
the connection parameters. An LDAP connection string cannot be entered in the requested URL format in the
aas_archive_database.properties. To overcome this, we had to hard code the connection string in the
stl_advarc_package.sql to enable a connection. 2. Customer policy is to not allow applications to run on the
Oracle database server. This meant that the aas_archive_database.properties file cannot be located. To overcome
this, we had to hardcode the file location in the stl_advarc_package.sql to overwrite the mandatory
$TLM_HOME/cfg location. No $TLM_HOME exists on the database server. These changes have overcome the
immediate issues but would need to be addressed by STL for a supportable resolution.
Component
Likely Impact
Incident No
Affected
Low
106190
A new SYST setting called 'ARCHIVE_PROP_PATH' has been created to allow the custom definition of the
location of the file aas_archive_database.properties which is used by AAS on Oracle.
90
Issue No
Description
Priority
RES-1206
Allow tolerance matching to work with pre-match aggregation P2
Problem Reported
Currently the pre-match aggregation of data can't work with declared tolerances on the match columns - the
aggregated amount is only substituted back into the reference array after the tolerance processing has happened.
We need the tolerance match logic to be able to work on aggregated data, generating two versions of the
calculated amounts/dates as they are put back into the reference array.
Component
Likely Impact
Incident No
Affected
Workflow
Low
63365
Allow tolerances to apply to aggregated results
7.5
SmartStudio
Issue No
Description
Priority
SMA-2967
Performance changes to support latent networks
P2
Problem Reported
Improve the speed of the application start-up and make it more resilient to network failures.
Component
Likely Impact
Incident No
Affected
Client , Server
Low
105759
Performance improvements have been made which should affect the loading of SmartStudio clients on slow
networks.
Issue No
SMA-2938
Description
SmartStudio has no concept of Private Views, and so there is
an upgrade issue between 2.6 and 2.7
Priority
P2
Problem Reported
There is an issue where WebConnect still has the concept of Private and Public views, whereas SmartStudio
does not, and this causes confusion where private views are available within WebConnect, but cannot be seen in
SmartStudio. We need to establish an upgrade mechanism to migrate private views over to public views. This
can be done either by making use of the current SmartStudio data migration solution, or via the standard
upgrade scripts.
Component
Likely Impact
Incident No
Affected
Client
Low
105758
An optional upgrade script has been added which will convert private views into public views.
91
8 Known Issues
Known issues are bug fixes found during testing of the current version of each component, which do not fully
address an issue and have been failed by Quality Assurance. These outstanding issues have a straightforward
recommended workaround, or are felt to be of limited impact to the majority of users. They will be addressed in
a future release.
8.1
WebConnect
Issue No
WBC-3686
Description
Priority
Problem with Chart Controls having apostrophes in
P2
name
Problem Reported
Customer had a problem with some upgraded dashboards (from their 2.1SP1 environment) not opening. They
noticed that a common factor seemed to be the use of apostrophes in the name of the control - they listed the
issue against a Chart control, but it may affect others. It seemed that when they removed the apostrophe the
control worked OK.
Recommendation
Avoid using apostrophes and any other special characters in control names.
Issue No
WBC-3721
Description
Exception error when drilling down to child
dashboard if drilldown was previously cancelled
when auto launched.
Priority
P2
Problem Reported
Build Version: 2.7 SP1 build 8 Pre requisite - a parent dashboard with grid control has a child dashboard with a
grid control with the following set: each time Launch of parent Parameter mappings Log into Dashboards' menu
then Signed Amount CASH DASH1' dashboard. Click on the Search button at the Parent dashboard when
prompted. At the Child search prompt, click on the Cancel button. Now manually select a row in Parent
dashboard, right-click and select child drilldown. WebConnect returns an error.
Recommendation
Do not cancel the search prompt. If this problem occurs, close and reopen the parent dashboard, then perform
the drilldown again.
Issue No
WBC-3734
Description
Priority
Audit trail for Case Resolved shows as Case Raised
(when using Case Resolved on Set-based Release
P2
Workflow)
Problem Reported
In Recon Admin attach Case80_resolve to Set-based Release Workflow (on Set = SMOKE_535) [use a
workflow rule of Count(GIN) > 0]. Open dbd = Securities Ad-Hoc Item Search (Web) with Set = SMOKE_535
Release Group [21, 16, 2, 3, 52, 57]. Cases 990 & 991 correctly Resolved. However the audit trail then shows
Case Raised.
Recommendation
None. This issue requires further investigation and will be addressed in a future release.
92
Issue No
WBC-3733
Description
Case Resolve is not executed or audited when fired
against items
Priority
P2
Problem Reported
Open dbd = Securities Ad-Hoc Item Search (Web) with Set = SMOKE_535 Execute the Case80_tool on Group
[21, 16, 2, 3, 52, 57]. It is expected that this will: 1. Be audited on the items. 2. The cases 990 & 991 will be
resolved. Neither of these happen. However, if you attached Case80_resolve to Set-based Release Workflow (on
Set = SMOKE_535) [use a workflow rule of Count(GIN) > 0] then the cases are resolved. There is still an issue
with the audit trail when this is done (please see WBC-3734)
Recommendation
Issue No
WBC-3762
Description
Priority
Child Form refreshes as empty after inserting a row
P2
on the parent
Problem Reported
1. Created a message routing parent grid that drilled down to a child form 2. The child form is set on Subsequent
Refresh of Parent 3. When I insert a message routing row on the grid and click save, the child form is refreshed.
- However, it displays as empty. Same also occurs when a row is deleted in the parent.
Recommendation
Following an update of a parent grid, if a child form goes blank refresh the child form manually so that it
displays the correct data. If the Refresh child on subsequent refresh of parent option is set for the dashboards,
manually refreshing the parent will also refresh the child.
Issue No
WBC-3771
Description
Message Routing: java.lang.NullPointerException
creating two message routing rows
Priority
P2
Problem Reported
Issue creating two message routing rows. Create row 1 as an Action = Ignore for From Message Feed Type =
Our Cash Settlements (see attached) Create row 2 the same but as an Action = Delete for From Message Feed
Type = Their Cash Settlements Save Now edit row 2 to have Action = Ignore and the error occurs on Save
Recommendation
Only occurs with message routing. Always refresh your dashboard after saving an insert or edit.
Issue No
WBC-3773
Description
Message Routing - Validation in WebConnect
different to Recon Admin
Priority
P2
Problem Reported
1. In WebConnect I can create the following message routing record: Feed: 123 Action: Delete From Type:
Their FX Option To type: Broker Call In Recon Admin, I am stopped from entering a To Type if the Action is
either Delete or Ignore.
Recommendation
Ensure that you do not enter a To Type if the Action is either Delete or Ignore.
Issue No
WBC-3751
93
Description
Priority
Release of items where Reference 1 is not defined is
P3
treated differently in Sybase (cf. Sqlserver)
Problem Reported
Using identical data on Sybase and Sqlserver. Running the Smoke test, Smoke test - Net to Net matching
(optional): Load the data: LDGRFEED 940LDGRFEED :25:TEST_NETTINGL_1 :28C:1/001
:60F:C040501EUR0, :61:040501040501D1000000,TRAN//TEST :61:040501040501D500000,TRAN//TEST
:61:040501040501C1000,TRAN//TEST :62F:D040501EUR1499000, $ STMTFEED 940STATFEED
:25:TEST_NETTINGS_1 :28C:1/001 :60F:D040701EUR1499000, :61:040701040701C400000,TRAN//TEST
:61:040701040701C503000,TRAN//TEST :61:040701040701C589000,TRAN//TEST :62F:D040701EUR7000,
$ to suitable Our Cash Settlement (Ledger) and Their Cash Settlement message (Statement) feeds on a new Cash
Set, currency = EUR. Set the Set > Financial Parameters > Charge Limit (Debit and Credit) to 100. In User >
Access and Limits: Set the User Limit Cash - Credit Netting = 100 Set the User Limit Cash - Debit Netting =
100 Check that the syst setting of allow the creation of statement net items (CREATE_STMNT_ITEMS) is set
to 1. If you have to change it, you will need to restart the app server. Make sure you know the user id and
password of another user which has the default access and limits set to high. This user will be needed to give
supervisor approval for the creation of any netting items > 100. Data Feeds Test Steps Action 1. Release item
GIN = 2 (amount = 400,000) with item GIN = 3 (amount = 1,000,000). When Release Interaction screen is
displayed, set Netting item type to Ledger Netting item if necessary. Enter id and password of supervisor user.
Enter value for reference1. On Sybase the user is *not prompted* for Reference 1, on Sqlserver this is
mandatory
Recommendation
None, however, that this is an unlikely scenario as Reference 1 is usually populated.
8.2
Design Studio
Issue No
DST-1297
Description
Priority
Error "Invalid expiry date or next password change
P2
date" when changing lead user authority for a User.
Problem Reported
TLM Design Studio Version DS 2.7 Build 2.7.37 Error "Invalid expiry date or next password change date"
when changing lead user authority for a User. Changed to p2 because i can't save changes.
Recommendation
This is only an issue for Users who have 'user expiry date/next password change date' configured.
Issue No
DST-1301
Description
Priority
Problem in Product Version Audit where incorrect
data is displayed within the Database Installation
P3
History tab
Problem Reported
There is an issue within the Database Installation History tab, where patch files are being shown as applied to an
incorrect patch. This however, should not have an impact on the component determining compatibility with the
database overall.
Recommendation
For more accurate data, see the contents of the product_version_audit table.
94
Issue No
DST-1307
Description
Custom system messages set in front end write to
emsg not ds_emsg
Priority
P3
Problem Reported
Custom system messages set in front end write to emsg not ds_emsg. CMsgs.loadEmsgs reads all messages with
id < 10000 from ds_emsg but altering the message using the front end edits the version stored on emsg and
therefore has no apparent effect.
Recommendation
8.3
SmartData Services
Issue No
SDS-405
Description
Priority
No default value binding for soft_lock_key attribute
P2
for Sybase database.
Problem Reported
The dbcreate_smartdata.sql script for Sybase database does not contain default value binding for soft_lock_key
attribute of role_header table. This issue does not allow to do CI import on Sybase database.
Recommendation
Issue No
SDS-423
Description
Priority
Error "No match for TLM Version 'TLM2.800' on
syst found in configuration file" when trying to log P2
into the latest CI 3.4 build.
Problem Reported
Error "No match for TLM Version 'TLM2.800' on syst found in configuration file" when trying to log into the
latest CI 3.4 build.
Recommendation
Issue No
SDS-429
Description
TLM2.7SP1 - csvload - trace/memory messages
displayed after load
Priority
P2
Problem Reported
When csvload is used on our suse10 server (may be other platforms but only suse10 used so far) error messages
are displayed after the load has successfully complete. We already have a note in the guide informing users to
ignore the "glibc detected " message but we have encountered the additional errors. Also, when csvload was run
against smartdata refdata and the error was displayed, csvload did not terminate correctly, it just hung. when
loading refdata for recon the trace was displayed but it did terminate cleanly.
Recommendation
You can ignore these errors, csvload does load the files successfully.
8.4
95
Recon Services
Issue No
RES-1264
Description
Item Reference 1 is mandatory for Manual Input
(GMI), but you can load data with GEMS that has
no Item Reference 1
Priority
P3
Problem Reported
The feed is: LDGRFEED 940LDGRFEED :25:TEST_NETTINGL_1 :28C:1/001 :60F:C040501EUR0,
:61:040501040501D1000000,TRAN//TEST :61:040501040501D500000,TRAN//TEST
:61:040501040501C1000,TRAN//TEST :62F:D040501EUR1499000, $ STMTFEED 940STATFEED
:25:TEST_NETTINGS_1 :28C:1/001 :60F:D040701EUR1499000, :61:040701040701C400000,TRAN//TEST
:61:040701040701C503000,TRAN//TEST :61:040701040701C589000,TRAN//TEST :62F:D040701EUR7000,
$ The test where it is loaded is: Smoke test - Net to Net matching (optional) The assumption is that it is highly
unlikely a customer has no Item Reference 1 defined - as this field is Mandatory for SWIFT.
Recommendation
None, however, that this is an unlikely scenario as Reference 1 is usually populated.

TLM Recs 2.7 SP1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TLM Recs 2.7 SP1

Caricato da

Copyright:

Formati disponibili

TLM Reconciliations Version 2.

TLM Reconciliations 2.7 SP1 Release Notes

TLM is a registered trademark of SmartStream Technologies. All rights reserved.

TLM Reconciliations 2.7 SP1 Release Notes

New Features and Enhancements ................................ 5

New SmartStudio application ............................................................................... 5

TLM Platform Deliverables................................................................................ 25

TLM Reconciliations 2.7 SP1 Release Notes

New Documentation ........................................................................................... 25

Level of Testing ............................................................ 25

Open Source Code used .............................................. 26

Issues Resolved in This Release ................................ 27

Known Issues ............................................................... 91

TLM Reconciliations 2.7 SP1 Release Notes

2 New Features and Enhancements

New SmartStudio application

TLM Reconciliations 2.7 SP1 Release Notes

Design Studio functions not migrated to WebConnect Studio

TLM Reconciliations 2.7 SP1 Release Notes

New single WebConnect menu structure

TLM Reconciliations 2.7 SP1 Release Notes

The full list of special commands is as follows:

Dashboard availability controlled by roles

User Maintenance in WebConnect

Adding and deleting users (only WebConnect-only users)

TLM Reconciliations 2.7 SP1 Release Notes

TLM Reconciliations 2.7 SP1 Release Notes

Role Maintenance in WebConnect

View the list of roles in the system and their details

Create and configure new roles

Modify roles including Update universe access, change associated tools

TLM Reconciliations 2.7 SP1 Release Notes

TLM Reconciliations 2.7 SP1 Release Notes

New Configuration Transfer utility

You can export all of the configuration data from a database.

TLM Reconciliations 2.7 SP1 Release Notes

New Dynamic Compare custom control

Notes on the displayed data:

- the values are the same.

TLM Reconciliations 2.7 SP1 Release Notes

SmartSchema Properties used

If present, a net total is calculated for the attribute.

If present, the attribute is not compared, however it is still displayed on the

2.7 Configurable Custom Date Formats

2.8 New Expandable Attribute Custom Control

TLM Reconciliations 2.7 SP1 Release Notes

Viewing a list of currently open dashboards

TLM Reconciliations 2.7 SP1 Release Notes

2.10 Grid enhancements

2.10.1 Enhanced filtering

2.10.2 Switching to edit mode

2.10.3 Summary row

TLM Reconciliations 2.7 SP1 Release Notes

2.10.5 Grid Column enhancements

2.10.5.1 Configurable tooltips for column headers

2.10.5.2 Flexible column widths

Fixed width enables you to specify a width for the column.

2.10.6 New shortcut keys for fast-cutting grid data

TLM Reconciliations 2.7 SP1 Release Notes

2.11 Business Logic enhancements

2.11.1 Bulk editing for non-item universes

2.11.2 Business Logic Progress Updates

2.11.3 Attaching documents to non-case universes

2.11.4 New Convert Case tool