What's New

Once a year we update our 2-Controlware with new features and bug fixes. On this page you have an overview of all updates based on our release notes.

All release notes are grouped below.

With this release letter we inform you of the release of the new 2-Controlware version 10.03. This release contains new functionality as well as bug fixes. 2-Controlware 10.03 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise. Versions for 2013 R2 and 2015 are available on request. Dynamics NAV version 3.xx, 4.xx, version 5.xx, NAV 2009, NAV 2009 R2 and NAV 2013 are no longer supported. It is not necessary to update your NAV license to be able to use the updated and new objects.

2-Controlware 10.03 has incremental improvements on the existing functionality and several bugs are fixed. See below a description of the most important changes.

Tenant permissions: In Business Central tenant permissions are used for User-Defined permission Sets. Navigation on this type of permissions did not work correctly on all pages. This is optimized. Also the following reports have been modified in BC to handle the tenant permissions correctly:

• Permissions per Permission Set
• Permissions per User
• Permissions per Organization Role

When using Dataset Type ‘Visible’ it is no longer possible to select a Table Relation because you are not able to do the setup based on the related table.

Renaming G/L account No.: When renaming an G/L account with more than 10 characters, the system give an error. This issue is solved.

Analysis Permissions: When analyzing all Standard Competences without a filter, the system also gave results on read permissions object 0. This was not correct if it had not been included in the Standard Competence. The issue is solved

Combination Filter: When using wildcards and a combined filter in a Mandatory field setup the system did not check on this. The issue is solved.

Validation Type error: a Mandatory Field with Validation Type error did only give a warning. It was possible to close the page without changing the field. This is fixed.

Minimum and Maximum Length: A Mandatory field Not Blank and only en Maximum Length did not work. This is solved. With only a Maximum Length you have to fill in at least something up to the maximum length.

Synchronize Organization Role: When synchronizing one organization role, permissions in this organization Role were removed for all users. This went wrong with the synchronization Type setting ‘Replace Permissions Sets’. This issue has been resolved.

For a new installation see the installation instructions.To perform an update installation from a previous 2-Controlware (= 2CW) version see the table below. The fob’s of version 4.01.01(VM) is available upon request.

1. Import ( with replace all) and compile version 2-Controlware 10.03 (“NAVW1x.xx,2CW10.03.fob”).
2. For NAV 2016 and up, the customization of Codeunits 1, 40 and 423 needs to be removed. If you have no other add-ons, you can – after consulting your NAV-partner – replace these Codeunits with the default NAV objects.

Important!

Please be sure to Replace All existing objects. Default action for some objects is Skip or Merge. Furthermore, always check if Menusuite 1052 is available.

There is no impact on permissions.

To be able to use the new objects you do not have to update your license.

The 10.03 update-package consists of one fob-file:

• NAVW1x.xx,2CW10.03.fob: the objects can be identified by version number 2CW10.03.===Dynamics NAV version ===

2-Controlware 10.03 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise.

No new setup is involved.

With this release letter we inform you of the release of the new 2-Controlware version 10.02. This release contains new functionality as well as bug fixes. 2-Controlware 10.02 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise. Versions for 2013 R2 and 2015 are available on request. Dynamics NAV version 3.xx, 4.xx, version 5.xx, NAV 2009, NAV 2009 R2 and NAV 2013 are no longer supported. It is not necessary to update your NAV license to be able to use the updated and new objects.

2-Controlware 10.02 has new features and incremental improvements on the existing functionality. Furthermore, several bugs are fixed. See below a description of the most important changes.

User Groups in Authorization Monitoring:If user groups are used within Dynamics, these can now be included in the analysis of permissions and conflicts. To activate this, the new option “Analysis with User Groups” must be activated within the Authorization Monitoring Setup. This will include the user groups in the analysis. The source type User Group can now be found within the analysis result. Also, a filter is included for this source type. You can also link a user group to a standard competence, similar to linking an organizational role. After a user group has been linked, the analysis result of the user group will automatically be Finding Accepted, and can be automatically approved.

