Ordering and Deletion Tracking

Ordering enables a user to specify how the query response should be arranged.

By default, Oracle Textura Payment Management arranges query response containing various objects in descending order based on their ID field values with the following graph exceptions:

Deletion Tracking

The isDeleted filter defaults to false; when set to true, it returns deleted records for the specified graph entity. Each response includes an isDeleted attribute reflecting the filter used and a dateModified timestamp indicating when the record was deleted in TPM.

When isDeleted=true, only ID, dateModified, and isDeleted are populated. All other fields are null. Access to deleted entities adheres to existing visibility and permission rules, so organizations cannot view records they were not authorized to see before deletion.

Graph Order By Asc/Desc Deletion Tracking
Payment id DESC Yes
Invoice id DESC Yes
Disbursable id DESC Not Applicable
Contract id DESC Yes
User id ASC Not Applicable
Project id DESC Yes
Draw id DESC Yes
PaymentHold id DESC Yes
TpaProgram id DESC Not Applicable
ChangeOrder id DESC Yes
LienWaiver id DESC Yes
Organization texturaCustomerNumber DESC Not Applicable
InvoiceApproval dateModified DESC Yes
SupplierTrackingProgram id DESC Yes
SupplierTrackingProgramValue id DESC Yes
SupplierTrackingContractorValue id DESC Yes
SupplierTrackingSelectedValue id DESC Yes
BudgetLines id DESC Yes
ManualContract id DESC Yes
OrganizationLevelHold id DESC Not Applicable
ProjectUserRole id DESC Not Applicable

Notes:

For deleted records (Filter isDeleted = True)