Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The Admin Panel is the place within Splash where you manage all the Game Actions, Custom Actions, and Game Transactions in the system. 

Game Actions:

Game Actions are activities that are tracked by Splash for the purpose of determining if a user has completed a Challenge or Game Activity. For example, if an organization wanted to setup a Lead Generation Challenge that required users to enter 35 Leads within one week the Game Action would be the specific "action" of creating a Lead in SugarCRM. The paramenters of Challenge like "Quantity" or the number of times the action must be taken are configured within the Challenge when configuring the "Game Activity". For more details see the Splash Guide on "Creating Challenges, Badges, Rewards and Levels".

There are the standard Actions that are preconfigured by the system when the first Game is initiated. A full list of Game Actions can be seen by navigating to Admin > Game Actions. 


Custom Actions:

These are the custom actions you can set up if the standard actions provided don't cover your needs. Maybe you want to give points for the number of meetings held for example. Here you can see all the created actions.


Game Transactions:

Here you can see all the actions completed by the players. Here you can see what each person has done and how often they are completing actions.:



Creating Custom Actions:

  1. To create a Custom Action: 
    1. Go to custom actions and click on add custom actions
    2. You will need to enter the name, and the action, the point category and the number points they earn each time they compete the action. Finally click the checkbox if you want the action to be active.
    3. Once all done, click on create. You will now have to define the custom action condition. A new  area will appear below and you will need to click on add new
    4. You will need to enter the name of the condition, the module, the old status and then the new status. An example would be setting the condition to be if a meeting (module) goes from planned (old status) to held (new status) then the condition is met. 
    5. Once the condition is added you can create the action. 


  • No labels