Action
JGR Experience Validation
Download .mdValidate if there still are seats available and if the fan has enough points to redeem.
Custom Laila action. Step 1 of the Premium Experience flow.
Identity
| Field | Value |
|---|---|
| Master label | JGR Experience Validation |
| Local developer name | JGR_Experience_Validation |
| Invocation target | JGR_Experience_validation |
| Invocation target type | flow |
| Confirmation required | false |
| Show in progress indicator | false |
Purpose
Validate if there still are seats available and if the fan has enough points to redeem.
The flow uses the active MessagingSession ID to find the fan's current Premium Experience attendance record and apply two checks:
- Seats are still available on the target Premium Experience.
- The attendee has enough points to redeem.
Used by
- Premium_Experience —
JGR_Experience_Validation_179KY0000000OtK
Inputs
| Name | Type | Required | User input | PII | Description |
|---|---|---|---|---|---|
inputMessagingSessionID | text | Yes | No (planner-piped from RoutableId context variable) | No | Messaging Session Id. |
Outputs
| Name | Type | Displayable | Used by planner | Description |
|---|---|---|---|---|
outputAttendeeId | text | No | Yes | Premium Experience Attendee record Id — fed into JGR_Confirm_Experience_Attendee and JGR_Slack_Notification. |
outputPremiumExperienceId | text | No | Yes | Premium Experience record Id — fed into JGR_Slack_Notification. |
outputMessage | text | Yes | Yes | Result message from the action (e.g. "You have enough points and X seats remain"). |
Dependencies
- Flow
JGR_Experience_validationdeployed. - Custom objects backing the flow:
Premium_Experience__candPremium_Experience_Attendee__c(or whatever the flow queries — verify by reading the flow on port). - Read access on those objects for the bot user.
Reuse notes
The contract is "given a Messaging Session, find the right attendee + experience and validate". When porting to another org you must:
- Recreate the data model — Premium Experience and its Attendees, plus a link from MessagingSession to the active attendee row.
- Re-deploy the flow
JGR_Experience_validation. - Bind the bot's
RoutableIdcontext variable (already part of the standard bot template).