Standard Competences Filter:in the analysis permissions page, it is now possible to see per line which standard competences apply to that line so you can easily filter. The standard competence filter will be included as a column, where the applicable standard competences for these results are shown.

Lookup user fromanalysis permissions page: When using a specific license, the link to the user in analysis permission results did not work properly. This issue has been solved

Incorrect property NAV Enabled: When using a specific license, the property ‘NAV enabled’in the analysis monitoring was not correctly presented. This issue has been solved.

Source nameWhen using a specific license, the name of the source in the analysis results was not shown.This has been fixed, so the name of the user in question is shown.

Invalid filter for field integer: When the validation value of an option field included a dot, an error was returned. This was caused by functionality that considered the dot as a separator for two values. This issue has been solved.

Exception error: Exception errors sometimes occurred when the mandatory fields functionality was triggered. This issue has been solved.

Filter on empty string: Filtering on empty strings in text and code fields did not work as expected. This issue has been solved.

Delete check on dataset security:When dataset security is set up to only trigger on deletion, then the dataset security is only active when a record is deleted. Inserting or modification of records is therefore authorized for all records. This functionality was working incorrect. This issue has been fixed

Wilcard filter: A dataset security where a text filter is defined that includes all values (*) was not functioning correctly. This issue has been solved.

Summary field and dataset security.In the summary functionality the default editable property and the Table security number field were missing. These have been added. In addition, the company was not always displayed correctly. If the field or dataset security is set for one company, then only lines with that company will be displayed for that field or dataset security. If no company is included in the field or dataset security, the source type “user” will be shown and the companies for which the field or dataset security is applicable.

Authorization request for revoking a single role:When revoking an organizational role, depending on the setup of linked templates, a record could be removed. This was also the case when a user was still linked to another organization role that included a template on the same table. This issue has been resolved.

Action copy from useron authorization request:In an authorization request you can choose the action ‘copy from user’. During this action data was also copied to other open, pending authorization requests. This was incorrect and has been resolved.

Incorrect synchronization of permission sets:Whenever a user has multiple roles and one of the roles is revoked, then it could occur that a user eventually did not have the correct permissions based on his assigned permission sets anymore. This issue has been solved.

Multiple requests for same user:It was possible to create two authorization requests fort he same user. This also meant that users received the authorizations. This has been resolved.

Error on processing requests:An error could occur when processing authorization requests. This has been resolved.

Authorization Box objects separately deliverable: The AB webservice used a report. In case this report was missing, there were issues in compiling the webservice. This has been solved.

Change Name of Permission Set: Changing a permission set name in the permission sets (2C) page resulted in an error. This issue has been solved.

For a new installation see the installation instructions.To perform an update installation from a previous 2-Controlware (= 2CW) version see the table below. The fob’s of version 4.01.01(VM) is available upon request.

1. Import (with replace all) and compile version 2-Controlware 10.02 (“NAVW1x.xx,2CW10.02.fob”).
2. For NAV 2016 and up, the customization of Codeunits 1, 40 and 423 needs to be removed. If you have no other add-ons, you can – after consulting your NAV-partner – replace these Codeunits with the default NAV objects.

Important!

Please be sure to Replace All existing objects. Default action for some objects is Skip or Merge. Furthermore, always check if Menusuite 1052 is available.

In order to setup the User Groups per Competence users need full permissions for the table “ 2C User Group per Competence” and execute permissions on the page “2C User Groups per Competence”.Besides the basic read and execute permissions for the objects, no other modifications for all users are necessary.

Furthermore, any new objects need to be authorized separately if not authorized with a permission line with Object-ID = 0.

To be able to use the new objects you do not have to update your license.

The 10.02 update-package consists of one fob-file:

• NAVW1x.xx,2CW10.02.fob: the objects can be identified by version number 2CW10.02.=== Dynamics NAV version ===

