Major changes in functionality. Merging PsoftQL functionality that was never publicly marketed before with the version 1 SWS into one platform.
2023-09-26
Small fix for automatic prompt table lookups. If no DESCR field is found, we now look for the first non-key character field on the prompt table that has a non-null value and return that. This supports prompt tables that have no DESCR field but have other fields that can be used as a description.
2024-05-01
Added some missing code to the project during last build.
2026-01-21
Add support for basic Aggregate functions in PsoftQL queries.
Only One record is supported and no support for Having clause currently.
2026-01-25
Added support for sorting results in PsoftQL queries.
Sort order can be ascending or descending.
Multiple sort fields are supported.
Fixed an issue with joining parent-child fields where the key field is a blank character and adding a “space” since PeopleSoft does NOT allow nulls in character fields.
2026-04-20
Added pagination support for SQL-type SWS configurations. Clients can now page through large result sets by passing the pageNumber and rowLimit URL query-string parameters. The response meta now includes pageNumber, rowLimit, and (when more rows remain) nextPageNumber. See Pagination for SQL endpoints for details.
This brings the SQL handler to parity with the PsoftQL handler on pagination.
Existing callers that send neither parameter continue to receive the same response they did before — the change is fully backward compatible.
2026-07-02
PsoftQL pagination now runs at the database level on Oracle and Microsoft SQL Server. Instead of reading a result set and discarding every row before the requested page, the handler pushes OFFSET / FETCH NEXT into the query so the database skips directly to the page and returns only that page’s rows. Deep pages over large records are faster, and the improvement grows with the page number. This applies to JSON, XML, and CSV responses.
The request and response formats are unchanged: the same rowLimit and pageNumber inputs and pageNumber / nextPageNumber metadata apply, so existing callers need no changes.
Database platforms other than Oracle and SQL Server continue to use the previous in-memory paging.
Fixed a defect in SQL-type SWS pagination where nextPageNumber was omitted on a page that was exactly full. A client reading a full page of rowLimit rows now correctly receives nextPageNumber when more rows remain, and still receives no nextPageNumber on the final page. See Pagination for SQL endpoints.