Support recently informed me while working on behalf of Nutrabolt that icentives with rules with an issuance limit (for example max 2 incentives per year) limit the maximum issuance potential of the program even if that setting lives at the rule level. I propose that we remove this limitation so that clients can maintain the same program and just create new rules for each year without the worry of users running into this program cap.
Client Name | Nutrabolt and all clients |
Employee Name | Steve Kluchin |
I meant to say "Hey Chris"
Hey
Even though product plans to create a "duplicate/copy feature". Clients intuitively see the rule function similarly to "Cycles" in Grants Connect. If we're making the exact same incentive program, it makes more sense to just have another rule. Is it not possible to have the rule attributes attached to the rule only and not the incentive program?
More reasons to have this enhancement
The UX is confusing if an attribute/configuration lives in the rule but is attributed to the whole program
If we can have 2 different rules in the same program e.g. one rule as manual and one rule for Volunteer Hours, will the limit in one rule also affect the whole program and prevent incentives being issued in another rule? If so, this is intuitively confusing/ contradictory since you can have more than one rule per program.
If we decide to do this enhancement can we make sure the Incentive rule is an attribute for Tableau/ad hoc, so that there will be accurate reporting?
Hey Steve, thank you for your submission. Standard practice for managing incentive programs and rules because of their overlapping limitation and settings, is by design and those best practices include creating a new program and rule per year/new program. In the future, product plans to enhance incentive programs and rule creation with a copy program and copy rules functionality which will solve this issue. Because of that we will be closing this idea as we do not want to remove that limitation that is set by design. Thanks!