When the Client Monitor is running, all communication between the client and database will be recorded. The resulting entries are a complete list of the objects and permissions required to perform the process that was recorded. This feature makes it easy to record the required permissions for any process. This process can be run in a test company. The Client Monitor can be used only in the Classic Client.

The actions performed do not need to include every possible lookup. With the Relation in the Source Code Analyzer and Add Related Permissions checked in Security Setup, additional permissions are automatically added when needed. This can also be controlled from the Add Related Permissions in Permission Set Recording when adding an Recording to an Permission Set.

When the option Extend Insert Permissions in Security Setup is enabled, you only need to insert a record. The permissions for Modify and Delete are added automatically because the Extend Insert Permissions field is checked. This can also be controlled from the Extend Insert Permissions in Permission Set Recording when adding the Recording to the Permission Set.

When recording permissions on a Form (Classic Client only) or on a Page (RoleTailored Client only); the Permission Set for Both Clients field must be checked in Security Setup. This ensures that permissions recorded for forms will be duplicated for pages and vice versa.

A few pages are unique and are not used in the Classic Client. These objects can still be recorded from the Object Designer. This can also be controlled from the Permission Set for Both Clients in Permission Set Recording when adding the Recording to the Permission Set.

Recording permissions for a Role Center in the RoleTailored Client requires executing the forms used for the Role Center from the Object Designer.

Before recording permissions for objects used in a process, the database should be closed and opened. Permissions for any objects previously stored in the object cache should not be included in a new recording. Closing and opening the database clears the object cache and ensures that no objects from previous processes are stored in the object cache. Another way to ensure that no objects are inadvertently recorded is to set the object cache to 0 when making a recording. However, setting the object cache to 0 can cause very slow performance and should be avoided in a live system.


Refer to the Documentation for the processes in Easy Security

Like   Don't Like

© 2015 Mergetool.com. All rights reserved.