Version: 8.1

Perspective Session Event Scripts

Perspective offers a collection of Session Events designed to allow the Gateway to track and interact with the Session at critical moments. Specifically, they are scripts that run in the Gateway when a Session starts up, shuts down, or runs a Perspective App action.

There are nine configurable Session events in Perspective:

Startup
Shutdown
Page Startup (new in 8.1.0)
Authentication Challenge Completed (new in 8.1.16)
Message
Keystroke
Barcode
Bluetooth
Accelerometer
NFC

note

Although they are designed to handle Session Events, the scripts that you write will be run in a Gateway scope, not a Session scope

Configuring Session Events

To start working on a Session event script:

In the Project Browser, double-click on the Session Events section:
The Session Events dialog will appear:
Configure a script by selecting one of the events on the left-hand side.

Startup and Shutdown Event Scripts

Startup and Shutdown events run, naturally, whenever a Session starts or ends. In each case, the Gateway will have access to the session object associated with the section, complete with all Session properties.

When designing a startup or shutdown event script, custom Session properties can be used to pass any additional information to the Gateway, or, in the case of a startup script, to pass information to the newly opening Session. You can configure custom Session properties from the Page Configuration dialog, by clicking on the Settings - icon in the Designer.

A shutdown event script will run specifically when a Session is ending. This happens specifically when any of the following events occur:

The Session closes due to a timeout. Session timeout is configurable in the Perspective > General section of Project Properties in the Designer
The user is no longer authorized to run the Session.
The redundancy system determines that the Gateway is inactive.
The licensing system no longer permits the user to run the Session.
The project is no longer runnable.
The project is deleted.

note

Closing the browser tab with the Session will not immediately close the Session; the Session must first time out.

Startup and Shutdown Example

This example will record the Session start and end time to the database.

For this example, we need to set up a few queries that we can use to write our data to the database.
Make a new named query called Startup Query.
1. Set the Query Type to Update Query.
2. Set up a single Value type parameter with a name of SessionID and a datatype of string.
3. Add the query:
```
INSERT INTO sessions (session_id, start_time)
VALUES (:SessionID, CURRENT_TIMESTAMP)
```
Make a second new named query called Shutdown Query.
1. Set the Query Type to Update Query.
2. Set up a single Value type parameter with a name of SessionID and a datatype of string.
3. Add the query:
```
UPDATE sessions
SET end_time = CURRENT_TIMESTAMP
WHERE session_id = :SessionID
```
Next, we need to add Session Events so that Perspective knows to run those queries on startup and shutdown.
Under the Project tab, select Session Events.
On the Session Events screen, click the Startup icon.

Add the following script to the page:

# This script will record the time when the Session is opened.
 
    # Create the parameters
    queryParams = {'sessionID':session.props.id}
 
    # Run the query
    system.db.runNamedQuery('My Project', 'Startup Query', queryParams)

Click Apply and then click the Shutdown icon.

Add the following script to the page:

# This script will record the time when the Session times out. Note that after the Session is closed,
# the Session won't time out until the time out period is reached.
    
    # Create the parameters.
    queryParams = {'sessionID':session.props.id}
    
    # Run the query.
    system.db.runNamedQuery('My Project', 'Shutdown Query', queryParams)

Click OK.
Save your project.

Test the Example

To test the example, open the Perspective App on your mobile device and load the project.

You should see a new entry in the database table with the time the time the Session was started as well as the session ID.
After the Session times out (such as after it is closed) you should see the original entry get updated to include the new shutdown time.

Page Startup

Watch the video

New in 8.1.0

This script runs in the Gateway when a Perspective page starts in a new tab or window.

note

Navigating to a page configuration in a tab that's already opened (such as using system.perspective.navigate) will not trigger this event.

Parameters

`page`

A reference to the newly created page. Note that other page props will not return a valid value on page startup.

Accessing properties under this argument requires that you include .props. along the path. Demonstrations are included below:

Props Demonstrations

Property	Description	Example
pageId	Identifier associated with the target page.	`# Provides the page id. pageId = page.props.pageId`
path	Represents the Page URL of the page, for example: / or /myPage.	`# Provides a path to the page. pagePath = page.props.path`

In addition to the arguments above, the Session is available from this event:

# For example, we can access the session id with the following:
sessionId = page.session.props.id

Authentication Challenge

New in 8.1.16

This event is fired when an authentication challenge is completed by the user.

Authentication Challenge Parameters

`session`