2-Controlware 10.02 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise. Versions for 2013 R2, and 2015 are available on request. Dynamics NAV version 3.xx, 4.xx, version 5.xx, 2009, 2009 R2 and 2013 are no longer supported.

For the new functionality of User Groups in authorization monitoring a new setting is available in Authorization Monitoring Setup. The setting ‘‘Analyses with User Groups’ will give you User Groups in Analysis Permissions (if you use User Groups within your authorization setup).

With this release letter we inform you of the release of the new 2-Controlware version 10.01. This release contains new functionality as well as bug fixes. 2-Controlware 10.01 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise. Versions for 2013 R2 and 2015 are available on request. Dynamics NAV version 3.xx, 4.xx, version 5.xx, NAV 2009, NAV 2009 R2 and NAV 2013 are no longer supported. It is necessary to update your NAV license to be able to use the updated and new objects.

2-Controlware 10.01 has a lot of new features and incremental improvements on the existing functionality. Furthermore, several bugs are fixed. See below a description of the most important changes.

Summary Secured Fields and Dataset per Source: It is possible to calculate two overviews containing a summary of the:

• Secured fields per source
• Dataset Security per source

These summaries can be used for analysis / justification of the authorization setup.

Depending on the “Show fields in summary” setting within the Field and Dataset security setup, only fields from the security are shown in the calculation, or all fields with access in the secured tables. Navigate to Compliance/Security/Field and Dataset Security/Summary of Secured Fields per Source and click Calculate summary in the ribbon. The system will then determine which permission sets, organizational roles, and users are included in the different security. The calculation is only performed on active field Securities (start date < current date). The overview can also be calculated for Dataset securities. To do this, click the Calculate summary button Dataset Security per Source. Here, too, you get an overview of permissions, organizational roles and users who are linked to one of the secured Datasets.

Improved performance processing authorization: Technically, a number of adjustments have been made so that authorization requests can now be processed faster.

Pre and Post actions when updating employee authorizations: Pre and post actions are executed before and after processing an authorization request. It has now been made adjustable whether this should also be the case when updating employee authorizations. The setting can be found on the organizational dimension value “Execute actions on update”. Here you can set what is desirable for the relevant organizational dimension value.

Free fields on employee authorizations: Within the authorization management Pro settings, free fields can be set for the authorization request line. These free fields could not yet be used on the employee authorizations. The fields are now available. If desired, the user can add the available columns.

Capture Confirm: It is not desirable for pieces of code to request confirmation for processing through a job queue. For this, a CONFIRM has been replaced by a GUIALLOWED in codeunit 11111997.

Status in user management: Within authorization management, users 2C, the status of the user account has been added. This makes it easy to see which users are active. Note: for an up-to-date overview it is important to renew the users regularly via the button “Refresh users”.

Temporary tables for Limited Users: A Limited User can only use a limited number of tables. Previously, various tables were filled by the system when logging in. This has been adjusted. In the new situation, the temporary tables are used, so that a Limited User can now log in without any problems.

Evaluation Windows groups in monitoring: Analysis results on Windows groups can be reviewed. In the old situation, this review was not passed on to the linked users. This issue has been resolved so that all users within the group are now provided with the review.

Special characters within table relations: Field validation was unable to properly handle special characters in values to be validated. This has been resolved so that it no longer causes problems.

Incorrect description of mandatory fields notification: If a minimum and maximum length was set for a field within mandatory fields, the system did not always correctly display that length. A length of 10 characters was shown in the description as 1. This issue has been resolved.

Missing SID within monitoring: There are cases that a user has no SID associated with it. If this was the case, the system gave an error when analysing the standard Competences. This has been adjusted so that the error is now addressed and the analysis can be completed.

Non-editable fields on authorization request: The fields under the integration fastbox were non-editable when creating an authorization request. This was wrong and has been corrected.

