Map Presto Attributes to Artifact Input Parameters
You can have the Presto Server resolve input parameters for apps, mashables or mashups at runtime from server data, called Presto attributes, rather than providing this directly in an app or other client. This is also sometimes called server-side binding or server templating.
Common use cases for attribute mapping include:
Information for the current user, such as credentials for a web service.
Shared information that should be used for all contexts, such as an application ID or other key that should always be used when invoking a specific mashable.
Information provided in a previous response that is specific to the current transaction or session.
The syntax to map artifact input parameters to Presto attributes is different for different contexts:
Parameters specified in the URL to run the artifact use a
mapping expression.
EMML statements in a mashup declare attributes as variables or input parameters and then refer to these variables just like any other variable. See
Using
Presto
Attributes in Mashups for more information.