An object that references the Project Session that triggered the authentication challenge. Use this to identify the specific Session that triggered the authentication challenge.

`payload`

The opaque payload provided by the initial Authentication Challenge Action or Scripting function invocation.

`result`

A Result object that can be parsed by the result functions below.

Result Functions

Function	Description
isSuccess()	Returns true if the authentication challenge was a success. If true, optionally call getAsSuccess() to get the result as a Result.Success object for further parsing. If false, optionally call getAsError() to get the result as a Result.Error object for specific details pertaining to the error.
getAsSuccess()	Returns the result as a Result.Success object if the result is successful, otherwise throws an UnsupportedOperationException if the result is an error. Check isSuccess() or isError() before calling this function to ensure you get the correct result type. Note: It is not necessary to call getAsSuccess(). If isSuccess() returns true, the result type is Result.Success, so all of the properties and functions of a Result.Success object are available on the original result reference.
isError()	Returns true if the authentication challenge resulted in an error. If true, optionally call getAsError() to get the result as a Result.Error object for specific details pertaining to the error.
getAsError()	Returns the result as a Result.Error object if the result is an error, otherwise throws an UnsupportedOperationException if the result is successful. Check isSuccess() or isError() before calling this function to ensure you get the correct result type. Note: It is not necessary to call getAsError(). If isError() returns true, the result type is Result.Error, so all of the properties and functions of a Result.Error object are available on the original result reference.

Result Objects

This object contains different properties depending on whether the authentication challenge result is a success or an error.

Result.Success

An object that represents a successful authentication challenge result. Call getContext() to return a WebAuthUserContext object with the following properties:

Property	Description
idp	The name of the IdP which challenged the user.
securityZones	A string array containing the names of the security zones associated with the challenged user.
user	A WebAuthUser object that contains the following properties. See user properties.
securityLevels	A string array of security level paths representing all of the security levels associated with the challenged user

User Properties

Property	Description
id	The unique identifier associated with the challenged user
userName	The challenged user’s username.
firstName	The challenged user’s first name, or null / None if not defined for this user.
lastName	The challenged user’s last name, or null / None if not defined for this user.
email	The challenged user’s email address, or null / None if not defined for this user.
roles	The challenged user’s roles as a string array.

Result.Error

An object that represents an error authentication result. It can be parsed by the following functions:

Function	Description
isGeneric()	Returns true if the error is not related to a timeout or user cancellation. Optionally call getAsGeneric() to get the Result.Error as a Result.Error.Generic object for specific details pertaining to the generic error.
getAsGeneric()	Returns the result as a Result.Error.Generic object if the error is generic, otherwise throws an UnsupportedOperationException. Check isGeneric() before calling this function to ensure you get the correct result type. Note: It is not necessary to call getAsGeneric(). If isGeneric() returns true, the result type is Result.Error.Generic, so all of the properties and functions of a Result.Error.Generic object are available on the original result reference.
isTimeout()	Returns true if the error is due to a timeout. Optionally call getAsTimeout() to get the Result.Error as a Result.Error.Timeout object for specific details pertaining to the timeout error.
getAsTimeout()	Returns the result as a Result.Error.Timeout object if the error is due to a timeout, otherwise throws an UnsupportedOperationException. Check isTimeout() before calling this function to ensure you get the correct result type. Note: It is not necessary to call getAsTimeout(). If isTimeout() returns true, the result type is Result.Error.Timeout, so all of the properties and functions of a Result.Error.Timeout object are available on the original result reference.
isCancelled()	Returns true if the error is due to user cancellation. Optionally call getAsCancelled() to get the Result.Error as a Result.Error.Cancelled object for specific details pertaining to the cancellation error.
getAsCancelled()	Returns the result as a Result.Error.Cancelled object if the error is due to user cancellation, otherwise throws an UnsupportedOperationException. Check isCancelled() before calling this function to ensure you get the correct result type. Note: It is not necessary to call getAsCancelled(). If isCancelled() returns true, the result type is Result.Error.Cancelled, so all of the properties and functions of a Result.Error.Cancelled object are available on the original result reference.

Result.Error Objects

This object contains different properties depending on the cause of the authentication error:

Object	Description
Result.Error.Generic	An object representing a generic error authentication result. Call getMessage() to return a diagnostic message pertaining to the error, or null if such a message does not exist.
Result.Error.Timeout	An object representing a timeout error authentication result. Call getTimeout() to return the integer timeout value (in minutes) that that was used to configure the timeout.
Result.Error.Cancelled	An object representing an error result due to user cancellation. This object has no functions or properties.

