We have added support for the use of comma's in keyfields of an F&O entity.
By adding an autocomplete field we have made it easier to select te business entity property name in a storage rule.
The gallery refresh button refreshes the gallery contents. This has been improved by making sure it adds and changes content as soon as possible, but only starts deleting shown content from the gallery when the refresh is over and we are sure that content is no longer present. This gives the user a smoother experience.
Changing the storage connector location from the UI is no longer possible. When this location would be changed for a storage connector with data linked to it, that data would become unavailable.
Newly added users could get a '403 Forbidden' error when logging in the first time. This has been fixed.
Storage rules based on business entity properties which are numeric or which have numbers in text fields could be evaluated incorrectly. We have fixed this by parsing values to the expected data type (text, number, date, boolean, etc.)
Content items linked to multiple business entities could be missing some business entity references when viewing them in the gallery. This has been fixed.
Due to a cache that did not take into account the user license, some read-only users where allowed to perform write actions (if there base permission set allowed it). We have updated this cache so read-only users also only get read-permissions in the cache.
Switching between Content Gate environments was difficult and could require manually clearing cookies. This has been improved by allowing a user to retain different cookies for different environments. Users can now be logged in in different environments (e.g. sandbox and production) without any problems. Logging into multiple environments with different users is not possible within the same browser session at the same time and will require the user to re-login on every switch.
When using special characters in an entity model name (such as a '.'), these characters are now automatically replaced with a '-'.
When configuring a SharePoint connector pointed towards a folder, upon connect we now validate that this folder (and not only the library) exists.
When a user deletes content, Content Gate will check if that content is linked to any other entities besides the one the user is currently deleting from. If this is the case, the user will see a warning stating that deletion of this content will delete the content from all the linked entities.
A few scenarios where views have a recursive entity (e.g. project -> subproject) were not working properly. The main scenario is a view with a recursion, where the entry point is an entity related to the recursive entity. In this case only the first entity of the recursive entity (and no parent or child entities) was loaded. This has been fixed and multiple recursion scenarios have been added to our test suite for continuous automatic testing.
When users cannot edit the category for a new upload, this resulted in a false error stating that the category field was invalid. This has been fixed so when users are not allowed to edit the category, but the category has a default value, the user is able to continue the upload.
When storage rules were created with a business entity property, but a business entity was opened that did not have this property, the evaluation was skipped for this part of the rule which could evaluate the rule wrong. This has been corrected by evaluating any storage rule with a business entity property to false if the entity does not have that property.
The Content Gate documentation page could throw an error on the first time the page was viewed. This has been fixed.
It is no longer possible to delete a storage provider from Content Gate if there is Content stored in it.
When viewing content, in some edge cases, the Save button could be enabled even when the user did not change any data. This has been fixed.
The power platform connector expected all user property values to be strings. This has been corrected so other value types are also allowed.
In some occasions the wrong category was checked when performing actions, which could lead to different permissions for a user. This has been fixed.
Storage rules can now be configured with category and/or business entity properties. This allows Content Gate to choose the storage location based on any property in the business entity where the document is uploaded to. An example use case is to map the storage location based on the dataAreaId in Finance&Operations.
A button has been added to the document list to print one or more documents directly from within Content Gate. To be able to print a document the user needs the 'Download' permission for that document.
Previously only view filters on system properties (e.g. category) were exported and imported. As of this release also filters on custom properties are exported and imported.
The cache that checks whether a user has access to a certain business entity has been improved for faster reads and writes. To disable the business entity check completely go to the admin section under General Settings -> Security.
When checking a lot of permissions (e.g. when listing all categories a user has access to), this operation could take quite some time. This has been improved so a summary of a users permissions can be accessed quickly most of the time.
In some cases the filename placeholder for a title was not resolved to the actual filename. This has been fixed.
When using a service principal to execute queries (retrieve documents) in Content Gate, in some rare cases an error would occur when retrieving an access token for this principal. This has been fixed.
Our browser application has been updated to the latest version of the Angular Framework.
It is now possible to export and import Content Item Template Groups and Content Item Template notifications between different Content Gate environments
The diagram showing all business entities and there relations did not load properly sometimes, this has been fixed.
When importing a configuration with view filters which filter out documents by category, those filters might not be mapped properly if the category ids between environments differ. This has been fixed so categories between environments are always mapped by name.
When querying documents using the /api/query/.../fromContext endpoint users would get an error. This has been fixed. This endpoint is not used by the Content Gate web application itself.
The Azure API versions used when deploying new Content Gate environments have been updated to the latest version.
Fixed an issue where a query would trigger an error. This error only happened on rare occasions where service principals run a query and that query does two conflicting actions concurrently.
Validating if the title template has not been changed by the user fails when the title contains the filename placeholder and the document has been uploaded via a content request. This has been fixed.
When using environment colours, the external request screens background colour would take up most of the screen. This has been improved so it only has a coloured border.
It is now possible to cache the results of a view, for improved performance. This can reduce the time to load documents by a lot for heavy views. Settings to enable this can be found under the 'Caching' tab in a views configuration. This allows users to retrieve and interact with documents instantly, while the latest changes are refreshed in the background. Icons clearly indicate when a document has been loaded from the cache (and thus might be outdated). Since Content Gate does not store the document, the user always sees the latest version of a document, regardless if the view query has been resolved via the cache or not. If a document is returned from the cache but is actually deleted from the storage location, the user will get a clear error message when trying to view or download the document.
It is now possible to export and import Content Item Templates and its properties between different Content Gate environments. Support for exporting and importing of template notifications and template groups will be added in a later release.
Updated the documentation page to include a separate link to the documentation for Content Gate with Business Central.
In the rare scenario where a lot of documents, belonging to a lot of different business entities are shown in a view, the browser could be 'overloaded' with changes when loading the view. This has been improved by better processing these changes in bulks.
We have updated the Content Gate Power Platform connector. This connector includes an action to call the content entities search endpoint in which you can search content entities across the entire system. This action is a basic (v1) version. More information about the search endpoint and how to use it can be found in the documentation.
We have added support to add a SharePoint folder to a storage connector, which enables you to store and retrieve documents from folders instead of the root of a library.
When a SharePoint library has a different name than title, the URL cannot be generated from the title. We have added functionality to retrieve and use the name, so it always generates the correct URL.
We have made a lot of small tweaks in the code, optimizing the use of asynchronous tasks, which enable the application to better divide and handle the workload.
When a business entity could not be retrieved from the external system, the error message now makes clear if the business entity was not found or was not accessible due to missing permissions.
In a recent version of Finance & Operations customers where getting an error when connecting the Business Entity Connector in Content Gate. The problem was in a version check on our side. This has been fixed.
Some views in a Business Central setup where not retrieving all the fields necessary to complete the view query and retrieve all business entities. This has been fixed.
External users where getting an error when upload content to a content request, due to a check to the external business entity system to which these users do not have access. We have removed this check, which was unnecessary for the upload to complete.
Preparations have been made to allow the application to automatically scale up resources whenever the application needs it, e.g. when the workload gets too high for the current amount of resources. These preparations include the use of a distributed cache instead of local in-memory caches. Auto-scaling will be enabled in a later release.
When a template title has a placeholder which is replaced with the filename after an upload, this placeholder is not replaced if the upload is done via a Content Request. This issue has been fixed.
Logging of certain queries has been improved to better monitor the system.
We have changed the namespace of the Content Gate SDK and uploaded this 'new' SDK NuGet package under the publisher signupsoftware. The previous SDK which was published under AXtension has been deprecated. There where no changes in functionality so it's possible to simply replace the old SDK with the new SDK.
In the previous release there was a small performance degradation, caused by functionality that was calling an external service too many times instead of using the appropriate cache. Functionally nothing was broken, but we have added a fix which improves the performance of some requests to Content Gate.
Selecting a dropdown with autocomplete was not working properly. This has been fixed.
When editing the fields of a shared identifier, the table did not reflect the latest changes. This has been fixed.
Expected content items where not shown if a views content was filtered on category. This has been improved to show the expected content item if the underlying template has the allowed category or has no category specified.
All customers in the same region will now login to the same reply url (e.g. europe-02.content-gate.com/...). After successful login they are redirected again to their own customer-specific url.
It is now possible to use guids as keyfields in entities used in Content Gate.
When exporting views, any filters in the views content properties are also exported in the configuration. When importing the views these filters are also imported. The only exception is filters on custom content entity properties, which are not yet supported for importing.
When exporting and importing views, the permissions where exported but not imported. This has been fixed.
We have migrated to Angular 18.
Loading business entities within Content Gate (this happens for instance when opening a gallery) has been improved with quicker load times. To enable this we enforce some limitations on the business entity.
When a browser window was zoomed in or out, the content preview did not scale along. This has been fixed.
When the template feature was enabled, the dialog to upload new documents did not show any properties like the category. Also saving a document which contains read-only properties could throw an error. Both scenarios have been fixed.
In the previous version we added support for special characters. This version includes some minor fixes, for instance for encoding white spaces. Also we have made a list of specifically supported special characters. Characters outside of this list might work, but are not tested nor guaranteed to work in every scenario.
Supported characters: /#=-&().:[]_%
We have migrated to Angular 17.
We have migrated all (form) components to version 17 of Angular. Normally this is just a technical improvement, but this time the layout also changed.
We have rebranded everything to the SignUp Software layout.
When importing categories the permissions were not imported correctly. This has been fixed.
The overriding of the default value was not working correctly. This has been fixed.
When filtering on specific values (e.g. a # in a name) this was causing issues. This has been fixed.