Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Holiday Cutoff in Smart Dispute not working

SA-5626

Summary



Smart Dispute accounting holiday cutoff not working correctly. If a claim is created on a date listed in the accounting calendar as a holiday or considered to be a "closed" (non business) day, and accounting is performed on that claim, the posting date of the accounting step reflected in the PAF_Entry table should be the next business day. The system appears to be ignoring those dates and posting the actual date the accounting step was executed.

For example, if December 25 is listed as a holiday, and a claim is created and provisional credit is given (which triggers accounting steps), the posting date of the accounting that is performed and stored in the PAF_Entry table should be December 26, as that is the next business day. The date is populating incorrectly.

The developers on the Cap1 project believe this is due to a possible mismatch. The calendars reflect US Timezones, but the activities that control the posting of the accounting to the PAF_Entry tables appears to be calculating the date based on GMT.


Error Messages



No error messages - the incorrect date is populated in the table.

Steps to Reproduce

  1. Configure closed and holiday dates in the accounting and default calendars
  2. Create a claim on which accounting steps are performed on a date that is a "closed" or "holiday" date
  3. Check the posting date in the PAF_Entry table to see what is shown as the posting date.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.


Resolution



HFix-20578 released. 

 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us