Weekly Patch - April 21, 2024
🐞 Bug Fixes 🐞
User Authentication & SSO
- User-Agent header has been added to OAuth provider API calls
This week we've got a few updates in addition to our usual bugfixes, making some improvements to our new resource creation system, as well as some general email updates!
Spring has officially sprung! In the spirit of the season, Centercode is also springing forward, with this month’s focus being on a redesign and refresh of our GoEarly program, making it easier than ever to provide feedback and shape the future of upcoming Centercode releases!
announcements
This month the focus is on our newly revamped GoEarly Program, freshly redesigned to streamline your access to upcoming releases while amplifying the value of your feedback. With this revamped structure, you'll now have access to up to three distinct Centercode sites at all times: your unchanged Live Site, a Stage Site (if included in your license) for testing new processes and configurations against production code, and an opt-in GoEarly Beta Site exclusively for exploring forthcoming features. The Beta Site, private to your team and pre-loaded with demo data, provides an opportunity to test monthly releases ahead of schedule, enabling you to provide feedback and shape the development process before these features reach your Live Site in a zero-risk environment!
In the new GoEarly program, we'll be implementing Centercode's structured Delta methodology in a continuous project format. Regular weekly patches will ensure that all three site types are kept up-to-date with bug fixes.
Your participation in the GoEarly Program is crucial in shaping Centercode's evolution, so please join us for the next testing phase that starts on April 1, 2024! Click here to check it out!
The first set of features we’ll be introducing into the 2024 GoEarly program is a more feature rich, streamlined, and intuitive new way to embed a wide range of custom and preset embed options for many popular external video, social media, and scheduling tools (with many more to come!) into your Centercode resources (content, releases, and activities).
We’re excited to get this new tool into your hands and hear what you’ve got to say about it, so get in there and get testing!
It’s February, and love is in the air! In the spirit of the season, Centercode’s February release brings you a whole new way to get your heartfelt feelings (and important test info) out to your testers with a totally revamped resource/content creation system. We’ve updated and streamlined the content creation process and added a bouquet of new options and features along the way to get your content looking better than ever before!
new features
Resources (which include content, features, and releases) are the primary way you’ll communicate information to your testers, distribute test-critical files, and give them instructions on what and how to test your product. In this release, we’ve overhauled and streamlined the UI to make the resource creation process more intuitive, added some useful new features, and paved the way for three exciting new resource element types coming down the line!
The first steps in the new resource creation process are to define the resource type from your available types, name it, and define how you would like this content to be accessed. Defining the resource type early in the process gives you a better idea of what the resource will need to contain, and controls which options will be available in that specific resource. One of the handy new features included in this update is a dynamic in-line help box, which defines the functionality of the resource type you have selected, tells how your users will be able to access it, and provides links to further information if necessary.
Once you’ve selected the type of resource you’re creating and how it will be accessed, you'll be presented with a series of checkbox options for all of the types of information your resource can contain. This allows you a finer degree of control over what exactly you’d like to present to your testers. These options update dynamically based on your previous selections, ensuring that you’re presenting the information appropriately and effectively (for example, preventing you from placing files or distributed values in an agreement that the user will only see a single time). Additionally, each of these options include a handy new hover-over description, detailing the functionality and giving a few suggested use-cases!
Selecting any of these options will add the appropriate section below, allowing you to further customize what it will contain. One notable new feature here is the inclusion of the “Inline images” section — a more flexible, first-class way to insert images, spreadsheets, and other information to your testers. This also includes a brand-new “Hero image” function, which will add a full width, banner-style image across the top of your resource!
Finally, you’ll use the “Content/release/feature options” (depending on which resource you’re creating) and “Team access” sections to determine who can see your content, and when (via notices). Two new features here include the two new content options “Use full browser width” and “Render edge-to-edge (both examples featuring a new hero image!). Note: Hero Images are not compatible with the Full Browser Width option.
“Use full browser width” will dynamically scale the page width based on the viewer's browser width:
Here's an example of a Hero Image on a piece of content:
“Render edge-to-edge” will remove all white padding around displayed resources:
Another notable new bit of functionality here is that since you are defining whether a resource is a notice earlier in the process now, the ability to set a content or release as a notice in the “Team access” section will be dynamically enabled or disabled based on your earlier selections!
fixes