Scoped application reading from a global table with caller restriction

[MK2]

Our scoped application wants to read from the 'sysevent' table which is in the global scope and has caller access set to caller restriction. Since the scoped application cannot read directly, we have created a script include in the global scope that reads from the 'sysevent' table and returns the result back to the scoped application. Is this a correct approach to read from a global table with caller restriction ? Please suggest any other approach if possible.

[Community Alums]

Hi MK,

That's the right Approach!!

Check the sysevent table entry. Enable the can read permission.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Community Alums]

Hi MK,

Any update to this ?Any follow-up required? if not

Kindly mark the answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep

[Markus Kraus]

Yes this is the correct approach.

Changing the sysevent table's 'Application Access' attributes requires you to rebuild the cache in order for the changes to take place. Depending on how large your production instance is, this might not be desired.

If you still go for the changes in the Application Access, make sure you do a gs.invalidateCache() in a background script (global scope) with Record for rollback = false.

[NStefanisko]

If find the whole concept of Write Only to be utterly nonsensical. There is a function gs.eventQueue() that lets me create an event, but no function that allows me to read back information regarding the events I created?