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 moves 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.
All changes to data inside the Easy Security company are offline from the Live security data controlling
access in NAV. When a Publish of permissions is done the Live data controlling security is changed,
but a Restore Point ensures that changes can easily be reverted.
A Restore Point is also created during the setup to ensure future changes can be compared or reverted
to the original 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; "ES1.xx.xx y.yy.yy.fob" and "ESACC Empty
Objects ES1.xx.xx.fob". The version xx.xx refers to the Easy Security version,
while y.yy.yy refers to the NAV executable version.
The ESACC file should only be imported when initially installing Easy Security.
For future upgrades only the first file should be imported.
If the MenuSuites used by Easy Security (52 and 1052) are already in the database,
additional Menusuites can be imported from the file "ES1.30.09 MenuSuite 51-60 and 1051-1060.fob".
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 C# code matches the current executable.
After importing the objects, remember to compile all the objects within the filter ES* on the Version
List 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.
Language modules are available in Danish, Dutch, English,
French, German, Italian, Portuguese and Spanish. To import the language module,
filter on the Version List with the filter "ES*" and select all objects,
then use Tools, Language Module, Import and select the needed language.
Based on a limitation in C/SIDE it is only possible to import 4-5 additional languages in Easy Security.
Full setup of Easy Security
The company where security is maintained should be a new company with limited data for the application.
Set up of NAV Easy Security can be done from the RoleTailored or Classic Client.
Initialize Complete Setup is done from Security Setup in the Roles and Logins menu of the Easy Security
company.
If using a different country version, it can be necessary to lookup the Role ID for SUPER.
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 in the Classic
Client or the NAV development environment in 2013.
This will normally require a Partner developer license.
This can also be done later from within the application if objects are updated or the text file was
not available during installation.
If the Role Builder module has been purchased, the "Role Builder Enabled" must be checked.
This will create data in the Role Details and related tables during the initialize process.
This can also be done later from within the application.
Note: If executing Initialize Complete Setup from RTC,
the path must point to a folder on the NAV server or a UNC path accessible from the server.
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 Demo data for Roles, Recordings, and Role Groups
Over 100 new roles are delivered with the solution.
These roles are based on recordings and contain roles for segregation of duties.
Roles for Finance, Sales, Purchase, basic Inventory,
Role Center roles, and some technical roles like SUPER(READ) are included.
Because these roles are based on recordings, many customizations are automatically handled.
The roles are recorded and tested in the North American and German databases.
In addition, Role Group Demo data has been added to match the data in the Roles Demo Data spreadsheet.
To import the Demo Data (includes recordings), from Security Setup,
click on the Import Role Demo Data button for Roles and Recordings.
Next, click on Import Role Group Demo Data if groups matching the spreadsheet are desired.
The text files for import can be found in the folder with the install files.
For next steps, see the following articles
How To Create a New Role Using the Client Monitor
How To Create a New Role Using SQL Profiler
For additional information, see the Easy Security FAQ list at this link.
NAV Easy Security FAQ
Refer to the Documentation for the processes in Easy Security
Like


© 2015 Mergetool.com. All rights reserved.
