Fixes issue
30187: prevent build in unsupported PG versions
Related to issue
30007: Backout changeset aed0c66779e9
Related to issue
30095: Backout changeset 195dff675189
Related to issue
30189: Adapt process handler to retrieve objects without id
Fixes issue
30189: Values could be overwritten in Modify Payment Plan
In the Modify Payment Plan grid an add function is creating an object to set the values for the new records. This function is setting an empty string for the id property, i.e., every new created record is generated with the same id. This causes that the selection record change is not handled properly under some circumstances in the _startEditing method of the ListGrid class.
To avoid this problem, the id property is not included in the object instead of leaving it empty.
Related to issue
29848: code review improvements
Fixed v_invoicepaidstatus variable type
Moved query code from the HqlQueryTransformer to the Application Dictionary
Fixes Issue
29848:Credit can be used although the payment were it was
generated is not in the configured invoice paid status
Implement FIN_Utility.invoicePaymentStatus and aprm_seqnumberpaymentstatus
in CreditToUseTransformer where clause.
Related to issue
30060: send null ROW_ID when selecting a record in P&E
Send null ROW_ID to avoid the edit values be overriden by the FIC response
Fixed issue
30123: Sample data (F&B International Group Client) for PR15Q03
Updated sample data for PR15Q3
Related to issue
30123: Delete fact_acct rows of sample data
Some rows of the table fact_acct has been removed. The last two years
of this table is still used for some reports.
Related to issue
30123: Export Log Clean Up process changes of sample data
The changes made in the process has been exported from the sample data
and commited.
Related to issue
30123: Export module scripts changes of sample data
The changes made in the ant update.database command has been
exported from the sample data and commited.
Related to issue
30060: removed already existing condition
fixed issue
28911: Possible to create new rows in edit only tabs in grid view
The problem was that when the UI pattern of the tab was set as "edit only", it was
possible to create new records in grid view, after editing the last record in grid view
and pressing the tab key and also by pressing the down arrow key.
The problem was in the ob-standard-view.js. There were two functions, one called
"setEditOrDeleteOnly" and another one called "setSingleRecord".
The first one, was calling another function called "setListEndEditAction" that changed
the value of "listEndEditAction" from "next" to "done" and that is the correct behaviour,
because if it is next, it allows to create a new row and in these cases we don't want it.
So, in the second function, "setSingleRecord", it was necessary to call the same function
for changing value of "listEndEditAction" from "next" to "done" for avoiding the bad behavior
of being able to create new rows.
Related to issue
30060: displayed value should be set in fk fields
When the default value of a foreign key field in a new record does not exist already in the grid data, the display value can not be recovered in the setEditValue() method.
In order to ensure the display value is updated to reflect the new edit-value for this field, the display value is now explicitly set.
fixed bug
30151: NPE with clientclass field + field level access
When calculating field role access, the code assumed all fields are linked to
a property which is not the case of clientclass fields. In this case a NPE was
thrown.
Related to issue
30174: Triggers temporarily disabled for whole application through webpos
Added check/test code in OBDal to prevent disabling triggers 'globally'
Related to issue
29766: Retail Operations Buffer: store all transactions in operations table before processing
Small re-ordering so that code uses loop instead of recursive call
Related to issue
30132: Updated condition to use the same as OBViewTab
Updated the condition to use the same as OBViewTab in getParentProperty() method, to retrieve the parent property when the parent tab and the child tab use the same table