time@work and expense@work Version 3.1.5

Version 3.1.5 of time@work and expense@work has been released and contains a number of significant enhancements.


You will be able to mark approval statuses as having a cut-off date, such that transactions earlier than date will not be considered for approval. This is useful when approvals functionality is ‘switched on’ from a given date.

You will optionally be able to specify that after an approval status has expired it will be modified to a specified status value. This means that transactions that have ‘expired’ without approval will no longer be presented for approval by project managers or customers.

Exchange Integration

time@work now supports Microsoft Exchange 2007. Should you need advice on configuring this please contact us.

Optionally for a particular Budget it is now possible to specify that all entries will be copied to Employees’ Outlook Diaries regardless of the use of Allocation Levels. This is useful when the refinements of Resource Scheduling are not required.

Support for ‘public’ diaries in Exchange has been withdrawn, but this does not affect the updating of individuals’ separate ‘private’ diaries.

PSW Client/Project Selection Tool

The selection tool has been enhanced to enable:

Return to Project based selection from the Client selection mode

Selection of a specifiable number of projects against which the employee has recently reported time

Task Scheduler

We have introduced a mechanism designed to prevent tasks from running simultaneously (as when more than one Task Scheduler is running or the user starts a task such as Routing from time@work Maintenance).

System Control now contains checkbox fields which enable or disable execution. However, in order that this mechanism should not cause confusion and prevent execution when a task fails, a time interval can be specified so that after this has elapsed a task will be permitted to start despite the value of the checkbox.


We have extended the pre-filtering on the invoice list in Reprint Invoices to the invoice list in Invoice Reversal. This pre-filter now limits the invoices shown to include invoices belonging to a specified number of recent periods.

We have optimized the SQL query used by Invoice Approval Review when evaluating the current user’s list of invoices at Approval or Review status, and we believe the function will now perform at least three times faster.

Cross Rates & Calculations

You need no longer specify Cross Rates between currencies in both directions. We have introduced a checkbox on System Parameters which allows for the use of a Cross Rate between currency B and A if a Cross Rate between currency A and B cannot be found.

PSW My Diary

Allocation Levels established using a Planning Profile in time@work Maintenance are now preserved when a Diary is saved in the PSW My Diary form.

Calculations are now executed when My Diary is saved.

Employees may modify the number of columns shown in My Diary. This can make My Diary easier to read, since fewer empty cells will be shown when the number of days is reduced.

Planning Profiles

When calculations are executed in Planning Profiles, and when Roles are not specified, the calculation algorithm will now use the same rules as those used during Timesheet posting to determine an appropriate Role value from the Project record (where an Employee may be assigned to a Role on a Project) or the Employee record (where an Employee may be assigned a default Role).

Active Schedules

Access to Active Schedules may now be defined using Employee Groups as well as at Employee level.

Expense Calculations

Calculations in an expense form row will now consider earlier rows in the same form if these are relevant (as for example when accumulations are used to determine a mileage rate).

Reporting From The PSW

We have enabled the execution of Inquiry Profiles through the PSW. This is a radical enhancement to systems@work that is introduced in this version as a prototype. Currently only Inquiry Profiles without runtime parameters may be executed, and no security controls limit access to each employee.

In the near future we will enable:

Control over access

Substitution of ‘Current Employee’ and other similar concepts enabling the selection (by substitution of Employees or Projects related using a Role to the currently logged on Employee) of Projects owned by a Project Manager, Employees managed by a Line Manager, etc. (This is similar to the concept recently introduced for Active Schedules.) This will make it possible for Inquiry Profiles to show only ‘My Data’, ‘My Company’s Data’, ‘My Team’s Data’, ‘My Clients’ Data’ or ‘My Projects’ Data’.

Handling of selected runtime parameters, likely initially to include Periods, Employees, Clients, Projects, Tasks, and Analysis.

[Note that when an Inquiry Profile is executed from the PSW, the Crystal Reports template selected is the first (in alphanumeric sequence) assigned to the Profile. Note also that this template must be placed in the time@work or expense@work Web Reports folder.]