Velocity powered by Wavelink
This page refers to an older version of the product.View the current version of the User Guide.
Setting Scopes
Use a scope to determine when a script should start or end. Scripts are linked to a session, screen, or field. After creating or using a library script, you must link it to a scope. Once linked, you may set variables from the Script Parameter pane.
Types of Scopes
TE
You can set scopes by session, screen, or field. Each scope type must be entered in a specific format to ensure scripts are invoked at the right time.
•Session: session
This scope must be entered as it is shown above. This scope executes any linked script when a session is started.
•Screen:@ScreenName
Screen scopes are the Template name of a screen preceded by an @.
•Field:@ScreenName:component-1
Field scopes consist of two parts: screen and element scopes, which are separated by a colon.
>Web
Using a scope with a Web host is different from TE. No scope is called upon until the web page has fully loaded. At that point, the scope becomes active.
•[Blank]
Leaving the scope blank is the same as specifying the root directory of a web host. Scopes applied this way will remain active for all screens on your host.
•URL
For hosts located on a web server, enter the web page name without the protocol, port, or trailing /. You can specify an individual page, or just a directory.
For example, you would enter a web host as webhost.ivanti.com.
•Custom
You can define your own scope on a web page, which can then be used as focal scopes for scripts. This can include such values as classes, IDs, paragraph text, and headers, effectively giving you complete control over what values to use as scope identifiers. The script library offers pre-defined scripts to help get you started with navigating pages on a web host. These scripts determine the behavior for entering and exiting a custom scope
After setting this scope, Velocity will actively watch for a string matching the scope, and then execute the script associated. To listen for, enter, and exit these scopes, you'll need to make use of the Android.scopeEnter and Android.scopeExit APIs in your scripts, which govern the behaviors for scope focus.
For example, a custom scope may be firstName. Based on the order and behaviors of the assigned script, Velocity will actively watch for that value and enter the scope.
Multiple scopes may be applied to a single script, which enables you to execute a script repeatedly based on screens or fields entered or focused upon. You can likewise change the order in which these scopes execute by dragging and dropping them within the Scope pane on the Scripts tab.
However, you cannot set conditional scopes that activate only when other specific scopes are active. Scopes will only execute in the order they've been arranged from the Scripts tab.
To link a script to a scope
Watch a related video (0:43)1.From the Scripts screen, enter the script you want to link the script to. This scope should match the format required by the host type, as described above.
2.Click the Link button below the Scope pane.
3.Enter the scope you wish to create. This can include session, screen, or field scopes, which are referenced above. After clicking OK, the script is linked to the scope.
To edit parameter variables
1.Select the script and scope you want to set parameters in. The parameters available for editing appear in the Parameters pane on the right.
2.Enter the parameter values as needed. Depending on the script, you can leave some fields blank. If a parameter contains a Managing Script Parameters, you cannot save the field's contents unless the value is entered correctly.
Values must be entered as they're required by the script. For an explanation on valid values for Ivanti's pre-generated scripts, see Using Library Scripts.
3.Click Save to keep your changes.
Scopes narrow the instances for when a script is invoked. This helps avoid potential overlaps with scripts that might interfere with one another. If you multiple scripts to the same scope, the parameters are applied based on the order of the scopes in the Scope pane.
For example, if you link the same script twice to a session where one parameter first prepends PRE- and the other prepends 123- to a bar code, the script with the PRE- value is applied first, followed by the script with the 123- value. The end result of a bar code scan would then be 123-PRE-XXXXXXXXX.
This page refers to an older version of the product.View the current version of the User Guide.
The topic was:
Inaccurate
Incomplete
Not what I expected
Other
Copyright © 2017, Ivanti. All rights reserved.