Rewards & Recognition: Limit Awards to once a month

[AndresCarter]

There has been a business requirement within SuccessFactors Rewards & Recognition where employees should only receive one award per month. This is either through a peer-to-peer process from the Rewards & Recognition landing page or from People Profile. In this blog, we will show how this is achievable through a validation rule on the SpotAward object.

From Admin Center> Object Definitions select the SpotAward object and 'Make Correction'.

Under the 'Validation Rules' click on the plus button to create and add a new rule.

The rule should be created as follows:

The following is happening in this rule.

- Capture award creation date
(create a custom date column on the SpotAward object and have the rule stamp current date into it)

- Variable to generate the 1st of the next month

- Obtain previously created award issue date
(this is program specific as well as the program having a unique component associated with it)

- Compare current award creation date vs previously created award taking into consideration 1st next month Variable

Note:
You may also want to include the last day of the previous month so you can create a period to do a comparison of date to determine whether you allow or disallow the award creation.

Once the rule is saved in the popup, close this page, select the new rule in 'Validation Rules' and save the object definition.

When processing an award where there is already an existing award published, we'll receive the following error.

To create the message which appears, go to Manage Data and create a Message Definition which you can reference in the validation rule.

This would only work from nominations which come from the Rewards landing page and Home Page quick card. If you would like this also trigger through People Profile, create a similar rule on the payComponentNonRecurring element as an onSave rule.

To ensure the rule is running as expected through testing, create a 'Rule Trace' in Manage Data to see the variables, dates, etc being called. Below is an example:

This is great for troubleshooting rules to better understand what they do when being triggered and why x may not be happening as you would expect.