Validate employee number for authorization request: When creating an authorization request, the employee number was not validated for an existing employee. This has been adjusted so that the current employee data is now on the request.

Dates by action copy from user: The 'Copy from user' function can be applied to an authorization request. Authorizations from another user are then included in the request. The dates of the request from the other user were also adopted. This has been adjusted so that now the current dates are used.

Status authorization request after rejection: Authorization requests can of course also be rejected by the approver. In the old situation, the status of the application for authorization remained “Waiting for approval”. This has been adjusted. After the approval request has been rejected, the authorization request will be given the status “Open”. Under the approvals, you can see who rejected the request and when.

Status authorization request after approval: If a request to approve for an authorization request is approved, the status will remain “Waiting for approval”. This has been adjusted. Once the application has been approved, the status will be “Released”.

Issues in Monitoring: There were some issues within the monitoring functionality. So gave the system an error message as soon as you clicked on het details of the analysed permissions. Another problem arose as soon as an analysis was performed without filters being specified for the calculation. The analysis report was also unable to deal with a complete analysis of all the standard competences. These issues have been resolved.

Missing license check: If only Essentials was included in the license, it was necessary to give everyone read permissions to TableData 2C Compliance Setup. An adjustment has now been made for this, so that it is no longer necessary.

Object Explorer and Tenant Permission Sets: Object Explorer can identify a permission set for an object. Because the new versions of Dynamics NAV / Business Central also use the Tenant Permission (2000000166) and not only Permission (2000000005), not all sets were visible in the overview. This has been adjusted. For this purpose, the column “No. of linked tenant permission sets” has been added. There the tenant sets and objects are visible (user-defined type and extension type). The permission sets of the type system are visible in the column “No. of linked permission sets”.

For a new installation see the installation instructions.To perform an update installation from a previous 2-Controlware (= 2CW) version see the table below. The fob’s of version 4.01.01(VM) is available upon request.

1. Import (with replace all) and compile version 2-Controlware 10.01 (“NAVW1x.xx,2CW10.01.fob”).
2. For NAV 2016 and up, the customization of Codeunits 1, 40 and 423 needs to be removed. If you have no other add-ons, you can – after consulting your NAV-partner – replace these Codeunits with the default NAV objects.

Important!

Please be sure to Replace All existing objects. Default action for some objects is Skip or Merge. Furthermore, always check if Menusuite 1052 is available.

In order to use the new field- and dataset security Summaries provided in this release, users need full permissions for the tables “2C Summary Sec Fld per Source” and “2C Summary DS per Source” and execute permissions for the pages “2C Summary Sec Fld per Source” and “2C Summary Dataset per Source” and the reports “2C Calc Sum Sec Fld per Source” and “2C Calc Sum Dataset per Source”.Besides the basic read and execute permissions for the objects, no other modifications for all users are necessary.

Furthermore, any new objects need to be authorized separately if not authorized with a permission line with Object-ID = 0.

To be able to use the new objects you need to update your license. You can ask your Dynamics NAV partner to update your license.

The 10.01 update-package consists of one fob-file:

• NAVW1x.xx,2CW10.01.fob: the objects can be identified by version number 2CW10.01.=== Dynamics NAV version ===

2-Controlware 10.01 is available for versions 2016, 2017, 2018 of Dynamics NAV and Fall ’18 (R13) and Spring ’19 (R14) of Business Central On Premise. Versions for 2013 R2, and 2015 are available on request. Dynamics NAV version 3.xx, 4.xx, version 5.xx, 2009, 2009 R2 and 2013 are no longer supported.

For the new functionality of the summary secured fields a new setting is available in field and dataset security setup. The setting ‘Show fields in summary’ will give you only the fields in the field security or all the fields with access (for tables in the field securities).The setting ‘Execute actions on update’ on the organization dimension value is added for the update employee authorizations. The options are:

• All actions
• No actions
• Only pre actions
• Only post actions