Presto Attribute Mapping Expressions

Scope

Mapping Expressions for URLs

Variable or Parameter Declarations in EMML

Prestoglobal attributes: custom attributes with simple values used for:

All users.

Default values for Presto user attributes. If a value is not available at runtime for the current user, the Presto global attribute value is used.

parameter=$global/attribute-name

Prestouser attributes: custom attributes with simple values for each specific user.

In addition to the custom attributes that you define, Presto user attributes can also refer to user attributes defined in your User Repository.

Global attributes can provide default values for user attributes with the same name.

parameter=$user/attribute-name

Prestosession attributes: simple values or complex objects with multiple properties.

They are data saved from a previous response during the user's current session.

To use session attributes, your app or other client must first define them with the Presto Server. See Define Presto Session Attributes for instructions.

Important:

Effective in this release, the user's Presto credentials are no longer available as session attributes.

parameter=$session/attribute-name[/Xpath-expression-to-a-specific-node]

The XPath expression is optional and is only relevant for session attributess that are complex objects.

For session attributes with simple values:

For complex objects:

Prestorequest attributes: refers to HTTP headers or cookies for the current request.

parameter=$request.http-header/cookie-name

Presto request attributes are not supported in EMML.

Presto.namespace("MyOrg");

var MyOrg.MyVideosApp = function(app){
var root = jQuery( app.rootElement ).find( '#content' );
var connection = app.getConnection();
var requestBody = "";

connection.request({
url: "/presto/edge/api/rest/VideoSvc/getAll?x-presto-resultFormat=json&videoKey=$global.VideoKey",
type: "get",
contentType: "application/x-www-form-urlencoded",
data: requestBody
},
{ onSuccess: function(response, responseHeaders) {
//handle response data
},
onFailure: function(e) {
//handle error message
}
});