| Month | Date | Week | Month | Date | Week | Month | Date | Week | ||
| JAN | 1 | n.a. | FEB | 12 | 7 | MAR | 12 | 11 | ||
| JAN | 15 | 3 | FEB | 18 | hotfix | MAR | 26 | 13 | ||
| JAN | 29 | 5 | FEB | 26 | 9 |
| Month | Date | Week | Month | Date | Week | Month | Date | Week | ||
| APR | 9 | 15 | MAY | 7 | 19 | JUN | 4 | 23 | ||
| APR | 23 | 17 | MAY | 21 | 21 | JUN | 18 | 25 | ||
| Month | Date | Week | Month | Date | Week | Month | Date | Week | ||
| JUL | 2 | 27 | AUG | 13 | 33 | SEP | 10 | 37 | ||
| JUL | 16 | 29 | AUG | 27 | 35 | SEP | 24 | 39 | ||
| JUL | 30 | 31 |
| Month | Date | Week | Month | Date | Week | Month | Date | Week | ||
| OCT | 8 | 41 | NOV | 5 | 45 | DEC | 3 | 49 | ||
| OCT | 22 | 43 | NOV | 19 | 47 | DEC | 17 | 51 | ||
The Authorization Box was updated on April 24. Below you will find the changes in this release.
Option to change the company of the webservice call that is used to insert a record into a table.
A new field for the Company is added to the Master Template header and the Authorization Template header. With this new field you can overwrite the Company used in the Connection URL to insert a record to a Non-Company table. If the table is by default a "Data per Company" table, this new field will not be visible.
Delete column has been added to the import file for Integration Data.
A "Delete" column is added to the "Integration Data" sheet of the Organization Chart export/import file. This way a User can mark an integration record as "to be deleted" from the integration data in the Authorization Box.
The Authorization Box was updated on April 9. Below you will find the changes in this release.
Option to add a non-key field to the INSERT action of a Template.
An extra field has been added to the Template Line, to indicate that the field should be part of the INSERT statement. This way you can add a non key field to the INSERT statement when a value for this field is required to be able to create a new record in Business Central.
The Authorization Box was updated on March 26. Below you will find the changes in this release.
The Authorization Box was updated on March 12. Below you will find the changes in this release.
Multiple queues for different types of User Syncs
When an authorization sync is performed, this can result in a lot of user syncs. These syncs fill up the processing queue and as a result a user sync that is triggered by an authorization request is added to the end of the queue and takes a lot of time to be processed.
To prevent this issue, we created separate queues for the different type of user syncs. This way an authorization sync or a full sync of a database connection can not get in the way of the regular user syncs that need to be processed as soon as possible.
Analysis results per Organization Role
On this new page, the Monitoring analysis results can be reviewed per organization role. This brings the presentation of the analysis results more in line with the way with how permissions can be maintained from within Authorization Box.
For each organization role, it is shown to which users the role is assigned and which permissions a role has based on the research questions/the critical permissions.
For additional information, please see this page of our wiki.
Add "Authentication Email" as field of Value Source type "User"
You can now use the user's Authentication Email as a value source for a Template. This way you can use the Authentication Email, which is the User's primary email address, to write data to other tables.
The Authorization Box was updated on February 27. Below you will find the changes in this release.
User is not automatically deactivated when he was activated with an End Date
When you create an Authorization Request and activate a User for a certain period, the request will have a start and an end date.
The User will now be deactivated on the given end date of the request and a Synchronization Log for the User of type "Scheduled sync" will be made.
The Authorization Box was updated on February 18 with a hotfix to prevent deletion of data in table 91 during the nightly synchronization.
The cause of the incident was a programming error that was not detected by our manual and automatic tests.
The specific scenario in which the error occurred was not identified as a test scenario.
We have improved our testing process to avoid similar mistakes in the future.
The Authorization Box was updated on February 17. Below you will find the changes in this release.
Unfortunately this release resulted in an incident as for some companies the user settings were removed during the nightly synchronization.
The impact varied per company, but in the most cases it resulted in a restricted access in Business Central for users.
We noticed the incident on Tuesday February 18th at approximately 08:30 hrs CET and took immediate action by supporting customers in recovering deleted data and developing a fix to solve the bug.
Our sincere apologies for the inconvenience caused by this incident and we are doing our utmost to prevent anything like this could happen in the future.
Navigate to the User page from the Organization Role page.
It is now possible to navigate to the User detail page by clicking on a user in the Users overview on the Organization Role page.
Activate a User that is to be deactivated in the future.
It is now possible to correct the deactivation of a User if that deactivation is to be performed in the future. This way you can prevent that a User is deactivated by cause of an input error. In a new authorization request you can click on the checkbox of the deactivation and input a new deactivation date by choosing a new end date of the activation. This way it is also possible to reverse the deactivation fully, by omitting a (new) end date of the activation.
Add an Approval Template on User level to overrule the Approval Templates on Organization Role level.
It is now possible to overrule the approval settings for a User on a user level. When you create an Authorization Request, you can select a user level Approval Template. This Template overrules the Approval Templates that are assigned to a User on an Organization Role level. So, when you have a temporary User, for instance an intern, you can assign the same Organization Roles as for a regular User and use a separate Approval Template to set the approval amount to €0,00.
The Authorization Box was updated on January 29. Below you will find the changes in this release.
The Authorization Box was updated on January 16. Below you will find the changes in this release.
Remove the Permission Set recorder functionality from AB
The Permission Set recorder functionality has been removed from the Authorization Box. To record Permission Sets you can use our Compliance Advanced Permissions Recorder app, which can be downloaded freely from AppSource or from our Partner portal.
For more information on how to use the Compliance Advanced Permissions Recorder, please see this page of our wiki or watch our presentation on YouTube
Search for Object Id 0 in the Object Explorer
When the "Id" field has value 0, the Object Explorer searches for objects that have Id 0 in the Permission Sets. When the "Id" field has no value, the Object Explorer lists all objects, including the objects with Id 0.
Add new "authorizationRequestLineCode" property
The responses of the GET Authorization and GET ProcessedAuthorizationRequestLine endpoints of the Authorization Request API are expanded with an "authorizationRequestLineCode" property. This way the response of the GET ApprovalRequest endpoint can be linked to the responses of both endpoints mentioned.
Update the Permission Set cache when a User creates, updates or deletes a Permission Set
The Permission Set cache is automatically updated after a user has created, updated or deleted a Permission Set. This way changes are immediately vissible without the need to manually refresh the cache.