Authentication Challenge Example

This example script will determine whether to proceed with a specified action after a completed Authentication Challenge Action. In this case, the action is permitted only if the second user's roles include 'supervisor', If the action is not permitted, or the authentication challenge result is an error, a message box will pop up with relevant context.

if result.isSuccess():
    # Parse information about the successful result
    success = True
    context = result.getAsSuccess().getContext()
    user = context.user
    roles = user.roles
             
    # Determine if the e-signature is valid:
    if 'supervisor' in roles:
        # If the user is a supervisor, proceed with the specified action:
        proceedWithSomeAction()
     
    else:
        # If the user is not a supervisor, write to a logger:
        logger = system.util.getLogger("Authentication Challenge")
        logger.info("%s is not authorized"% user.userName)
             
# If the result is an error, write to a logger:
else:
    success = False
    error = result.getAsError()
     
    # Change the content of the logger message based on the type of error:
    if error.isGeneric():
        message = error.getAsGeneric().getMessage()
        logger = system.util.getLogger("Authentication Challenge")
        logger.info(message)
             
    elif error.isTimeout():
        timeout = error.getAsTimeout().getTimeout()
        logger = system.util.getLogger("Authentication Challenge")
        logger.info("Authentication challenge timed out after %d minutes."% timeout)
             
    elif error.isCancelled():
        logger = system.util.getLogger("Authentication Challenge")
        logger.info("Authentication challenge cancelled.")   
             
    else:
        logger = system.util.getLogger("Authentication Challenge")
        logger.info("Unknown error occurred.")

Message

The Message Handler scripts will run whenever the Session receives a message from system.util.sendMessage or system.util.sendRequest.

note

These types of message handlers are different than component-based message handlers, which are accessed with system.perspective.sendMessage. Session Message Handlers can not be called by system.perspective.sendMessage.

tip

An efficient way to use this message handler in cases with user driven operations is by incorporating system.perspective.getSessionInfo to lookup all sessions and then filter the sessions to target specific users.

Message Parameters

`session`

The Perspective Session that is handling this message.

`payload`

Retrieve them with a subscript, e.g., myObject = payload['argumentName']

Message Example

This example shows how to set up a message handler script to send a simple log message to the Gateway. We will use a button component to run the system.util.sendMessage command.

Under the Project tab, select Session Events.
On the Session Events screen, click the Message icon.
Click the Add icon.
Enter myMessage in the Message Handler Settings Name field.
Click OK.

We will first define the define the message and assign the sessionId to our current Perspective session. Then, we will use Logger functions to return a logger object to log message with level info. Add the following script to the page to complete these functions:

def handleMessage(session, payload):
    message = payload['message']
    sessionId = session.props.id
    
    logger = system.util.getLogger("myLogger")
    logger.info("Your session "+str(sessionId)+" received the message: "+str(message))

Click OK.
Add a Button component onto a view.
Right-click on the Button component and choose Configure Events.
On the Event Configuration screen, select Component Events > onActionPerformed.
Click the Add icon and select Script action.
For this example, we will use system.util.sendMessage, which means we need to add our project name, the message handler we created, the payload message we want to send, and limit the scope to Session. Add the following script to the page:
```
def runAction(self, event):
    system.util.sendMessage("samplequickstart", "myMessage", {"message":"Hello World"}, "S")
```
Click OK.
Save your project.

Test the Example

To test the example, launch your Perspective Session and click the button component we created.

After clicking the button, the script will send the "Hello World!" message to your session id.
Access your Gateway Status > Diagnostics > Logs page to confirm the message was received.

Keystroke

New in 8.1.10

Keystroke scripts will run when the session detects a KeyboardEvent matching either a single key or a regex pattern. A single key match can be made on either a key press (keyDown) or on a key release (keyUp). A regex match is always made on a key release. Key Event scripts can be triggered by keyboards and any other device that is capable of generating a KeyboardEvent, such as an HID barcode scanner.

Keystroke detection is only active inside of a Perspective session and is not active inside of the Designer.

note

Note: The device being used to trigger key event scripts must be able to generate a KeyboardEvent. HID barcode scanners will generate KeyboardEvents because they mimic a user typing keys on a physical keyboard. Scanners and other input devices that do not create KeyboardEvents will not trigger this logic.

Keystroke Parameters

`page`

