WorkBench can perform column sorting in Table and Documentview styles. This can easily be performed by clicking on a column heading.
Selecting a column heading will display four sort options. When one of these options is chosen the items will be sorted and then displayed based on that selection.
Sortascending – Case insensitive
The first sort option will sort the items from A to Z, based on the item’s value for the selected column. This is done regardless of whether the characters are upper-case or lower-case.
Sort descending – Case insensitive
For the second sort option the items are returned from Z to A, based on the item’s value for the selected column. Again, as this option is case insensitive the returned items can be upper-case or lower-case.
Sortascending – Case sensitive
The third sort option will sort the items from A to Z; but this time all upper-case items are returned first:
Once there are no more upper-case items the remaining items are then displayed a to z:
Sort descending – Case sensitive
The final sort option will sort the items from z to a; meaning all lower-case items are shown first:
Once there are no more lower-case items the remaining items are displayed Z – A:
This sorting only re-arranges the current data brought back in the current query. It does not retrieve new data from the database. In order to retrieve data from the database in a particular order, then one of the database key fields must be selected in the Sort by: field of the query. However, because the sorting occurs on the data in the table it does have the advantage of being able to order the table by frame content or other non key fields.
Parametric queries prompt you at runtime for values for certain parameters prior to the query being run. They are supported for Identity, Name, Key, Level and free-format categories (including picklists).
You are prompted for values when the query is run from the following places:
Query Details dialog
As part of a report
When performing an export by query
A start page
From the Query dialog press the arrow button next to the field you want to set the prompt for and select “Choose at Runtime“. This produces the “Runtime Parameter Definition” dialog where you can setup the parametric query prompt:
You can also specify more than one parametric in the query dialog. This can prove very useful in simplifying the interaction in not having to use the full query details window.
When you run a parametric query the prompt will be shown. An example is shown below:
Parametric queries are supported in both WorkBench and Web Access.
When running a basic item query all items of that type that the user is allowed to see are returned. As a project grows this number may become quite large, it therefore becomes necessary to add additional filtering criteria, such as the date. Querying on dates allows you to filter by the modification or creation date of an item.
Relative and Absolute Dates
You may have a good enough memory to remember it is the item you created on the 24th that you want to return. Choosing ‘Specify:‘ from the drop-down will enable a date picker. However, it is much more likely that you’ll want a range of dates, as you want to run a query each Thursday to find the new ‘issues’ raised in the last week. Relative dates allow you to do this, choosing ‘Start of last week’ and ‘Today‘ would give the data required. The benefit of the relative date specification is that the query can be saved. It can then be run next week to give a new set of values.
An item’s creation or modification date may not be something that you can directly control. It certainly can not be set in the future. If a data entry clerk enters all emails as items on a Friday they’ll all have the same creation date. Equally updates will change the modification date making an old item appear more recent. Categories can be set to hold abstract data of type Date, this would allow a value such as “Review Date” to be set, and then queried upon. This data is based on a user input value and not the automatic dates recorded by Cradle.
This filtering functionality is available wherever queries can be run. This includes WorkBench, Web Access, C_IO command line tool and the Cradle API.
At some points in a project’s lifecycle, a large number of items need to be submitted. These may be too numerous to ‘select‘ and ‘Submit‘, Cradle offers ‘Submit by Query‘ option. This allows submission of all the items (subject to access rights) that match a query to be moved to the review stage in the configuration management system.
Check Before Submission
Using the ‘Show Items’ button allows the user to run a report that will detail which items the current settings will submit. In this way users can ensure that the correct items are going to be processed before creating all the approval records and changing the status of the items being submitted to that of ‘Under Review‘. For further information see the article How to Submit Items for Review Based on a Query. Also see further information on Cradle’s Configuration Management System in this article.. Configuration Management features are also available in Web Access.