Pre and Post Process in Timesheet Workflows

The Timesheet Workflows include Pre and Post Process functionality, allowing you to execute custom validations or actions during State Transitions. Pre-process procedures run before a transition is committed, enabling error or warning checks, while post-process procedures run after the transition is saved, supporting follow-up actions.

Pre and Post Process functionality helps enforce custom business rules during timesheet transitions. Pre-process procedures can prevent errors or flag warnings, while post-process procedures handle automated actions after the transition, supporting follow-up actions. Both rely on database stored procedures.

Note: To create or customize Stored Procedures, contact PSA Support to discuss your specific business requirements.

How to Use Pre and Post Process

  1. From the Icon Bar click Setup .
  2. From the Navigation Menu click Timesheet.
  3. From the available menu options select Timesheet Workflows.
  4. From the Timesheet Workflows list that displays, click the Name of the Timesheet Workflow you wish to access.
  5. Click the Transitions tab on the left pane.
  6. Select an Transition you wish to modify.
  7. From the right pane navigate to the Processing tab.
  8. In the Pre Process or Post Process field, enter the name of the Stored Procedure to be executed..

    Tip: To create or modify Stored Procedure, contact PSA Support.

Examples

Examples of PRE (error) validations: These prevent the timesheet transition from going through until corrected:

  • Invalid Client/Pay Code combination: An error appears if you select a Pay Code that is not mapped to your Functional Group.
  • Invalid hours for Pay Code: An error appears if you enter hours that exceed the allowed limit for a specific Pay Code (for example, only 1 hour is allowed for “Training Session Cancelled”).
  • Invalid Pay Code for day: An error appears if you enter a Pay Code on a restricted day, such as a holiday.

Examples of PRE (warning) validations: These show a warning but still allow the transition:

  • Part-time employee > 35 hours: A warning appears if you enter more hours than allowed for a part-time employee in a week, based on the configured maximum hours (35 hrs).
  • Leave codes > 3 days: A warning appears if you record more than 3 days in a week against Leave Time Pay Codes such as Vacation Leave, Sick Leave, or Compassionate Leave.

Examples of POST validations: These execute actions after the transition:

  • Automatically create an issue: Executes when a timesheet transition meets defined conditions and copies key data.
  • Run follow-up functions: Performs tasks such as logging or reporting once the transition is complete