Security Code Number Pad

This is a project I have been working on for quite some time, due to the Storyline 360 limitations etc using expressions and having to use several triggers to do one thing, as part of this project.

This is an advanced setup so I do not really want to have to troubleshoot or explain if possible. So I am providing as much info as I can here. All shapes and buttons are Storyline shapes and buttons so you can style any way you please. The font for the numbers I used is Digital-7 a free font available online.

This is a single slide of a Security Pad where you can add 4 one/two digit codes, so that when they are all correct a Continue button will appear. This can obviously be changed to show a layer or do something else. I left the instructions on the slide that Correct1-4 in the Variables management can be manually changed to the 4 different numbers up to 99.

When the number is correct it will be green, when it is incorrect it will be red. All 4 numbers must be correct to show the continue button. The USERINPUT field at the top will show the number currently being input by the user, when the user hits submit the USERINPUT field clears for the next number and moves to the allocated Code to the side.

Javascript has been used where necessary such as each number button has a JavaScript code assigned to it to add its value to the USERINPUT with a limitation on 2 numbers. I comment in the codes where possible to explain what is happening.

Also, you will see in the triggers panel greyed out triggers. Activating these triggers will allow you to Randomly generate the 4 numbers so that each user gets a unique set of numbers that will avoid copying or code sharing if it is a requirement.

Now it is not practical to do this on this slide, so you can move the triggers to different slides in the course to generate the code. Below is the matching pair that you put on a different slide that you want the random number to appear. So RandomNumber1 generates a random number, and the second trigger assigns that random number to Correct1, and so on. 

They must be in the order below as the RandomNumber1 has to be generated first before populating Correct1 for example.

*By leaving those triggers inactive simply means you manually change the Correct1-4 values in the Variable section.

Uses for this. Usually for re-enforcement and to ensure attention and focus. At the end of a section you can show a slide that generates a random number or the manual number by adding a text filed with the %Correct1% etc reference and you give instructions to the user to write down the number or whatever, so that at the end of the course they need to input all 4 codes to either complete or move on etc. I have also put a code into a video (sneaky I know) so that they must watch the video to get the number. You can also use a quiz question to give a number answer which can be a "Clue". Good for re-enforcement and remembering and attention. Many applications for this.

The Reset Button also has inactive randomising triggers also but activating them will cause the random numbers to regenerate when the reset button is clicked.

I have also left on the slide the four Variable references of Correct1, 2, 3 and 4 so you can see the correct answers required. Remove them when publishing.

Manually it is Correct1 = 10, Correct2 = 20, Correct3 = 30, and Correct4 = 40. But you will most likely change them to whatever you want.

You will find the values in the Variables panel where you can manually change them to whatever you like. Simple place their reference %Correct1% etc, into the section or slide in your course where you want it to be shown for the user to take note of.

 

To use in an existing project, simply go to File-Import, and find the .story file. Import it and if there are more than 1 slide in the .story file you will be asked to choose the slide you want. In this case there is only one slide. By doing this, all triggers and variables will also be imported correctly into the project.

I suggest you keep a backup copy of the .story file, and also if you have advanced knowledge of Storyline, spend some time going through everything to help understand what is going on.

I am not always available to respond and this is a project that works as is and you are free to adapt change and improve it as you wish. You might want to add an audio beep for each button press for example...

I hope this might be useful in some way to add a bit more user interactivity.