Office +1 (678) 666-2100
Fax: +1 (678) 666-1997

Search:

Installing and implementing Easy Security in a production environment

Overview: This document outlines the necessary steps for implementing Easy Security, including Field Level and Data Security, in a production environment. We have also included steps to bring over Easy Security data from a test environment. Every NAV install is unique, so this should be used as a guideline only. The intention of this article is to provide summary steps, since detailed information can be found in the referenced FAQ documents.

1. The user performing the installation must have permission to create objects on SQL Server.

2. Make sure that the customer license has been updated to include the Easy Security granules and has been uploaded into the production environment.

3. Import the Easy Security objects and compile. Note: It may be necessary to compile all menusuite objects if there are other add-on menus.
For additional details, see:
Easy Security: Installation and Setup (Logins and Permissions)

4. Create the Easy Security company

5. Export all objects as text from Object Designer. This step requires a partner license unless the customer license has granule 7200. For Field Level and Data Security, a text file of tables, forms and pages should also be created.

6. If Field Level and Data Security is to be installed, some FL permissions need to be added to a role that applies to non-super users, like the ALL or Basic roles. If there are multiple ALL roles, these permissions should be added to all. This step should be done prior to the Initialize step.
TableData (Read): 14123801 to 14123809, 14123811 to 14123813, 14123817 and 14123818
Codeunit (Execute): 14123801, 14123805, 14123806, 14123811, 14123812 and 14123814

7. In the Easy Security company, run Initialize Complete Setup.
For additional details, see:
Easy Security: Installation and Setup (Logins and Permissions)

8. Optional: Export any Permission Sets, Permission Groups, Logins and Object Properties from the test environment that is needed in production.
For additional details, see:
How to move Easy Security data from a test environment to production

9. Optional: Import Demo Data if desired and import data exported from Test. This completes the Logins and Permissions implementation. Login setup for Roles must be done manually.

10. In Field Level and Data Security Setup in the ES company, check Install Allowed and execute the Get Relations from Source Code, using the data from Logins and Permissions. If Logins and Permissions granule is not installed, use the text file of all objects created earlier.
For additional details, see:
Easy Security: Installation and Setup (Field Level and Data Security) 2009 R2
Easy Security: Installation and Setup (Field Level and Data Security) 2013+

11. Optional: Copy over Source Table Setups from Test and export any Field Level Security Codes or Data Security Codes needed in Production.
For additional details, see:
How to move Easy Security data from a test environment to production

12. Backup forms and pages by exporting to fob from Objects Designer.

13. Implement Changes in Code. A partner license is required for this step, and due to the potential for compile errors in the customer's objects, a partner should be assisting with this step as well. Note: During the time that the objects are in an uncompiled state, users may receive errors on pages and forms.
For additional details, see:
How To Implement Changes in Code

14. Import any codes exported from Test

This completes the Field Level and Data Security implementation. User Security Setup must be done manually.



Like   Don't Like

© 2017 Mergetool.com. All rights reserved.



Related resources

Download software from Mergetool.com