Built to keep you moving

Whether you're specifying on a tight deadline or inspecting fire doors in the field, Openings Studio is designed to keep you moving. It works wherever the job takes you.

This release focuses on flexibility, reliability, and transparency. The mobile app now includes an offline mode, so you can keep working without internet access. On desktop, you can copy pins between PDFs to speed up coordination. Openings Studio will now install with DirectX 12 as the default setting.

We’ve also updated our privacy policy to reflect our continued commitment to protecting your data and being clear about how we use it.

Explore the full release notes to learn more about what’s new in 3.26.

Wishing you the best!

The Openings Studio Team

• Jump to desktop app updates.
• Jump to mobile app updates.

Desktop App Updates

Copying pins from one PDF to another

Received a new PDF after placing all your pins?  No problem!  You can now copy pins between PDF documents.

DirectX 12 will be the default setting

When you install Openings Studio, it will now automatically use DirectX 12.  If you still would like to use DirectX 9, it's still available, but you will need to follow these steps to install it.

XML export for Key Studio in EMEIA

You can now export cylinder data to Key Studio for your projects. This feature is permission-based, so it must be enabled for your account.

Once turned on, you'll find the export option at the bottom of the Reports screen.

Note: This feature is available only for the EMEIA division.

Spec Builder files will default to .docx when exported

On new or updated projects, the Spec Builder will now export Microsoft Word files in .docx instead of .doc.  This follows the change we made in the last couple months for switch all Report files created in Word to .docx as well.

Config changes will re-enable the hardware set correctly

Previously, when you changed an opening from Cased Opening or Borrowed Lite to Single or Pair, the hardware set field would sometimes stay grayed out, even though those configurations support hardware sets.

This issue has been fixed,  Now, when you select a configuration that allows hardware sets, the hardware field will automatically become active.

Mobile App Updates

New offline mode

We’ve added a brand-new Offline Mode to our mobile app, making it easier than ever to stay productive, even when you're in areas with poor or no internet connection.

While working in airplane mode has been possible for years, it wasn’t always clear what features were available or when to use it. This new Offline Mode is designed specifically to give you a more reliable and optimized experience when you're off the grid.

Check out this tutorial to learn how Offline Mode works and how it can help you stay on track, no matter where you are!

Registration

Users can now register for Openings Studio directly through the mobile app. Previously, registration required using the desktop app or a web browser, but now it can be completed entirely on mobile for added convenience.

Note: Registering on the mobile app does not mean that your account has been assigned mobile app permissions. If you believe that you should have mobile app access, but are unable to login after registration, contact support for assistance.

Server/version number on load/login screens

To help users and support teams quickly identify which server and mobile app version is being used, this information is now displayed at the bottom of the loading and login screens.

This update helps reduce confusion, especially since Openings Studio operates across multiple global servers.

Issue codes have been updated

The issues codes for most of the inspections have been revised and revamped to be more in line with each section and remove duplication.  This includes punch inspections, United States fire door inspections, and more.  

Reports that use these issues codes in country where the inspections are in use have been updated as well.  This change mostly just applies to the United States.  Please reach out to support if you any questions about how to run a report with legacy codes vs. the new codes.