The Event Mapping table is a limited feature and not widely available for use. To trigger Centauri logic from the Vega runtime, view our How to: Use Cross-Runtime Support article.
Overview
The Cross-Runtime Support Event Mapping table enables Creators to trigger Centauri logic using a Vega-enabled Panel component. After enabling CRS, Creators use the Event Mapping table to specify what Vega component and Vega events trigger Centauri logic components.
For example, if logic from a Vega Table contained in a Vega-enabled Panel component must trigger logic in a Centauri-runtime module, you map the triggering Vega component, the Vega Event watching the Vega component, and the Centauri component to trigger.
Using the Event Mapping table might reduce application performance. Consider using the direct execute method detailed in our How to: Cross-Runtime Support article.
Triggering Centauri Logic in a Vega-Enabled Panel Component
A Vega-enabled Panel component uses the Event Mapping table to map Vega events to the Centauri runtime. Vega events include runtime specific operators, DOM events, or events from Vega components. For example, when a Vega Button component is clicked, it reveals a hidden Centauri Text Field component.
For this example, use a Vega Button component in a Vega-enabled Panel component to reveal a Centauri Text Field component:
What You Need
To configure the Centauri module, you need the following components:
Configure the Text Field Component
Add a Text Field component to capture an end-user's last name. Hide the Text Field component using the Hide Field setting. Later, we'll configure a Decisions component to make it visible.
In the Module Builder, drag and drop a Text Field component onto the canvas.
In the Property ID field, enter lastName.
In the Label Text field, enter
Enter your last name:
.Set the Hide Field toggle to
(ON).
Click Save Component.
Configure the Decisions Component
Add a Decisions component that, when triggered, displays the lastName Text Field component.
Drag and drop a Decisions component onto the canvas, placing it below the lastName Text Field component.
In the Property ID field, enter ruleShow.
In the Label Text field, enter
ruleShow
.In the Outputs table, enter the following:
Source
Type
1
lastName
visible
Under the Conditionals table, click New Row.
In the Conditionals table, enter the following:
lastName_visible
1
yes
Click Save Component.
Configure the Panel Component
Configure a Panel component to use the Vega runtime. You'll also use the Event Mapping table to make a Vega Button component trigger the Centauri ruleShow Decisions component.
Drag and drop a Panel component onto the canvas, placing it below the ruleShow Decisions component.
In the Property ID field, enter panelVega.
Under Runtime, set Render components with to
Vega (2.0)
.Set Event Mapping to
(ON).
Next to Event Mapping, click Edit.
In the Event Mapping table, enter the following:
#
(Vega) Event Scope
(Vega) Event Name
(Centauri) Logic Component to Trigger
1
btnShow
onclick
ruleShow
You'll set up the btnShow
Button component in the following steps.
Click Save Component.
Configure the Button Component
Configure a Button component to use the Event
Action Type. When the end-user clicks the button, the panelVega Panel component looks for the onclick event and triggers the ruleShow Decisions component.
Drag and drop a
Button component onto the canvas, placing it inside the panelVega Panel component.
In the Property ID field, enter btnShow.
In the Label Text field, enter
Enter Last Name
.Navigate to the Actions settings.
The Action Type to
Event
.Click Save Component.
Save your module.
Preview your module in Express View. You'll see the following functionality:
Overview
The Cross-Runtime Support Event Mapping table enables Creators to trigger Centauri logic using a Vega-enabled Panel component. After enabling CRS, Creators use the Event Mapping table to specify what Vega component and Vega events trigger Centauri logic components.
For example, if logic from a Vega Table contained in a Vega-enabled Panel component must trigger logic in a Centauri-runtime module, you map the triggering Vega component, the Vega Event watching the Vega component, and the Centauri component to trigger.
Using the Event Mapping table might reduce application performance. Consider using the direct execute method detailed in our How to: Cross-Runtime Support article.
Triggering Centauri Logic in a Vega-Enabled Panel Component
A Vega-enabled Panel component uses the Event Mapping table to map Vega events to the Centauri runtime. Vega events include runtime specific operators, DOM events, or events from Vega components. For example, when a Vega Button component is clicked, it reveals a hidden Centauri Text Field component.
For this example, use a Vega Button component in a Vega-enabled Panel component to reveal a Centauri Text Field component:
What You Need
To configure the Centauri module, you need the following components:
Configure the Text Field Component
Add a Text Field component to capture an end-user's last name. Hide the Text Field component using the Hide Field setting. Later, you'll configure a Decisions component to make it visible.
In the Module Builder, drag and drop a Text Field component onto the canvas.
In the Property ID field, enter lastName.
In the Label Text field, enter
Enter your last name:
.Set the Hide Field toggle to
(ON).
Click Save & Close.
Configure the Decisions Component
Add a Decisions component that, when triggered, displays the lastName Text Field component.
Drag and drop a Decisions component onto the canvas, placing it below the lastName Text Field component.
In the Property ID field, enter ruleShow.
In the Label Text field, enter
ruleShow
.In the OUTPUTS table, enter the following:
Property ID
Type
lastName
visible
In the MICRO DECISIONS table, enter the following:
Property ID
lastName_visible
yes
Click Save.
Configure the Panel Component
Configure a Panel component to use the Vega runtime. You'll also use the Event Mapping table to make a Vega Button component trigger the Centauri ruleShow Decisions component.
Drag and drop a Panel component onto the canvas, placing it below the ruleShow Decisions component.
In the Property ID field, enter panelVega.
From the component settings menu, select Runtime.
Set Render Components with: to
Vega (2.0).
In the Event Mapping table, enter the following:
You'll set up the btnShow
Button component in the following steps.
Click Save & Close.
Configure the Button Component
Configure a Button component to use the EventAction Type. When the end-user clicks the button, the panelVega Panel component looks for the onclick event and triggers the ruleShow Decisions component.
Drag and drop a
Button component onto the canvas, placing it inside the panelVega Panel component.
In the Property ID field, enter btnShow.
In the Label Text field, enter
Enter Last Name
.From the component settings menu, select Actions
Set the Action Type to Event.
Click Save & Close.
Save your module.
Preview your module in Express View. You'll see the following functionality:
Best Practices
The Event Mapping table might reduce application performance. Consider using the direct execute method detailed in our How to: Cross-Runtime Support article.