An object that contains information about the current page.

Argument	Description
props	Properties of the "page" object.
session	An object that contains information about the current session.

`event`

An object that contains information from the Key Event.

Argument	Description
altKey	Returns a boolean that is true if the Alt (Option or ? on OS X) key was active when the key event was generated.
code	Returns a string with the code value of the physical key represented by the event.
ctrlKey	Returns a boolean that is true if the Ctrl key was active when the key event was generated.
isComposing	Returns a boolean that is true if the event is fired after "compositionstart" and before "compositionend".
key	Returns a string representing the key value of the key represented by the event.
location	Returns a number representing the location of the key on the keyboard or other input device.
metaKey	Returns a boolean that is true if the Meta key (on Mac keyboards, the ? Command key; on Windows keyboards, the Windows key) was active when the key event was generated.
repeat	Returns a boolean that is true if the key is being held down such that it is automatically repeating.
shiftKey	Returns a boolean that is true if the Shift key was active when the key event was generated.
matches	Returns a list where the first entry of the list is the exact text which registered as a match for the regex, and all subsequent entries in the list are the content which fell into capture groups.

Single Key

For single key matches, the match can be a physical key typed or the code generated by the key. Modifiers are additional keys that can be held down during a KeyboardEvent and are detectable in the event data. These include Alt, Control, Shift, and Command/Meta.

In addition, the resulting Key Event that is used for match detection has the following advanced features:

Capture Phase - Allows execution during event capturing, which will let the resulting script execute before other interface events that may be in place. By default, events execute during an event bubbling phase which is dictated by the position of the event binding in the Document Object Model (DOM). In the case of Key Events, these are bound to the document layer of the DOM and will execute after other interface events if this option is unchecked.
Prevent Default - Prevents any default browser functionality that would be associated with the event binding. This can be toggled on if there is any functionality that should not be run when a keyDown/keyUp event has been fired at the document level when a key match is made.
Stop Propagation - Prevents the event from propagating beyond the point in the DOM where it is bound (the document level). This can be useful if combined with the Capture Phase option as it will prevent any interface keyDown/keyUp events from running that are bound deeper in the DOM than the document level.

Regex Match

For a regular expression (regex) pattern match, a match will be based on a supplied regex pattern and a series of keys stored in a match buffer. This buffer will always be the most recently typed characters and should be the length of a "correct match" to the supplied regex pattern.

Regex Example

This example will update a custom Session property when a regex pattern match is found.

For this example, place a Label component onto a view.
Add a custom Session property called scannerInput.
Bind the text value of the Label to the custom Session property.
Under the Project tab, select Session Events.
On the Session Events screen, select Key Events.
Click on the Add icon and select regex match.
Enter the regex pattern you want the Session to watch for. In the above example, a match occurs for any sequence of 12 numeric characters followed by an "@"
Enter the length of the match buffer. The match buffer should equal the minimum number of characters required for a pattern match.
Add the following script:

page.session.custom.scannerInput = "Match found"

Click OK.
Save your project.

Test the Example

To test the example, launch a Perspective session and open the view containing your Label. Type a string of characters matching the regex pattern you configured above. You should see the Label's text change:

Perspective App Event Scripts

When the Perspective App is running on a mobile device, it enables users to use tools available on the device, such as GPS location data, the camera, or the accelerometer. The remaining Session events are designed specifically to handle the Perspective App Actions..

Barcode

Barcode Scanned

Watch the video

The scanned barcode action can make use of a mobile device's built in camera.

Barcode Parameters

session

An object that references the project Session that called the Barcode Scanned event. Use this to identify the specific Session that scanned the barcode.

data

The data returned from the barcode scan. Access the underlying barcode data using:

# The value that was scanned
data.text
 
# An integer representing a unix timestamp of when the barcode was scanned
data.timestamp

New in Perspective Mobile app version 0.98

Version 0.98 of the Perspective Mobile App added the following property:

# The type of barcode that was scanned.
data.barcodeType

context

The user defined context object that can be defined on the action.

Barcode Example

This example will scan a barcode, and write its value to a tag.

For this example, drag a Button component and a Label component onto a view.
Create a new Memory tag with a data type of String. Set the value to Please scan a barcode.
Bind the text of the Label to the new tag.
Right-click on the Button component and choose Configure Events.
On the Event Configuration screen, select Mouse Events > onClick.
Click the Add icon and select Scan Barcode action.
Click OK. Next we need to set up a session event so that Perspective knows how to interpret the scanned barcode data.
Under the Project tab, select Session Events.
On the Session Events screen, select the Barcode icon.
Add the following script to the page:
```
system.tag.writeAsync(['[default]New Tag 5'], [data.text])
```
note
We used the tag created for this example, New Tag 5. You can enter your own tag name if different.
Click OK and save your project.

