complianceapps:1get_started:1whats_new

  

What's New

Every six months we update our Compliance Apps 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 hotfix we fixed some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation:

  1. New pages instead of standard pages for web services: We have added some new pages that are used for views in the Authorization Box. Before, standard BC pages where used;
  2. Table Relation on flowfiield for validation on Related No. of Records: it is now possible to use a flowfield in the setup of a Table Relation. This Table Relation can be used in a Field Validation or Filter Security;
  3. Length Number Series: A No. Serie with more than 10 characters gave en error in Field and Filter Securities. This problem is solved;
  4. AB Batch Action Buffer: when using User Templates in the Authorization Box, an error could arise regarding to the Batch Action Buffer. This bug has been fixed.

With this hotfix we fixed the following issues:

  1. The usage of IsolatedStorage by our apps could lead to locking problems. We have solved this problem;
  2. In Field Validation, validating on empty values did not work as expected.

With this release we fixed some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. The new version is 2.1.20210401.0. Below you will find the most important issues and features.

General

  1. All apps are now Microsoft Dynamics 365 Business Central Wave 1 2021 (BC18) compatible;
  2. The version number from the extensions are now conform Microsoft rules. The new version is v. 2.1.20210401.0 based on year.wave.date.version;
  3. The webservices have been expanded for the connection with The Authorization Box;
  4. Technical adjustments have been made in preparation for additional functionalities in the Authorization Box;
  5. Translation issues are solved.

Field Security

  1. The logic of our Field Security App is changed. In the old situation the security was valid for all users with the permission sets that were defined in the Field security line. The security could be overruled when the user has another not linked permission set with at least insert rights of the same table where the Field Security was set for. In the new situation the user needs a not linked permission set with modify permissions to overrule the Field Security;
  2. Also Filter Security is valid for all users with permission sets that are defined in the security. This is not the case if a user also has another not linked permission set with insert, or modify, or delete rights;
  3. Now Filter Security also works when you use the URL to go directly to a page with Filter Security;
  4. New events are added for regular used pages so you can setup more visability security filters;
  5. Summary of Field Security per Source and Summary of Filter Security per Source are optimized. With this functionality you can easily generate an overview including the users who are linked to the security settings. The Authorization Box also uses this information so that it can be shown within the analysis results for critical permissions;
  6. There were some issues with loading default data. In the old situation it could be that when loading default data into the Field Security settings, the settings in the action security were removed. This issue is solved.

Field Validation

  1. When validating default dimensions now the current value of dimensions is also shown in the error message for an better understanding of the error;
  2. In a Field Validation you can use a related table in the conditions. Now the trigger is no longer executed by default when the field is updated in the related table. You can change the setting in the conditions by the checkbox Execute validation on Related Table modifications;
  3. We have added the column Default Notification in het Regular Expression to make the validation messages more understandable for endusers.

Upgrade Instruction

You can upgrade to this version as follows:

1. Cloud/AppSource: Follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrade-appsource-app-in-prod;
2. On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions#running-the-upgrade-for-the-new-extension-version.

With this release we have made all of our apps compatible to the Microsoft Dynamics Business Central 2020 Wave 2 release, fixed some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. The new version is 1.2.0.20201027. Below you will find the most important issues and features.

Essentials

  1. Load Default Data: from the page Table Relations you can now load default data. Click on the action Load Default Data to load our default Table Relations. Note: It is possible to load data several times.
  2. Table Lock Isolated Storage: The interaction with the system table Isolated Storage could cause deadlocks. This is significantly improved.

Field Security

  1. Multiselect Permission sets: When linking permission sets to a field, filter or action security, it is possible to select multiple permission sets so that they are linked to the correct security line in one action. In the permission sets screen, click on the dots, select more, and select the rows you want to link.
  2. Licence Information: The licence information for the extension is improved. You can see the Status, Registration Date and when the Trial Expires. With a contract you can see the Contract Start Date and the Contract End Date.
  3. Load Default Data: From the Field Security Setup and the Field Security Wizard, you can now load default data. Click on the action Load Default Data to load our default Table Relations and to load the Page and Action event subscriber information. Note: It is possible to load data several times. With the Action event subscribers, the linked Permission Sets will be overwritten so use this only a second time when needed.
  4. Exclude Inactive Action Events: Inactive Action events (related to issue https://github.com/microsoft/AL/issues/942) are no longer subscribed to in our Action Subscriber Codeunit.
  5. Filter on Field Security: A filter on the Field Security (header) did not always work. The problem is solved.
  6. Field Show Permission Sets: The field Show Permission Sets in the Field Security Setup did not work as expected, this is solved.
  7. Related Filter Security: The releated filter security did not work as expected, this is solved.

Field Validation

  1. Regular Expression Validation: From now on Regular Expressions can be used as Field Validation. A Regular Expressions is a sequence of characters that define a search pattern for (in this case) input validation. From the Field Validation Setup you are able to load default data (Regular Expressions) that you can use in Field Validations, or you can setup your own validations in the page Regular Expressions. Select in the validation line the Validation Type Regular Expression, select the field to validate and select from the field Regular Expression the validation that you need.
  2. Load Default Data: From the Field Validation Setup and the Field Validation Wizard, you can now load default data. Click on the action Load Default Data to load our default Table Relations and to load the demo Regular Expression codes. Note: It is possible to load data several times.
  3. Permissions in 2C-FIELDVAL-USE: To use Field Validation you need the Permission Set 2C-FIELDVAL-USE. In this Permission Set we have added two permissions that were missing: Table 70196825 and 70196826.
  4. Check Overview: The Field Validation Check Overview page did not expand and collapse as expected, this is solved.

Upgrade Instruction

You can upgrade to this version as follows:

  1. On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions#running-the-upgrade-for-the-new-extension-version
  • complianceapps/1get_started/1whats_new.txt
  • Last modified: 2021/07/08 12:13
  • by rogier