Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

The auto refresh is handled based on refresh schemes.

Example of a Refresh Scheme
{
	"Tables": "", // table name or comma separated list of multiple tables names
	"AddRepositionTo": '#NewRecord', // default reposition to newly created record (other options: #KeepSelection, #NextRow)
	"UpdateRepositionTo":'#KeepSelection', // default keeps selection of the selected record (other options: #NextRow)
	"RemoveRepositionTo": '#NextRow' // default reposition to next available record using #NextRow
}


Above is the default Scheme, the refresh will add the BEs own entityTable by default and you can add multiple Tables in the refreshScheme.Tables.

The reposition options are default values (you are not required to define them if you need to add more tables to the refresh).

You can also change the handling on Add event, for eg. to reposition to the currently selected record, by changing the AddRepositionTo: '#KeepSelection'.

ClientSide API for calling the refresh

For a delete refresh you can call the RefreshEmitter as follows:

akioma.RefreshEmitter.refreshData('eTerm*', { lastRowState: 'delete' }) // This will select the next available record

For an update refresh you can call the RefreshEmitter as follows:

akioma.RefreshEmitter.refreshData('eTerm*', { lastRowState: 'update' })

For an add refresh you can call the RefreshEmitter as follows:

akioma.RefreshEmitter.refreshData('eTerm*', { lastRowState: 'add', lastUpdatedRecord: { selfhdl: 'A69:111:000008101398'} })

Wildcard support is available, as you can see in the above examples where using 'eTerm*'

For the moment, only 'begins with' is supported in the wildcard.



  • No labels