QuerySecurityCheck and SaveSecurityCheck

QuerySecurityCheck and SaveSecurityCheck exist only in DevForce Classic.  In current DevForce, the facilities provided in Classic by those methods are provided via IEntityServerFetching and IEntityServerSaving interfaces, respectively. By implementing these interfaces in your own class (deployed server-side) you gain the ability to intercept queries and saves, examine their content, and then take any desired actions including modifying or refusing the request.

 

IEntityServerFetching mandates the implementation of an OnFetching method which receives an EntityServerFetchingEventArgs parameter. That parameter provides access to the submitted Query object, the authenticated Principal (user) who submitted it, and a Cancel property, among other things.

 

Similarly, IEntityServerSaving mandates the implementation of an OnSaving method which receives an EntityServerSavingEventArgs parameter. That parameter provides access to the authenticated Principal (user) who submitted it, a Cancel property, and an EntityManager instance that contains all the entities submitted for the save.

 

Incidentally, you also get IEntityServerFetched and IEntityServerSaved interfaces for after-the-fact server-side processing of queries and saves.

 

Sorry, we don't yet have an example showing their use, but I think you will find it straightforward. Please post a question if not.