Test the Example

To test the example, open the Perspective App on your mobile device and load the project.

Click Scan Barcode.
If this is the first time scanning a barcode, you'll get a message requesting permission for Perspective to take pictures and record.
Click Allow.
You can now use the camera on the mobile device to scan the barcode.
Ignition scans the barcode. Once it recognizes the barcode, the script will run and the text is written to the tag. The Label then shows the new tag value.

Bluetooth

This Session event script sends received Bluetooth advertising data to Perspective. It supports iBeacon and Eddystone formats.

Eddystone will work on iOS and Android
iBeacon on iOS requires user to specify the specific region (iBeacon UUID) located on Session props bluetooth.config.iBeaconRegion.

note

Bluetooth "advertising data" is the name of the communication data according to the Bluetooth spec. There is no connection to advertising as an industry.

Bluetooth Parameters

session

An object that references the Project Session.

data

List of buffered advertising data. The data comes in as a data object, which has various parts. The following is example output.

{
    "values":
        [
            {
                "rssi":-48,
                "timestamp":1570147485167,
                "manufacturerData":{
                    "companyId":6,
                    "dataBase64Encoded":"AQkgAl_edccdnHClMvecMCiM--aAkLHAPibd"
                }
            },
            {
                "rssi":-48,
                "timestamp":1570147486012,
                "serviceUUIDs":[
                    "FEAA"
                    ],
                "serviceData":{
                    "uuid":"FEAA",
                    "dataBase64Encoded":"AOyqqqqqqqqqqqqqAAAAAAAA"
                    },
                "eddystoneUID":{
                    "txPower":-20,
                    "namespaceID":"AAAAAAAAAAAAAAAAAAAA",
                    "instanceID":"000000000000"
                    }
            },
            {
                "rssi":-54,
                "timestamp":1570147485919,
                "manufacturerData":{
                    "companyId":76,
                    "dataBase64Encoded":"AhV88isfQjVLY4VnXXfYqpTyAAAAAL8="
                    },
                "iBeacon":{
                    "uuid":"7CF22B1F-4235-4B63-8567-5D77D8AA94F2",
                    "major":0,
                    "minor":0,
                    "txPower":-65
                    }
            },
            {
                "rssi":-54,
                "timestamp":1570147485987,
                "manufacturerData":{
                    "companyId":65535,
                    "dataBase64Encoded":"vqwSNFZ4EjQSNBI0EjRWeJASAAAAAOwA"
                    },
                "AltBeacon":{
                    "manufacturerId":65535,
                    "uuid":"12345678-1234-1234-1234-123456789012",
                    "instance":"00000000",
                    "txPower":-20,
                    "manufacturerReserved":"00"
                    }
            }
    ]
}

Accelerometer

Accelerometer Data Received

Watch the video

The Accelerometer event is only used when data is coming in from a batched Accelerometer Action.

Accelerometer Properties

session

An object that references the Project Session that called the Accelerometer Data Received event. Use this to identify the specific Session that triggered the batching of accelerometer data.

data

The data returned from the batched accelerometer. The data comes in as a data object, which has various parts. Access the various parts like:

logger = system.util.logger('accelerometer')
for row in data.values.data:
    logger.info('X:' + str(row['x']))
    logger.info('Y:' + str(row['y']))
    logger.info('Z:' + str(row['z']))

context

The user defined context object that can be defined on the action.

Accelerometer Example

This example will write accelerometer data to the Gateway logs.

For this example, put a Button component onto a view.
Next right-click on the Button component and choose Configure Events.
On the Event Configuration screen, select Mouse Events > onClick.
Click the Add icon and select Accelerometer action.
1. Select Batch mode.
2. Set a Sample Rate of 400.
3. Set a Duration of 2000.
Click OK. Next we need to set up a Session Event so that Perspective knows how to interpret the accelerometer data.
Under the Project tab, select Session Events.
On the Session Events screen, click the Accelerometer icon.

Add the following script to the page:

# This script will take the accelerometer data and print it to the Gateway logs.

# Create the logger.
logger = system.util.logger('accelerometer')

