Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scheduler name is “Auto loyalty update”
will update all persons benefits status or clear it if it fit some restriction

Default restrictions

Days without subscription without lost of loyalty status is set to 30

To become a loyalty level 1 memeber user need be a member for 3 years minimum with end date not less then 30 days before today

To become a loyalty level 2 memeber user need be a member for 7 (TP53764 / 2023.4005)

Purpose

Automatically update the “Benefit status” property on persons based on how long they have been a member for.

Configuration

  1. Create the loyalty levels as “Benefit status” in configuration/benefit-status

  2. Decide how many years the persons need to be members for to reach each level.

  3. Decide how many days gap there can be between two memberships to still base the loyalty level as for a non broken membership period.

  4. BRP Staff will check the “Benefit status IDs” for the Benefit status objects.

  5. BRP staff will configure and enable the scheduled task “Run auto loyalty update”

Functionality

If the scheduled task is enabled, the benefit status for persons will be updated every night

  • If the person qualifies for one of the configured levels, the one that requires the most numbers of years will be set.

  • If the person does no longer qualify for any of the specified levels the benefit status will be cleared

Parameters

allowedDaysPause

Default value (if not configured) is 30 days.

allowedDaysPause=20 will change this to 20 days.

yearsToBenefitStatusMap

Number of years-BenefitStatusID1;Number of years-BenefitStatusID2;Number of years-BenefitStatusID3

Example of parameters

To become a loyalty level 1 member the person needs be a member for 3 years minimum with end date not less then 30 20 days before today

Change restrictions parameters

User can do it with some schedule setups:

allowedDaysPause - will change amount of days without subscription that allow person to keep loyalty status
yearsToBenefitStatusMap - map of years to become some related loyalty level

Its not required to set all 3 parameters if user need to change only one, you can set only those that you need to change

Full parameters list example

this exaple will set days without subscription to 20, status “1” after 10 year and “2“status after 7 years.

After 5 years: Level 2

After 10 years: Level 3

Higher value for number of years has priority, so after 10 years I get status 3, not 1 or 2.

Code Block
allowedDaysPause=20
yearsToBenefitStatusMap=

...

3-1;

...

5-2;10-3