Unlocking Efficiency with Smartes’ Record Lock
Smartes Record Locking helps prevent multiple NetSuite users from editing the same record at the same time. Once implemented, the solution locks configured records while a user is actively editing them, notifies other users when a record is unavailable, and helps prevent conflicting updates or overwritten data.
This implementation guide explains the main setup steps for deploying Smartes Record Locking in NetSuite, including script preparation, record-level deployment, lock duration configuration, and testing.
Before You Begin
Before setting up Smartes Record Locking, confirm the following:
- Have NetSuite Administrator access or the required scripting permissions.
- The Smartes Record Locking scripts are installed in the account.
- Know which record types need locking.
- Have identified the users or roles that should be included.
- Have selected the lock duration for the workflow.
- Test in a sandbox before deploying to production.
Initial Setup: Preparing the Scripts
Begin by accessing Customization > Scripting > Scripts in NetSuite. Look for scripts with the prefix ‘EAG’, focusing on EAG Record Lock Suitelet, User Event, and Client Scripts. These scripts are crucial for activating the solution on desired records.
Deploying Scripts: Activation for Each Record
For each record type, deploy the User Event and Client scripts for every record you want the solution to apply to. This step is essential to ensure the record locking feature functions correctly across all desired records.
Suitelet Setup: Configuring Duration
In the Suitelet, set up as illustrated in your documentation. Customize the Lock Duration, ranging from a minimum of 5 minutes to a maximum of 20 minutes. A timer will display the remaining lock duration to the user.
Continuous Record Lock Control
When a user begins to edit the record, it is locked for the entire duration the user is editing the record as continuous edits to a record will refresh the lock timer and prevent outside edits. However, if the user is inactive the lock timer will decrease from the amount of time set in the script. This feature maintains a balance between record accessibility and data security.