EM Release Notes

welcome to entity management 4 0! we're excited to introduce a range of enhancements aimed at improving user experience with this release, developers can take advantage of streamlined apis, enabling faster and more efficient project integration additionally, improvements in consistently rendering dates and aligning api and ui validation ensure a seamless user experience read more below about how we are reinforcing our dedication to delivering a robust and reliable software solution table of contents release overview what's new entity management 4 0 simple apis zero downtime upgrades streamlined, out of the box upgrades what's improved configurable date rendering aligned api & ui validation independence integration updates reduced upgrade duration what's fixed dashboard entity details entity history entity import entity search my tasks workflow definition workflow routing known issues the entity management (em) product 4 0 release provides new simple apis that make it easier to use workflow, search, and transition apis the new apis require less information in the request and no longer return unnecessary fields the release also includes the configuration of date fields in entity details, updates to the default time for review due date, and the enforcement of api and ui validation by introducing two new rules our clients can also experience zero down time during minor releases and no impact to their use of the product during deployments what's new discover the latest additions to our software, an offering designed to improve your functional experience explore simplified apis and improved upgrade procedures, designed to make integration, transitions, and updates smoother and more efficient than ever before this release includes the following new features entity management 4 0 simple apis zero downtime upgrades streamlined, out of the box upgrades entity management 4 0 simple apis new entity management apis https //kingland atlassian net/wiki/display/rmpep/entity+management+simple+apis help simplify and improve the developer experience existing apis will not undergo any changes to allow time for clients to transfer over to the new apis new workflow apis make updating and creating entities and associations less cumbersome by only needing to provide changed or required fields new search apis make it easier to search for entities, users and workflows by providing more versatility in request and response details while removing unnecessary fields a default sort order is used to make it easier to sort through paginated search results the new workflow transition api makes it easier to perform workflow task transitions and approvals by requiring less details in the request the new apis allow reference data values to be used in the workflow requests to create or update an entity or association in addition, reference data values are provided in the api response to help reduce the number of call backs a 400 response code is provided when a request is missing required fields, and a workflow batch will not be created if a validation rule fails when creating or updating entities and associations we suggest transitioning your integrations to use these apis eventually, in an future release, we will remove documentation and support for the old apis kingland will provide further details and collaborate with you when determining an official date for discontinuing support of the old apis zero downtime upgrades our clients can expect zero downtime during minor release version deployments and no impact to the existing client experience down time is only permissible for major release version or exceptional security events and will be communicated ahead of time streamlined, out of the box upgrades out of the box upgrades will allow entity management to be deployed with features toggled on/off with no impact to the current functionality our clients can expect no impact to their use of the product during deployments and will no longer have client release fix versions what's improved explore the improvements and optimizations we've made to existing features, aimed at refining your interaction with em dates are now optionally configurable in ui and notifications, ensuring clarity and consistency throughout your user experience refinements to enhance current functionality will be made to these areas as part of this release configurable date rendering aligned api & ui validation independence integration updates reduced upgrade duration configurable date rendering with our new configurable date rendering https //kingland atlassian net/wiki/display/rmpep/entity+management+configurable+date+rendering , the date fields in entity details and workflow drawer can now optionally be configured by kingland services to be displayed in a date (yyyy mm dd) or datetime (yyyy mm dd hh\ mm\ ss) format kingland will confirm and document the client desired configuration for all date fields if no confirmation is provided by the client, the date fields will be displayed in their default configuration the default time for review due date is being updated to ensure users across all time zones will have the correct review due date displayed this change is persisted to each instance of review due date within the application and does not change existing workflows aligned api & ui validation two new rules have been added to entity management 4 0 that contain all required fields and invalid field formats, respectively the rules dynamically check the ui configuration to enforce the same validation when using apis the new rules will be inactive upon deployment and the client will need to activate the rules when ready to transition to the new format existing product rules that check required fields and invalid field formats will be deprecated in the future, as they are no longer needed due to the new rules this provides a grace period to our clients before they are ready to make the change independence integration updates the attribute fields used to trigger the independence integration are configurable the integration has been updated to send additional restriction types based on the entity restriction locally restricted designation will be sent as restricted audit team restricted and assurance restricted designations will be sent as covered person restricted reduced upgrade duration infrastructure upgrades will result in much faster deployments, requiring no manual intervention and take less than 2 hours to complete what's fixed we take testing releases very seriously and are committed to promptly fixing issues when they are identified the following reported issues have been fixed in 4 0 to provide a smoother and more stable user experience for our clients dashboard when a user does not have permission to view a dashboard widget, a permission denied message will be shown entity details removed the value of tree deactivation from the inactivation reason field when inactivating an entity tree deactivation when manually applied to an entity was causing issues when reactivating a tree local restriction type(s) are now shown on the indirect designation entity history the review due month in entity history was fixed to display the correct month when comparing to other versions entity import a major rejection would occur when importing a file that contained an update to an existing rpv for an entity this has been fixed and the entity import file will be processed successfully entity search no search results were being returned when filtering upon an identifier that contains more than one value this has been resolved to return the appropriate results when filtering upon an identifier my tasks the sender column in my tasks has been updated to display the user that last transitioned the workflow it was previously not showing the correct user when a workflow was pushed back workflow definition the text labeling the transition name in workflow definitions has been adjusted to make it easier to read workflow routing updated the workflow routing logic to use location hierarchy when assigning a batch to a workgroup for instances when a rp does not exist on a batch, or the rp does not have an override location known issues in preparation for our upcoming release, we have found a few issues that have been identified and are currently being tracked by our team rest assured, we are actively working on issues to ensure the highest quality user experience your patience and understanding during this process are greatly appreciated a list of known issues can be found in a separate document em known issues copyright © 2024 all rights reserved