Northern.3 Release notes (October 29th 2024)
We are excited to announce that the new BlueDolphin release Northern.3 is out!
It’s been a while since we last posted here, but some great things have been cooking!
We have released the first iteration of one of the most requested features ever.
The new release will introduce a new attribute called Object Lifecycle State, which will allow objects to be classified as either ‘Current’ or ‘Future’.
What is new in iteration 1 of current and future state modelling?
In this iteration, we have introduced a new attribute called "Object Lifecycle State" for every object in your repository.
This attribute can have two values: "Current" or "Future," allowing you to classify objects based on whether they currently exist or are planned for a potential future state.
The "Object Lifecycle State" attribute will be available via OData and directly within reporting upon release, making it easy to incorporate into any reports.
Rest assured, this new addition will not impact any of your existing reports or dashboards.
How does it work?
Existing Objects:
Since it's not allowed to have a '0' value for the object state, all existing objects in your repository will automatically be assigned the value "Current."
If you have been using a workaround, such as naming conventions, to indicate the state of an object, you will need to manually update the property to reflect the correct state (either "Current" or "Future") for those objects.
If you need assistance with this, don't hesitate to reach out to your CSM/AM, who can guide you through the process. Once set, you can switch the state of objects at any time, either manually or via the API.
New Objects:
When creating a new object, the "create new object" dialog will allow you to choose the desired state ("Current" or "Future") during the creation process.
Visual indication of future state objects:
On views, future state objects will be indicated with a star icon.
This star icon will be visible on the left side of objects in the object browser, spider tool and ‘add existing objects’ dialog.
The star icon will allow for quick identification of future state objects without the need to navigate to the object detail pages.
Note: On the objects page there is not yet a visual difference between current and future state objects. This improvement is however scheduled for the near future.
Is This It?
Not at all! This is just the first step in our journey toward comprehensive object lifecycle management.
Expect several upcoming releases over the next few months that will further enhance current and future state modelling.
Many of these enhancements will be closely integrated with our new features around solution design.
Want to learn more about Solution Design and Object Lifecycle? Reach out to your account manager to explore the possibilities.
Thank you for your continued support!
-
The mentioned "…to indicate the state of an object, you will need to manually update the property to reflect the correct state…" is really easy with the ‘edit multiple objects’ feature: https://support.valueblue.nl/hc/en-us/articles/202919801-Edit-multiple-objects
2 -
How are permissions for this features implemented? I do not see any options in the roles and permissions?
0 -
Dear M.Suurmond ,
Thank you for your patience, and apologies for the delay in getting back to you.Regarding your query, the ability to update the lifecycle state of an object is linked to permissions for creating and deleting the object. In essence, any user with permissions to create or delete an object also has the ability to update its lifecycle state.
For further details, please refer to the documentation here.
Should you have any additional questions or need further clarification, please feel free to reach out.
Regards,
Team ValueBlue
0
Please sign in to leave a comment.
Comments
3 comments