Experience
Description
The experience is the entire project, like features it also has properties and events except these properties and events which apply to all views of the project.
Properties
Start View: This property is used to select the view that the experience opens with when the player runs it.
Width: This can be used to change the resolution of the entire experience. Note that all the views will change to this dimension and all features inside it will also be scaled proportionately.
Height: This can be used to change the resolution of the entire experience. Note that all the views will change to this dimension and all features inside it will also be scaled proportionately.
Multiscreen: Select true if this experience is going to be deployed across multiple screens. When deployed on a windows device with multiple screens the experience will span across all the screens like it was one single screen
Orientation: Here you can select the destination orientation between the options of landscape portrait and either of them flipped.
Maximize Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Minimize Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Close Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Restore Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Pin Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Unpin Button: Many features in Baetho can be allowed to be maximized, minimized, closed and pinned. By default there are some icons for these buttons but it can be changed here
Events
Triggers
Key Pressed
Key Pressed: This trigger listens to the event of a key being pressed. It listens for the key that is specified in the parameter key
Parameter
Key: Character that it’s listening for
Timer
Timer: This starts a timer and executes the actions when the time is up. You can have it run multiple times by specifying the number of runs, 0 is to keep running indefinitely
Parameter
Duration: duration of time before executing actions
Number Of Runs: Specifies the number of runs, 0 is to keep running indefinitely
Inactivity
Inactivity: This trigger will execute the actions if the device has not had an interaction for the period specified by the duration parameter
Parameter
Duration: duration of time before executing actions
Application
App Closing: This trigger will execute the actions before the app closes. This is particularly useful if you want to call an api and send some data just before the app is closed
Api Triggers
API Call Complete: This trigger will execute the actions when a particular api has run successfully.
Parameter
API Asset: This specifies the api to listen to
API Call Error: This trigger will execute the actions when a particular api has encountered an error.
Parameter
API Asset: This specifies the api to listen to
API Call Started: This trigger will execute the actions when a particular api has been called.
Parameter
API Asset: This specifies the api to listen to
Player Connector
Player Connector Data Received: This trigger will execute the actions when data is received from a specified device.
Parameter
Player Connector: Specify the player connection from which data is to be received to trigger this event.
XML Asset: When data is received it will be stored into this xml data asset
RFID
RFID Tag Found: This trigger will execute the actions and RFID tag is detected by a compatible reader.
Parameter
Tag Id: The tag id which when scanned will trigger this event
Scanner Serial Number: This is the serial number of the scanner which must detect the tag in order to trigger this event
RFID Tag Lost: This trigger will execute the actions and RFID tag is removed from a compatible reader.
Parameter
Tag Id: The tag id which when removed will trigger this event
Scanner Serial Number: This is the serial number of the scanner which the tag must have been removed from in order to trigger this event
Actions
View Navigation
Go To View: This action will go to a specified view
Parameter
Target: This is the view you wish to go to
Transition: These are different effects to choose from to add style to your experience
Effect: The effect on the transition controls the manner in which the transition plays
Duration: This specifies the amount of time for the transition to take
Go Forward: Similar to the forward in a web browser, if the experienced has transitioned to the current view through the Go Back action then Go Forward will go to the view it came from.
Parameter
Transition: These are different effects to choose from to add style to your experience
Effect: The effect on the transition controls the manner in which the transition plays
Duration: This specifies the amount of time for the transition to take
Go Back: Similar to the forward in a web browser, this will cause the experience to go to the previous view.
Parameter
Transition: These are different effects to choose from to add style to your experience
Effect: The effect on the transition controls the manner in which the transition plays
Duration: This specifies the amount of time for the transition to take
Experience
Upload Data Asset: This will upload a data asset to the CMS
Parameter
Data Asset: The xml data asset you wish to upload
Update Experience: This checks with the CMS if there exists a newer experience for the current device. If there is, it will download and update the experience.
Update Content: This checks with the CMS if there exists any newer media files for the current device. If there is, it will download and update all the mandatory files. Non mandatory files can be skipped by the person using the device.
Answer Question: Use this action to store a value against a question. To learn more about how to use questions go to www.baetho.com
Parameter
Question ID: The id of the question created on the CMS
Question Answer: The answer you wish to store
Take Screenshot: This action takes a screenshot of this and stores where the parameters specify
Parameter
Save Folder: Folder in which to save to
Save File Name: File name to save with
Clear Screenshots: Deletes all screenshots that have been taken
Take Screenshot: This action sends an email with the specified properties
Parameter
To: Email address to send to
CC:Email address to CC to
BCC: Email address to BCC to
From: Email that is set as a sender in your CMS
Subject: Email subject
Body: The body of the email. You can also take this from a global var of xml data asset by hooking it. It can have content of html.
Documents: Here you can specify the id of a document in the CMS that you wish to send as an attachment. You can also send multiple documents by separating the Ids by a comma
Attach Screenshots: Here you can also specify if you want to send the screenshots taken by the action take screenshots as attachments. You have the option to send all the screenshots, only the last screenshot taken or none at all
Parameter Name: Here you can add parameters which are string in the body of the email to be replaced to another value. For example you can have the string “<name>” inserted in the body of the email which you wish to be replaced by a value from a global variable which has the name stored in it. So parameter name you would set to <name> and parameter value would be hook to the global variable that has the name stored
Load Image From Camera Roll: This action can be used on tabs to load an image into the experience from the camera roll
Parameter
Image Asset: The location to store the image in the experience
Session
Send Data: This action send the tracking data of the current session to the CMS
Start Session: This action starts tracking events for the current session
End Session: This action stops tracking events for the current session
Session
Restore All Global Variables: This resets all the global variable values to what they were when the experience originally started
Restore All XML Data: This resets all the xml data assets to what they were when the experience originally started