The Arria NLG Studio 3.8 release is all about efficiency in data-driven storytelling: a more efficient way to preview edits to hierarchical subscripts and faster, easier ways to share narrative output with end-users and everyone across the organization.
When it comes to editing subscripts, we’ve listened to feedback and made it even easier to review your edits as you make them.
Do you ever wish you could create a version of your Studio project that anyone can use – even if they don’t have a Studio account? If the answer is yes, you should be using Studio Runner! Keep reading to find out how you can simplify the workflow from script to shareable document.
Work more efficiently with faster, easier script editing
Scripts are the foundation of the narratives you build in NLG Studio. With one default Main script and the potential for many subscripts, a single project can become an elaborate, structured hierarchy.
If you already work with hierarchical scripts, you know that they are great building blocks for generating narratives, but if you edit a subscript, you need to check how those changes impact the output before you republish the project. Previously, this meant making edits and then returning to the Main script to check the preview.
The latest release now includes a Preview Main button in the Studio interface, letting you edit subscripts and review the main narrative without switching away from the script you’re working in.
This simple change keeps you right where you want to be and speeds up the process of building and revising projects, helping you to work more efficiently. It is especially useful for checking scripts with user-defined functions (UDFs), which you can’t preview directly.
Share the data story straight to a report
In the previous release, Studio Runner included a beta version of an Export to Word feature, letting you share your project with users who don’t have a Studio account and enabling them to import the narrative straight into their own Microsoft Word document.
With only the Studio project ID, API Key, and Studio Runner, anyone can use the correctly formatted data to generate the narrative output from a project. Once they have the narrative, they can copy the text to their clipboard and paste it wherever it needs to go.
Studio 3.8 streamlines this workflow further, now enabling the end-user to send the narrative straight from Studio Runner into a PDF or Word document. Want to add the narrative into a section of a larger report? Simply add a bookmark at the appropriate point in your document and the narrative will be inserted right where you want it, with the most current data insights as often as you need them updated.
Working more efficiently with Studio Runner
If you use a document template, you probably re-use the same one for multiple documents — the Export Narrative dialog now remembers and pre-selects the last-used template in the session, speeding up further exports.
When you use the Studio Runner Export feature, the filename for the exported document is now taken from the project name rather than the template. This means that if you have a report template, you don’t need to keep renaming the file with each export – Runner does it for you.
Want to see how easy it is to export narratives?
Sharing your narratives and delivering data-driven storytelling has never been easier. All users across the organization — even those without Studio accounts or ATL experience — can generate or update reports as soon as the latest dataset is available.
Do you already have a Studio account? Just log in and check the bottom-left corner of the screen to make sure you’re using the new 3.8 version. Publish your project, share the ID and API Key, and let your end-users start exporting narratives straight into their report documents.
Want to learn more?
You can also learn more about the new features and enhancements of Studio 3.8 in the Release Notes.
If you don’t have a Studio account but you’re ready to try the most flexible, self-use natural language authoring platform, get a demo for your specific use case.