Before starting the installation please review the Best Practices for NAV Easy Security setup
Following the recommended best practices, a new company is created in the NAV database to contain security
setup. The Initialize Complete Setup process in the Easy Security module copies all existing security
settings from NAV to this Easy Security company. This ensures that all work already done on security
is maintained when installing NAV Easy Security.
Importing Objects
The objects for NAV Easy Security are all new objects.
This makes integration with a customized database very easy since no merge is needed and objects can
simply be imported. The objects are distributed in 2 files; "ES1xxx.fob" and "ESACC Empty Objects ES1xxx.fob".
The ESACC file should only be imported when initially installing Easy Security,
this file contain Codeunits that is modified by the Field Level and Data Security installation.
For future upgrades only the first file should be imported.
When importing the files. Check to verify that the MenuSuite used by NAV Easy Security is not in use
by another ISV solution when importing the objects.
If the MenuSuites used by Easy Security (52 and 1052) are already in the database by other ISV solutions,
additional MenuSuites can be imported from the folder "Additional MenuSuites".
Only one MenuSuite in the range 51-60 and one in the range 1051-1060 should be imported.
During the import of the objects, a warning may be shown about the code using an older version of NAV
(based on hotfixes being applied). This is not a problem because the code is going to be recompiled
to ensure the executable code matches the current executable.
After importing the objects, remember to compile all the objects within the filter Version List=ES*
in Object Designer. Some fields in the security tables have different data types between versions of
NAV/SQL/Native and will cause a run-time error if not compiled after importing objects.
The compile also ensure that he objects are correctly imported.
MenuSuites added is not always showing up correctly.
Because of that remove all filters on the object list,
select the MenuSuites and compile all of them. This normally solves the problem with the MenuSuite not
showing up.
A customer license with access to NAV Easy Security must be uploaded to the database before the install
process can be run.
Language modules are available in Danish, Dutch, English,
French, German, Italian, Portuguese and Spanish. To import the language module,
filter on the Version List=ES* and select all objects,
then use Tools, Language Module, Import and select the needed language.
Full setup of Easy Security
The company where security is maintained should be a new company with no data for the regular NAV application.
Before the setup can be run must a text file with the source code from the database be available.
Initialize Complete Setup is done from Security Setup in the Logins and Permissions menu of the Easy
Security company. If the initialization wizard was aborted before can the function "Set Up Easy Security"
restart the process.
If the Source Code Analyzer module has been purchased,
the "Source Code Analyzer Enabled" must be checked and the path and filename entered for the current
source code. The source code can be exported as a text file from the Object Designer.
This requires a customer license with 7200 Application Builder or a Partner developer license.
Not every objects is needed, but the Source Code Analysis is a central part of NAV Easy Security so
as many as possible of the objects must be exported.
This import of the source code can also be done later from within the application if objects are updated
or the complete text file was not available during installation.
If the Permission Builder module has been purchased,
the "Permission Builder Enabled" must be checked.
This will create data in the Permission Details and related tables during the initialize process.
Note: Because of the size of the Source Code file is the typical upload not possible when accessing
the file from the service tier. The path must point to a folder on the NAV Service Tier or a UNC path
accessible by the account running the service tier.
See the following article for more information.
Accessing Files via RTC
Click on the Initialize Complete Setup to finish the setup.
During the process multiple messages will appear to tell about the progress,
just click ok on these messages. After this process is finished,
NAV Easy Security is ready to be used and the Setup Easy Security window can be closed.
The specific settings that are needed for the installation can now be changed directly in the Security
Setup.
Importing Segregation of Duties Permission Sets and Permission Groups
Over 100 new permission sets are delivered with the solution.
These permission sets are based on recordings and contain permission sets for segregation of duties.
Permission Sets for Finance, Sales, Purchase, basic Inventory,
Role Centers read access, and some technical permission sets for NAV Easy Security are included.
Because these permission sets are based on recordings,
many customizations are automatically handled. The permission sets are recorded and tested in the North
American and German databases for multiple version of NAV from 2009 R2.
In addition, Permission Group Demo data has been added to match the data in the SoD Permission Sets
spreadsheet and for Quick Security.
To import the Segregation of Duties Permission Sets Data (includes recordings),
open the Permission Sets and Import the file from the installation folder.
The Permission Groups can be imported the same way from the installation folder.
SQL Profiler and Templates
For recording in NAV Easy Security the SQL Profiler is used.
The SLQ Profiler is part of the SQM Management Studio and can be used from any computer,
but is easiest done when installed locally. The SQL 2014 Express Management studio contain the SQL Profiler
and can be used again all older version of the SQL Server.
Installing the SQL Management Studio 2014 Express does not require a license and can be downloaded for
free from Microsoft.
The standard template in the SQL Profiler does not contain the needed transactions and a template must
be imported. Open the SQL Profiler and use the "File,
Templates, Import Template" to import the template from the SQL Profiler folder in the installation
folder for NAV Easy Security.
Refer to the Documentation for the processes in Easy Security
Like


© 2017 Mergetool.com. All rights reserved.
