New items in April include the ability to use a rich text editor in Next Steps to Close, the ability to filter and sort Field Lens requests by Internal Contact and Support Cases, and a few bug fixes.

New rich text editor options have been added to the Next Steps to Close text box, helping you highlight updates and making it easier to parse at a glance. Bold important deadlines and target dates, underline names you need to remember, or strike through statements to show they no longer matter without deleting history. Be more detailed in your notes, using the rich text features to emphasize important data.

We hope to update additional note fields on the Opportunity to support rich text formatting in the near future. We'll make an announcement when those changes are live!

We've added a new column to the Field Lens table. Follow-up Contact will hold the Technical Alliance team member responsible for validating or processing the request entered. Technical Alliance can now use this column to quickly filter and find requests assigned to them.

You'll also see the Follow-up Contact inside the details of each expanded line item.

For any newly created Field Lens requests that involve an SE Support Case, you'll now be able to see the linked SE Support Case in the table. You can also search for the Case ID to quickly find the request.

In addition, you can see summary info about the linked Support Case and any Partnership Requests in the request description area. Click the expansion arrow to the left of the request title to see more data about the request.

🪲 We've corrected an issue with the average reservation time displayed on the HPOC Activity report.

🪲 SEs in EMEA should not encounter issues when creating new Field Lens Product Enhancement Requests.

🪲 Fixed an issue where Check-In names that were too long could cause errors

🪲 Fixed a problem with certain form inputs not showing the proper values on page load and causing issues when saving changes

🛠️ Made improvements to some of the charts across the app