The heart of xACTION
At the heart of xACTION are triggers. Each trigger can contain one or more rules and one or more outbound actions. As statements come in, xACTION matches them against a trigger’s rules. When it finds a match, it records that matched trigger rule for the statement’s actor. Once all the trigger rules have been met by an actor, xACTION fires off all the outbound actions.
- Advanced Pattern Matching
- 3rd Party API Calls
- Intelligent Statement Forwarding
- Statement Transformation
If you need more information
Contact us! Sales@risc-inc.com
- xACTION is a bridge between xAPI and your other Enterprise systems. xACTION can take your xAPI Statements, match them to rules, and based on the matches it finds xACTION will make outbound REST API calls.
- No. xACTION can do statement forwarding, since xAPI is also a REST API, but xACTION can call virtually any REST API. It can include data from the statements that it receives in those outbound calls.
- Suppose there are 10 courses that must be completed to get a digital Learning badge. Over time, as a student completes the courses a statement is sent to an LRS indicating that each course has been completed. Once all 10 statements are received and meet the rules, xACTION could call a REST API that awards the student a badge.
- No, they could come from different LRSs. xACTION allows you to define multiple sources. The statements do not even need to come from an LRS, they could come directly from a Learning Record Provider.
- No, you define rules that must be matched for the statement to “count” toward executing the outbound actions.
- A rule consists of most parts of an xAPI statement. You can match based on verb, object, result, context activities and extensions or any combination of those parts. imperdiet nibh diam vel elit. Phasellus mollis ac augue sed varius.
- Yes, you can set a time limit for an Actor to match all statements for the trigger.
- xACTION allows for intelligent statement forwarding.
- They do, but they either forward every statement they receive or forward based on a match to one statement template. xACTION can match multiple statements to multiple rules. Suppose that you set up a trigger with 10 rules. All 10 must be matched by incoming statements, then xACTION can forward one of the incoming statements.
- xAPI can record lots of different data points, some of which may be important to you and others may not. For example, an instructional designer or content developer may send statements showing every action a student takes within a piece of content – how they navigate, what they click on, if they fast forward video, etc. That may be great data but what if you only need to capture completions or scores and don’t need the extra information in your Authoritative LRS or system of record?
- xACTION can “Transform” a statement, using pieces of incoming statements. For example, you could use the Verb from the statement that matched Rule 1, and the Object from the statement that matched rule 3. Or you can create an entirely new statement from different statements which are matched to Trigger Rules and then a brand new statement is sent out.
- Governance – If you have a data model where you have defined how learning and career data is recorded. An off the shelf content module may not follow your data model. You can take their xAPI data and transform it into a new statement following your rules and using your vocabulary.
