Exporting Storyline Variables

Hi all,

I'm speaking at the ATD TechKnowledge conference later in January (San Jose, CA). My session is about advanced Storyline (variables, triggers, and conditions). I'm created a script to help me prepare for the session. It exports Storyline variables into an external file (.csv), so you can open it in Excel, and add description to each. 

I've been using this xPorter script to document variables, especially, in large projects. If you're interested trying out for yourself, contact me. The program only works on Windows, and as usual, it is not supported by Articulate. 

Here's how it works: 

https://youtu.be/-f01ZrQNm-k

 

6 Replies
Zsolt Olah

Brian is correct, it literally automates what you would do manually:

1. Open the Variables dialog box

2. Highlight the variable

3. Click the edit icon

4. (this is the only tricky part) Reads the form labels and values to grab the name, type and inital value. Copy the values.

5. Clicks on the usage number, and grabs all the instances where the variable is used.

6. Finally, it writes all this info into two files: one with all the usage info, and one as a csv for Excel.

In the Excel file, you can add description/explanation to each variable for documentation purposes. Let's say add new variables or update their value in SL. Now, if you run this again, it recreates these files but keeps the description, so you won't lose it.  

Zsolt Olah

If you want to give it a try, here's the download info:

 

Here’s the drop box link to the file. The first link is a self-extracting .exe file. After downlading it, you can run and creates the necessary files.

 

https://www.dropbox.com/s/9onq4w79b1lrql9/xporterinstall.EXE?dl=0

 

If your system/firewall doesn’t play nice with .exe files, you can also download the zip version below. In that case, you need to unzip the file manually.

 

https://www.dropbox.com/s/o5qls3hg6k6clsa/xporter.zip?dl=0

 

After unzipping or installing the files, there’s a README.txt in the folder. Read it before you try xporter. It might not work out of the box if your Storyline looks different. You need to “teach” the script what to look for. The readme files explains how.

 

Best way to test it out is creating a new Storyline and adding three variables (one for each type).