We are halfway through 2023 and Onspring has done it again…twice.
In Onspring’s two latest releases (v24.0 on January 28 and v25.0 on June 17), the GRC platform has provided their user community with a collection of new and meaningful features that greatly enhance its collective problem-solving capabilities in the Onspring Platform.
At Cential Consulting, we understand the “Eyes on the Prize” mentality that often drives our clients. Many GRC professionals are focused on addressing their immediate and ongoing “day job” priorities and may not have much, if any, time to digest the new Onspring features.
As a risk manager, you may find yourself in a similar situation, asking:
- Where and how should we use the new features?
- How can we get a quick win?
- What existing capabilities do the new features work well with?
That’s why we wrote this blog article: to give you a simple yet informative summary of what these new Onspring features offer and, more importantly, how they can help you solve problems you may not even realize you have.
Some of the new features are obvious, while others are a bit more subtle, but the constant theme is that both of these new Onspring releases are chock full of useful tools that stand to make the lives of GRC professionals a bit easier.
Overview Of The New Onspring GRC Features
|Version||Feature||Plain Language Summary||Problem Solving Power|
|24.0||Survey Page Visibility||Dynamically dictate which survey questions you want to send or hide based on who you’re sending them to.||Sending a Risk Assessment to a Vendor who doesn’t provide cloud computing services? No need to create multiple surveys – simply add a rule to hide the Cloud Computing question page for vendors who don’t need it.|
|24.0||Custom Layouts in Workflow||Create multiple layouts for a single app or survey that present only the most necessary information to reviewers at each workflow stage.||Engaging an Executive in your Finding review process? Create a layout that eliminates the “noise” and only gives them the information they need and assign it to their workflow step.|
|24.0||New Key Metric Displays||Engage users with a wider variety of meaningful and measured summaries of data on your dashboards.||Want to track progress achieving a specific goal? Use a Dial or Bar metric to measure how you’re faring.|
|24.0||Embed Reports in Dynamic Documents||Present reports alongside record content to create enhanced deliverables.||Creating a summary report for your Board? Include a visual representation Finding Progress alongside key report context.|
|24.0||Set Reference Outcomes via Multi-Select References||Configure Set Reference Outcomes that can reach through multi-select references and auto-populate other shared multi-select reference fields.||Targeting multiple risks in an engagement? Use this feature to auto-relate all controls related to those risks to drive engagement level evaluations.|
|25.0||Automated Workflow Enrollment||Allow formulas and other system actions to drive workflow enrollment logic.||Want to ensure Exception Requests are reviewed as they approach their expiration date? Use a formula-driven expiration date to enable re-enrollment in workflow.|
|25.0||Automated Step Routing||Allow content to move to the next stage in workflow if they’re not touched by a reviewer in a certain amount of time. Or eliminate the need for direct user interactions in a particular workflow step.||Speak now or forever hold your peace: Give users the ability to approve or reject a request, but automatically approve the record if they don’t protest in the designated time frame.|
|25.0||Packaging Support for Workflow||Update workflow configurations via package migration and enable admin users to handle any exceptions created by the new configurations.||If your Contract Approval process no longer requires a review step, eliminate that step and use the packaging feature to decide where any impacted content records should land.|
|25.0||Field Security Enforcement in Workflow||Set a simple flag in your workflow steps to ensure reviewers are only seeing or editing the fields they have rights to no matter the situation.||If you don’t need your reviewers seeing or editing certain fields, you no longer have to worry about workflow giving them this ability (but you can still give it to them if you want to).|
Want to stay on top of all the relevant GRC platform updates? Follow us on LinkedIn.