...
Creation of Rebate Records – There are no Rebate Records created by default for the line, so you always have to use the function add() to add the Rebate Records, otherwise there will be no Rebate Record for the line item.
The Rebate Records (created by the line item logic) will appear in the list of Rebate Records only after you save the Rebate Agreement.
Rebate Records – When a Rebate Record calculation job runs, it sorts the Rebate Records by agreement.uniqueName and rank, so records with a lower rank get calculated first. (Ideally there are no dependencies between Rebate Record calculations, so avoid using the Rank field for this purpose.)
Rebate Records – Although the inputs are copied from the rebate agreement line item into the rebate record, the UI will only render those inputs that are created during syntax check. This means that if an input is generated within an logic element that has the calculation context set to agreement, this input field will not be visible on the rebate record detail screen.
Payout Records – During Testing of the logic, the functions on payoutRecords do not do anything, so no records will be stored into database, and ultimately if you will try to read the records using payoutRecords. find(Filter.isNotNull("name"), you will get an empty list.