# Loop through the list of batched events and pull out the x, y, and z values to print to the Gateway logs.
for row in data.values.data:
    logger.info('X:' + str(row['x']) + ', Y:' + str(row['y']) + ', Z:' + str(row['z']))

Click OK.
Save your project.

Test the Example

To test the example, open the Perspective App on your mobile device and load the project.

Click the Accelerometer button.
The script will record accelerometer data for the next two seconds, so move the phone around.
After the two seconds, you should see the logged information appear in the Gateway logs.

NFC

NFC Ndef Scanned

Watch the video

The NFC event is used when the NFC Action is used and the mobile device scans an NFC tag.

NFC Properties

session

An object that references the Project Session that called the NFC Ndef Scanned event. Use this to identify the specific Session that scanned the NFC tag.

data

The data returned from the NFC tag scan. The data object is a list which can contain multiple records from a single NFC tag. Access the underlying NFC data using:

logger = system.util.logger('NFC')
for row in data:
    logger.info('Type:' + str(row['type']))
    logger.info('Type Name Format:' + str(row['typeNameFormat']))
    logger.info('Payload:' + str(row['payload']))
    logger.info('String:' + str(row['string']))
    logger.info('Bytes:' + str(row['bytes']))

context

The user defined context object associated with the NFC scan event.

NFC Example

This example will write the NFC tag data to the Gateway logs.

For this example, place a Button component onto a view.
Right-click on the Button component and choose Configure Events.
On the Event Configuration screen, select Mouse Events > onClick.
Click the Add icon and select Scan Ndef NFC action.
Select Single mode, then click OK.
Next we need to set up a Session Event so that Perspective knows how to interpret the NFC data. Under the Project tab, select Session Events.
On the Session Events screen, click the NFC icon.

Add the following script to the page:

# This script will take the NFC data and print it to the Gateway logs.

# Create the logger.
logger = system.util.logger('NFC')

# Loop through the list of records stored in the NFC tag and pull out the type, type name format, payload, string data, and raw byte data from each record and print it to the Gateway logs.
for row in data:
    logger.info('Type:' + str(row['type']) + ', Type Name Format:' + str(row['typeNameFormat']) + ', Payload:' + str(row['payload']) + ', String:' + str(row['string']) + ', Bytes:' + str(row['bytes']))

Click OK.
Save your project.

Test the Example

To test the example, open the Perspective App on your mobile device and load the project.

Click the NFC button.
- After clicking the button, the script will pass the next NFC tag scanned to the script to be handled.
After scanning an NFC tag, you should see the logged information appear in the Gateway logs.

Configuring Session Events​

Startup and Shutdown Event Scripts​

Startup and Shutdown Example​

Test the Example​

Page Startup​

Page Startup

Parameters​

page​

Props Demonstrations​

Authentication Challenge​

Authentication Challenge Parameters​

session​

payload​

result​

Result Functions​

Result Objects​

Result.Success​

User Properties​

Result.Error​

Result.Error Objects​

Authentication Challenge Example​

Message​

Message Parameters​

session​

payload​

Message Example​

Test the Example​

Keystroke​

Keystroke Parameters​

page​

event​

Single Key​

Regex Match​

Regex Example​

Test the Example​

Perspective App Event Scripts​

Barcode​

Barcode Scanned

Barcode Parameters​

Barcode Example​

Test the Example​

Bluetooth​

Bluetooth Parameters​

Accelerometer​

Accelerometer Data Received

Accelerometer Properties​

Accelerometer Example​

Test the Example​

NFC​

NFC Ndef Scanned

NFC Properties​

NFC Example​

Test the Example​

Configuring Session Events

Startup and Shutdown Event Scripts

Startup and Shutdown Example

Test the Example

Page Startup

Parameters

`page`

Props Demonstrations

Authentication Challenge

Authentication Challenge Parameters

`session`

`payload`

`result`

Result Functions

Result Objects

Result.Success

User Properties

Result.Error

Result.Error Objects

Authentication Challenge Example

Message

Message Parameters

`session`

`payload`

Message Example

Test the Example

Keystroke

Keystroke Parameters

`page`

`event`

Single Key

Regex Match

Regex Example

Test the Example

Perspective App Event Scripts

Barcode

Barcode Parameters

Barcode Example

Test the Example

Bluetooth

Bluetooth Parameters

Accelerometer

Accelerometer Properties

Accelerometer Example

Test the Example

NFC

NFC Properties

NFC Example

Test the Example