systems@work Version 6.1.8

time@work, expense@work and forms@work Version 6.1.8 have been released to the Customer Web.

Version 6.1.8 contains the following enhancements:

  • Modification of the operator (e.g. * or /) can now be prevented in Cross Rates Override
  • Option to control the minimum number of parameters used to determine image matching in forms using the options introduced in Version 6.1.7
  • Status Date, Document Employee and Action Employee enabled as runtime parameters in Inquiry Profiles
  • Timesheet Type now specifiable at Company level (in addition to System and Employee)
  • Attendance Form Type now specifiable at Company level (in addition to System and Employee)
  • Login name extended to 50 characters
  • Encryption algorithm for password storage has been changed
  • Manual Cross Rate Override now also works for exchange rates obtained through Web Services
  • External Single Sign-On is now also an option in the systems@work App
  • Visibility of Links (as shown on the PSW Home Page) can now be controlled by Employee Company and Distribution Masks
  • Visibility of News (as shown on the PSW Home Page) can now be controlled by Employee Company
  • Account code lists in the systems@work App are now controlled as they areĀ in forms in the PSW
  • Images (such as receipts attached to expense forms) can now more easily be printed in Reporting Services templates
  • Optionally Timesheets can now be sorted automatically by Project and Task
  • The names (filenames) of Linked Documents are now available in Inquiry Profiles
  • Option to specify a Provider for a Cross Rate and to specify that a calculation should obtain a cross rate based on the ProviderĀ defined on Company, Client or Project. This enables, for example, different cross rates between the same pair of currencies to be used, depending on Company. (National Banks, for example, set different rates in different countries.)
  • Reports can now be published to a folder (so that they can be accessed from outside systems@work)

Release Notes describing corrections in this release can be found on the Customer Web.

< Back to blog