Hello, how can we help you?

Recent Searches: Changelog - Process - Changelog - Business rule - Configuring a multi-language knowledge base - Adding costs

Configuring reward types

Shield icon with a star, which leads to the challenge creation step, where the user can configure a new challenge. Gear icon that leads to the configure reward type step, where the requirement configurations are made. Coin icon that leads to the Create reward step, where the reward details are entered. Shopping cart icon that leads to the redeem reward step, where the user can select and obtain their available rewards.

 

Prerequisite

  • Access to the Configuration > Reward type (GM006) menu.

 

Introduction

To add rewards in SoftExpert Gamification, reward types must be created. 

They classify created rewards. See how to configure them below:

 

Configuring a reward type

1. Access the Configuration > Reward type (GM006) menu.

2. Click on the Add icon. button to add a new type.

3. On the screen that will open, enter an ID # and a name

4. If you wish, fill in the Upper level type field in the General tab. This field allows for defining a hierarchy for reward types.

5. Then, click on Save icon. to enable more tabs.

6. In the Type security tab, click on the Add icon. side toolbar button to add a permission profile to the type.

7. In the Reward security tab, using the Add icon. button, define a permission profile for the rewards of this type.

To learn how to add permission profiles, access the Associating a permission profile with the security article.

 

In SoftExpert Gamification, reward security lists are inherited from the reward type. For this reason, it is not possible to disable the Inherit reward type security list (default) option in the Reward security tab.

 

8. Click on Save and exit icon. to finish the creation.

User following the steps described above to create and configure a reward type.

 

Conclusion

The reward type has been recorded. Now, it will be possible to create rewards that will be redeemed by the user.


Was this article helpful?