The automatic refresh mechanism works by notifying all Business Entities that match the currently updated Business Entity table or custom handling using the RefreshScheme Attribute settings.
If the update/delete/create operations are not done using the Business Entity from the repository then the correct way to handle the refresh is by ClientLogic code, triggering the refresh programmatically for the needed entity tables.
The auto refresh is handled based on refresh schemes.
...
Above is the default Scheme, the refresh will add the BEs Business Entites own entityTable by default and you can add multiple Tables in the refreshScheme.Tables.
...
| Info | ||
|---|---|---|
| ||
The refresh scheme is not used to mention on which tables to refresh the data, actually the tables present in refresh schemes represent a list of listeners for the changes that will occur in the mentioned tables, which means that if an update / add / delete is done on one of the tables specified in the refresh schemes then the refresh will be done on the DSO table, not the other way around. |
Starting with the SWAT 2019.23 release, also SkipRefresh parameters are available.
...
| Code Block | ||
|---|---|---|
| ||
{
'Tables': 'Table1*,Table2*',
'AddRepositionTo': '#NewRecord,#KeepSelection',
'UpdateRepositionTo':'#KeepSelection,#KeepSelection',
'RemoveRepositionTo': '#NextRow,#KeepSelection' ,
'RepositionToKey' : 'selfhdl,user_key'
} |
Starting with 2020.13, a new parameter refreshConditionCallback is available, support for callback refreshScheme method:
| Code Block | ||
|---|---|---|
| ||
{
"Tables" : "Table1,Table2",
"UpdateSkipRefresh": "Table2",
"RefreshConditionCallback":"akioma.Function_Name(eventSource)"
} |