Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Cutoff operation

Updated on January 18, 2022

The cutoff time in the transaction and step class is a string property and is in the format of HHmmss. It does not include a reference to time zone. During processing, the time is compared with the current time and time zone of the server processing the transaction to determine if the cutoff time has been reached.

For example, if the server is in CMT, set the cutoff times to the value in CMT. If the server is in CMT and the accounting deals with a processing area in EST whose cutoff is 18:00 EST, then set the cutoff to 17:00 (the CMT value). The 17:00 time is then compared with the time portion of the current date on the server (which is in the server time zone).

Note: Cutoff times (warn and cutoff) are stored in each transaction and the earliest transaction time is copied to the Step.

The rules that compare current time to cutoff times are:

  • Function rule named PegaAcct Default PastStepCutoff – Compares the hour and minutes of the current time (using the server’s time zone) with the step cutoff.
  • HTML fragment rule named FinTxnCutoff – Compares the hour and minutes of the current time (using the server’s time zone) with the transaction cutoff warning or cutoff times. This is used to display the red or yellow clocks on the worklist if a transaction is past warning or cutoff.

Checking to determine if a step is past cutoff occurs in the FinStepPost flow in the work object class using the activities FinStepCutoffEval in the work and step classes. The processing of accounting which is past cutoff differs based on a map value.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us