255571

255571 - PA-7JYD35/ Tracking Screen Date Range Filter

Copyright OBS Logistics © 2009

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Functional Overview

Client Requirement

Tracking Screen v2.55 - Retain the date Range Filter when performing searches.

When carrying out a search using the drop-down options the Filters disappear off screen. Amend the screen so that the Filters remain in all cases as a combined Search/Filter facility. This change is required as several sites use repeated customer refs.

Added by SS 02/10/08 - When entering data into search option pre populated date range would be removed, however user would still be able to add dates back into the date field to execute a search .

More specific searches e.g. Stock movements with a common reference over a date range to be POD'd

Solution

When a user runs a search by clicking the ‘Refresh’ button, data will be returned according to the filters combined with any data specified in the Search field and Search By drop down list.

If nothing is specified in the search field or in the filters then the data returned will be based on the ‘From Date’ and ‘To Date’ only.

As requested, when a user enters data in the search field the dates in the ‘From Date’ and ‘To Date’ fields will be cleared, and all data will be searched. The user will still have the option of entering dates into these fields to limit the search to a specific date range. However, note that entering dates should be done after entering data in the search field, because if a user specifies a date range and then enters data into the search field then the date range will be cleared out due to the newly requested functionality to remove the dates when entering data into the Search field.

Currently, when the Search By field is used, all Trips except those in a status of PLANNED are searched and returned. When the Filter options are used, only Trips in status of ACCEPTED, EN-ROUTE or COMPLETED are searched and returned. The new combined functionality of Search By and Filters will query all trips, except those in a status of PLANNED.

Scope

This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts.

Functional Description

Sample Layout Below is a screenshot of what the current Search By and Filter options in the TRACKING screen looks like. This is v2.56 taken from CONTST, as developed according to RIO PA-7FZBNZ.

Currently, when the user types anything into the Search By field, the filters are coded to disappear, so that the user can only use the Search option or the filter. This is what the screen looks like when the filters are removed:

The screen will be amended so that the filter options are always available, so that they can be combined with the Search By option. Below is an example of how the screen will look when the user enters text into the Search By field, and the filter doesn’t disappear. Also note that when a user does enter text into this field, the Date Range will be cleared out so that all data is searched without restriction, as you can see below:

Coding Amendments

Currently, the WHEN-VALIDATE-ITEM trigger on the Search By field fires when the user clicks into or enters data into this field. The current code within this is used to make the filters disappear

This code will be amended and used to clear out the date range when a user enters data into this field

When the user clicks the ‘Refresh’ button, this calls procedure F_REFRESH_STOP_LIST, which displays trips in the bottom section of the screen according to the filters or using the Search By. This procedure will be amended to combine both search and filter options. Attached below is a link to the preliminary version of the amended code for this procedure.

References

Ref No	Document Title & ID	Version	Date
1	EST-255571 PA-7JYD35 Tracking Screen Date Range	1	08/10/08

Document History

Version	Date	Status	Reason	Initials
1a	13/10/08	Draft	Initial Version	LAD

Authorised By

Dave Meir	Development Manager
Suk Sandhu	TMSCC MTS Product Manager