HomeGuidesDeveloper HubRelease Notes
Get supportBook a chat
Release Notes
These docs are for v2.96. Click to read the latest docs for v2.208.

Spring '21 Package Updates

View and install the latest updates of our Spring '21 release.

PLT Package Versions x Issues Fixed

2.114.61
Install
(Note: If you skipped the 2.114.52 and 2.114.53 upgrades, you must follow the post-upgrade instructions under 2.114.53.)

  • Fixed [FL-12423] - Redemption not created via REST API when Member status is Opt-out and there is no Opt-out Expiration Period

    Functionality affected: Member Opt-Out

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12430] - After reverting Tracker, leaderboard position is not reset to previous state

    Functionality affected: Challenges

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12456] - Unable to revert Tracker of login event

    Functionality affected: Challenges

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12577] - It's possible to change the mission action when the challenge has progress and is in Edited status

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12608] - Cannot extend the email campaign form

    Functionality affected: Messaging

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? On the Email Template object, create a custom field set called FieloEmailTemplate and on the Email Campaign object, create a custom field set called FieloEmailCampaign.


  • 2.114.60
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12581] - On "Earned" tab in the Badge component, instead of the translated Challenge name, the original Mission name is displayed

    Functionality affected: Badges LC

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12584] - Editing the start date to the future in an Active challenge creates a new version without applying changes

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12586] - Member is not earning points after editting rules from No Competition to Best Option and clearing the cache

    Functionality affected: Promotions

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.59
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12397] - Challenge Component showing Global Challenges

    Functionality affected: Challenges LC

    Is there any new dependency or effect caused by this fix? Instead of showing the Enroll button on Global Challenges, the component will display text indicating that enrollment is automatic.

    Are there any upgrade steps required? No.


  • Fixed [FL-12426] - Leaderboard Value stays the same even after reverting the Tracker

    Functionality affected: Reversion on Challenges

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12460] - Missing custom label for "Challenges" label on the Challenges component

    Functionality affected: Challenges LC

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12465] - If program agreement is updated, the member record cannot be edited until the member accepts the new version of the agreement

    Functionality affected: Agreements

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12475] - Change rule criterion to Dynamic - Processing fails before applying changes, when it should fail only after

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12476] - Editting a rule that has a related list condition with two or more fields, and removing one field, and not applying changes, the changes are applied regardless

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12483] - Rule has two related list conditions and Match criteria is ANY - Edit to ALL - and don't apply changes - changes are still applied

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12497] - Error when Mission start/end dates are changed without applying changes

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12535] - Error when a related list condition is removed without applying changes

    Functionality affected: Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12536] - FieloPLT__Level__c.Name not retrieved

    Functionality affected: API: MemberService

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.57
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12404] - Member's balance is rolled back if earns points while Segment batch job is running

    Functionality affected: Segmentation

    Is there any new dependency or effect caused by this fix? The batch now records only the fields that will be changed during processing so that it does not overwrite member balances.

    Are there any upgrade steps required? No.


  • Fixed [FL-12410] - Date/Time Field not working on segment criteria

    Functionality affected: Criteria

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12412] - Name of the Incentive is not translated on the "Earned for" section of the Badge component

    Functionality affected: Badges LC

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.56
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12387] - Promotion with cap is not rewarding correctly

    Functionality affected: Caps

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12395] - Insufficient Balance error when creating Adjustment Transaction

    Functionality affected: Adjustment Transactions

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12400] - User Cannot create a Rule on Promotion because Lookup of Action not loading on criteria screen

    Functionality affected: Fielo Admin Permission Set

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12403] - Challenges are not being incentivized, scheduled status on version

    Functionality affected: Challenges, Versioning

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.55
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12395] - Insufficient Balance error when creating Adjustment Transaction

    Functionality affected: Adjustment Transactions

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.54
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12368] - Class PointsPartialExpirationBatchSchedule - public constructor is breaking customer customization

    Functionality affected: Points Expiration batch

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12369] - Provider Orders not working when accrual cap is active

    Functionality affected: Provider Order

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.53
    Install
    (Note: If you skipped the 2.114.52 or 2.114.53 upgrade, you must follow the instructions below.)

    Post-Upgrade Instructions (2.110 - 2.114.48 → 2.114.53):
    1. From Salesforce, click on the gear icon and select Developer Console.
    2. From the Developer Console, open the Debug menu and select Open Execute Anonymous Window.
    3. Execute the following code block:
      List<FieloPLT__Version__c> versionsToUpdate = [SELECT Id, FieloPLT__RelatedObjectType__c, FieloPLT__Challenge__c, FieloPLT__Promotion__c, FieloPLT__Rule__c, FieloPLT__Level__c, FieloPLT__Mission__c, FieloPLT__ChallengeReward__c FROM FieloPLT__Version__c WHERE FieloPLT__RelatedObjectType__c = null AND (FieloPLT__Challenge__c != null OR FieloPLT__Promotion__c != null OR FieloPLT__Rule__c != null OR FieloPLT__Level__c != null OR FieloPLT__Mission__c != null OR FieloPLT__ChallengeReward__c != null) LIMIT 200];
       
      if (versionsToUpdate.isEmpty())
          throw new FieloPLT.FieloException('NOTHING TO FIX');
       
      for (FieloPLT__Version__c version : versionsToUpdate){
          if(version.FieloPLT__Promotion__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Promotion';
          }
          else if(version.FieloPLT__ChallengeReward__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Challenge Reward';
          }
          else if(version.FieloPLT__Challenge__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Challenge';
          }
          else if(version.FieloPLT__Mission__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Mission';
          }
          else if(version.FieloPLT__Level__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Level';
          }
          else if(version.FieloPLT__Rule__c != null){
              version.FieloPLT__RelatedObjectType__c = 'Rule';
          }
      }
       
      FieloPLT__Triggers__c triggerVersion = FieloPLT__Triggers__c.getInstance(UserInfo.getUserId());
      triggerVersion.FieloPLT__Version__c = false;
      upsert triggerVersion;
      update versionsToUpdate;
      delete triggerVersion;
      • Repeat this step until you receive an Execute Anonymous Error that says "NOTHING TO FIX".
    4. Now, clear the previous code and execute this code block:
      List<AggregateResult> versionsDuplicate = [SELECT FieloPLT__Level__c, FieloPLT__Promotion__c, FieloPLT__Rule__c, FieloPLT__Challenge__c, FieloPLT__Mission__c, FieloPLT__ChallengeReward__c, FieloPLT__IsCurrentVersion__c, COUNT(Id) totalDuplicates
      FROM FieloPLT__Version__c
      WHERE FieloPLT__IsCurrentVersion__c = true AND (FieloPLT__Level__c != null OR FieloPLT__Promotion__c != null OR FieloPLT__Rule__c != null OR FieloPLT__Challenge__c != null OR FieloPLT__Mission__c != null OR FieloPLT__ChallengeReward__c != null)
      GROUP BY FieloPLT__Level__c, FieloPLT__Promotion__c, FieloPLT__Rule__c, FieloPLT__Challenge__c, FieloPLT__Mission__c, FieloPLT__ChallengeReward__c, FieloPLT__IsCurrentVersion__c
      HAVING COUNT(Id) > 1
      LIMIT 100];
       
      if (versionsDuplicate.isEmpty())
          throw new FieloPLT.FieloException('NOTHING TO FIX');
       
      Set<Id> promotionIds = new Set<Id>();
      Set<Id> ruleIds = new Set<Id>();
      Set<Id> challengeIds = new Set<Id>();
      Set<Id> missionIds = new Set<Id>();
      Set<Id> challengeRewardIds = new Set<Id>();
      Set<Id> levelIds = new Set<Id>();
      for (AggregateResult version : versionsDuplicate){
         
          if(version.get('FieloPLT__Promotion__c') != null){
              promotionIds.add((Id) version.get('FieloPLT__Promotion__c'));
          }
          else if(version.get('FieloPLT__Rule__c') != null){
              ruleIds.add((Id) version.get('FieloPLT__Rule__c'));
          }
          else if(version.get('FieloPLT__Challenge__c') != null){
              challengeIds.add((Id) version.get('FieloPLT__Challenge__c'));
          }
          else if(version.get('FieloPLT__Mission__c') != null){
              missionIds.add((Id) version.get('FieloPLT__Mission__c'));
          }
          else if(version.get('FieloPLT__ChallengeReward__c') != null){
              challengeRewardIds.add((Id) version.get('FieloPLT__ChallengeReward__c'));
          }
          else if(version.get('FieloPLT__Level__c') != null){
              levelIds.add((Id) version.get('FieloPLT__Level__c'));
          }
      }
       
      List<FieloPLT__Version__c> versionsToFix = [SELECT FieloPLT__Level__c, FieloPLT__Promotion__c, FieloPLT__Rule__c, FieloPLT__Challenge__c, FieloPLT__Mission__c, FieloPLT__ChallengeReward__c, FieloPLT__VersionNumber__c, FieloPLT__IsCurrentVersion__c
      FROM FieloPLT__Version__c
      WHERE FieloPLT__IsCurrentVersion__c = true AND (FieloPLT__Level__c IN :levelIds OR FieloPLT__Promotion__c IN :promotionIds OR FieloPLT__Rule__c IN :ruleIds OR FieloPLT__Challenge__c IN :challengeIds OR FieloPLT__Mission__c IN :missionIds OR FieloPLT__ChallengeReward__c IN :challengeRewardIds)
      ORDER BY FieloPLT__VersionNumber__c];
       
      // build the list in ascending order
      Map<Id,List<FieloPLT__Version__c>> versionsByParent = new Map<Id,List<FieloPLT__Version__c>>();
      for (FieloPLT__Version__c version : versionsToFix) {
         
          version.FieloPLT__IsCurrentVersion__c = false;
       
          Id parentId = version.FieloPLT__Level__c != null ? version.FieloPLT__Level__c : version.FieloPLT__Promotion__c != null ? version.FieloPLT__Promotion__c : version.FieloPLT__Rule__c != null ? version.FieloPLT__Rule__c : version.FieloPLT__Challenge__c != null ? version.FieloPLT__Challenge__c : version.FieloPLT__Mission__c != null ? version.FieloPLT__Mission__c : version.FieloPLT__ChallengeReward__c != null ? version.FieloPLT__ChallengeReward__c : null;
         
          if (versionsByParent.containsKey(parentId)) {
              versionsByParent.get(parentId).add(version);
          } else {
              versionsByParent.put(parentId, new List<FieloPLT__Version__c>{version});
          }
      }
       
      // remove the last element from the list and build the final list to update
      List<FieloPLT__Version__c> versionsToUpdate = new List<FieloPLT__Version__c>();
      for (Id parentId : versionsByParent.keySet()) {
          List<FieloPLT__Version__c> versions = versionsByParent.get(parentId);
          versions.remove(versions.size()-1);
          versionsToUpdate.addAll(versions);
      }
       
      FieloPLT__Triggers__c triggerVersion = FieloPLT__Triggers__c.getInstance(UserInfo.getUserId());
      triggerVersion.FieloPLT__Version__c = false;
      upsert triggerVersion;
      update versionsToUpdate;
      delete triggerVersion;
      • Repeat this step until you receive an Execute Anonymous Error that says "NOTHING TO FIX".
    5. Finally, from Salesforce Setup, search for and select Platform Cache. Click on the partition called Settings in the FieloPLT namespace, then select Clear Cache.


  • Fixed [FL-12020] - Listview of Rewards Catalog LC is failing and Promotion LC description is not showing

    Functionality affected: Fielo Communities Lightning Components

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12283] - Create Challenge from Model is failing

    Functionality affected: Models

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12320] - Members able to enter a Challenge for which they are not eligible

    Functionalities affected: Versioning, Fielo Communities Lightning Components

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12323] - Incorrect leaderboard positions being assigned

    Functionality affected: Leaderboards (Challenges)

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12339] - Cannot create a mission

    Functionality affected: Challenges

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.

  • 2.114.52
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12231] - Level assigned incorrectly when member initially created

    Functionality affected: Levels

    Description: Members are being assigned a higher level than they qualify for upon initial creation. Assignment is only corrected the next time the Assign Levels batch is run. However, the incorrect level in the meantime could trigger an undesired incentive reward.

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12232] - Points attributed for Rules where rule conditions are not met

    Functionality affected: Rules Engine

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12233] - Adjustment Transaction creation error after clearing cache

    Functionality affected: Rules Engine

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12236] - Versioning-related error upon challenge activation

    Functionality affected: Challenges (Rules Engine)

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12240] - CPU Limit Exceeded with too many segments

    Functionality affected: Segmentation

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12242] - Time Table table type is not working

    Functionality affected: Challenges (Rules Engine)

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12187] - Segments disappeared from the member

    Functionality affected: Segmentation

    Note: Fixed as part of FL-12240

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12257] - Not able to create a new program

    Functionality affected: Programs

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12266] - Apex CPU time limit exceeded

    Functionality affected: Rules Engine

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12270] - processRecords throwing null pointer exception

    Functionality affected: Rules Engine

    Note: Fixed as part of FL-12266

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12279] - Update Payout Status batch hitting Apex limit

    Functionality affected: Payouts

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 2.114.48
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12223] - Custom labels for Subscribe button in PLT and Module # in ELR are missing

    Functionality affected: Fielo Communities Lightning Components

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.

  • Fixed [FL-12208] - Incorrect calculation of member points due to excessive batch size on method call

    Functionality affected: Rules Engine

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.

  • 2.114.47
  • Fixed [FL-12028] - The condition deleted in the criteria is not being deleted from the database

    Functionality affected: criteria (from levels, segments, rules, and missions).

    Expected behavior: when deleting a related list condition, the Criterion Group and Condition related to the condition should be deleted from the database.

    Case: in a program, there is a segment that uses a related list condition. The user edits this segment in order to delete the related list condition and create a new one. Instead of the system deleting the Criteria Group and Condition from the database and creating new ones related to the new related list condition, it does not delete the Condition. Because of this, he org keeps storing unnecessary content.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  •  
  • Fixed [FL-12020] - Issues on the Catalog and Program Promotions Lightning Components

    Functionality affected: Lightning Components for Experience Cloud Sites.

    Expected behavior: the promotion's description should be displayed in the component if the FieloPLT__Description__c/richtext field is still in the Program Promotion's Promotion Detail Fields field (in the Builder). Rewards should be displayed side by side if the grid layout is selected.

    Case: in a program, there is a promotion with description and some rewards. When the admin removes the FieloPLT__Description__c/richtext field from the  Program Promotion's Promotion Fields field (in the Builder), the description isn't displayed in the portal for the members.

    Moreover, If the member selects the layout Grid in the component Fielo - Catalog, the rewards are not displayed side by side.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  •  
  • Fixed [FL-12038] - Member is able to do redemptions when they don't have point records

    Functionality affected: redemption.

    Expected behavior: members with a currency balance that is higher then it should (e.g. due to a calculation mistake or currencies that were not given through a transaction), should not be able to use this balance to redeem rewards.

    Case: a program member has received 100 Points that are not related to a point record or a transaction. Meanwhile, their actual sum of Points balance (from Point records) is lower than their balance: 50 Points. When they try to redeem a reward that costs 100 Points, the redemption goes through and the member receives the reward.

    Is there any new dependency or effect caused by this fix? after the fix, the system will now validate first if the member meets the following requirement before allowing them to redeem a reward: Redemption.cost ≤  Member.Balance AND Redemption.cost ≤  Sum(Member.Points.Balance).

    Are there any new steps to use the affected functionality? no.

  •  
  • Fixed [FL-12032] - The user isn't able to deactivate Capping if the related rule was deleted

    Functionality affected: Capping.

    Expected behavior: the user should be able to deactivate a cap whenever needed.

    Case: In a program, there is a cap by period with Limit of 50000 Cash (a currency that generates payout) configured and set to apply to Specific Rules. The admin deletes the rule specified in the cap and, then, tries to deactivate the cap, but is not able to.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  •  
  • Fixed [FL-11988] - Expiration batch gives Time Out error when ORG has a high volume of Point records

    Functionality affected: currency expiration.

    Expected behavior: provided that a currency has an expiration date defined, when the expiration batch runs, it should expire the currencies that have the expiration date is in the past.

    Case: in a program, the members who have accomplished a behavior receive a number of Points as a reward and some of these Points have a defined expiration date. In this program's ORG, there are 20 million Point records in total.

    In this case, the issue was in in the fact that there was a high volume of Point records that needed to be processed by the query used to find the points that should expire (which is within the expiration batch): SELECT Id FROM FieloPLT__Point__c WHERE FieloPLT__ExpirationDateCheck__c != null AND FieloPLT__ExpirationDateCheck__c <: strToday ORDER BY FieloPLT__Member__c

    When the expiration batch runs, a time out error occurs.

    Is there any new dependency or effect caused by this fix? The issue is the comparison with null values in the query to find the points that should be expired in the expiration batch process. So, the fix consists of replacing in the query the comparison of != null in the FieloPLT__ExpirationDateCheck__c by > '19000101' and adding a LIMIT of 50M.

    Are there any new steps to use the affected functionality? no.

  • 2.114.45
  • Fixed [FL-11964] - Error message being displayed after activating/deactivating Level

    Functionality affected: Levels

    Expected behavior: No error displayed.

    Case: When admin activates or deactivates a level, an unexpected error message is displayed.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-12023] - Image source path changing with Community Prefix

    Functionality affected: Fielo Communities Lightning Components

    Case: FieloPLT is including the community prefix to the source of images stored inside Salesforce. This affects customers that are using custom domain, wherein the community prefix is not in the community URL. This is causing the badge image to not display in the community.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • 2.114.44
  • Fixed [FL-12015] - Inactive promotions showing up on Community Lightning component

    Functionality affected: Fielo Communities Lightning Components that display incentives

    Expected behavior: Inactive incentives are not shown.

    Case: Incentives that have been deactivated are still being displayed to members on the Community (Digital Experience Site) LC.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • 2.114.43
  • Fixed [FL-11988] - Expiration batch gives Time Out error when ORG has a high volume of Point records

    Functionality affected: currency expiration.

    Expected behavior: provided that a currency has an expiration date defined, when the expiration batch runs, it should expire the currencies that have the expiration date is in the past.

    Case: in a program, the members who have accomplished a behavior receive a number of Points as a reward and some of these Points have a defined expiration date. In this program's ORG, there are 20 million Point records in total.

    In this case, the issue was in in the fact that there was a high volume of Point records that needed to be processed by the query used to find the points that should expire (which is within the expiration batch): SELECT Id FROM FieloPLT__Point__c WHERE FieloPLT__ExpirationDateCheck__c != null AND FieloPLT__ExpirationDateCheck__c <: strToday ORDER BY FieloPLT__Member__c

    When the expiration batch runs, a time out error occurs.

    Is there any new dependency or effect caused by this fix? The issue is the comparison with null values in the query to find the points that should be expired in the expiration batch process. So, the fix consists of replacing in the query the comparison of != null in the FieloPLT__ExpirationDateCheck__c by > '19000101' and adding a LIMIT of 50M.

    Are there any new steps to use the affected functionality? no.

  • 2.114.42
  • Re-evaluated [FL-11968] - When creating a Behavior with the Opportunity object, the eligibility fields do not load

    Previously corrected for package 2.114.41, it was reopened and correction was added to 2.114.42 version.

  • 2.114.41
  • Fixed [FL-11968] - When creating a Behavior with the Opportunity object, the eligibility fields do not load

    Functionality affected: behavior.

    Expected behavior: after the User selects an object when they are creating a new Behavior, the “What date should determine the eligibility of actions performed?” picklist should load all the Date Type fields from the object, so that the user can choose one.

    Case: when trying to create a Behavior with Opportunity as the object that we want to incentivize, its fields don’t load in the “What date should determine the eligibility of actions performed?” picklist. When selecting another object, these object fields are shown, but selecting Opportunity again, the fields of the previous object are still shown.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11970] - Performance issue on the ChallengesRewards Class when it has Inner Queries

    Functionality affected: ChallengesRewards Class (API)

    Expected behavior: the system should process the query sent to create a reward.

    Case: this issue occurs in Orgs with a great amount of data; in this case, there are more than 700 missions in the query.

    In a program that has a challenge mission that incentivizes the members to accomplish at least the 3 courses (each course with 2 Modules), the admin wants to reward the members who accomplish the mission with a Badge. The admin defines the mission's rewarding scheme as Just one reward, one or more times to be delivered when the mission is accomplished. When he is creating the reward and tries to select the Badge, an An internal server error has occurred error appears.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • 2.114.40
  • Fixed [FL-11962] - Profile image cannot be uploaded

    Functionality affected: Profile Lightning Component.

    Expected behavior: if a member wants to upload a profile picture to the Portal profile, they are able to.

    Case: when the member tries to upload a profile picture through the Profile Lightning Component, they receive an error that says "document cannot be inserted".

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11963] - Challenge's image and description overlapping the component's frame

    Functionality affected: Challenges Lightning Component.

    Expected behavior: the Challenges Lightning Component should display the challenge's image and description within the tile's frame limit.

    Case: the Component displays the challenge's image cut or outside the tile's frame, instead of just reducing it to fit the frame. Also, the long description is displayed in only one line, instead of being broken to fit the frame.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11964] - Platform displays an error when activating or deactivating a level

    Functionality affected: levels.

    Expected behavior: levels should be activated or deactivated whenever the user needs without any issues.

    Case: in a program, there is an active level. When the user clicks on the button to deactivate it, a A Component Error has occured! error shows up. The same happens when activating a deactived level.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11966] - Members are not automatically enrolled in global challenges.

    Functionality affected: challenges.

    Expected behavior: if a challenge has a Global subscription mode, when the member performs the Action being incentivized (and mee the criteria, if any) he is enrolled into the challenge automatically.

    Case: In a program, there is a Promotion Rule that rewards an amount of Points and also creates an Event with type = Points, as defined by a Salesforce flow. In the same program, there is a Challenge Mission (Compare Among Members) that incentivizes the Events with type = Points. When the member accomplishes the Promotion Rule, he should (as a consequence) be automatically enrolled in the Challenge because the Points Event was created, but he isn't.

    The challenge in this case has a segment.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Re-evaluated [FL-11897] - Missing custom labels, that cannot be translated

    Previously corrected for package 2.114.39, it was reopened and correction was added to 2.114.40 version.

  •  
  • Improved [FL-11957] - Member's balance not updated correctly due to concurrency issue, causes error in expiration process

    Functionality affected: Points accrual.

    Expected behavior: the member should receive the Currencies (e.g. Points) as defined in the program (e.g. from an incentive). These Points received should be available to be expired, if configured.

    Case: in a program where a member has 100 Points, 2 transactions are created almost at the same time. However, the member's balance is updated only by one of the transactions. Since the member balance does not correlate to the amount of points related to this member, when Fielo tries to expire the Point the process fails, resulting in members sustaining expired points.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.
  • 2.114.39
  • Improved [FL-11897] - Missing custom labels, that cannot be translated

    Functionality affected: Experience Cloud Site, Labels.

    Expected behavior:custom labels are available for translation.

    Case: in a program, which has a portal built on Salesforce's Experience Cloud, the admin needs to translate the Fielo lightning component labels. However, some labels cannot be found.

    This is a list of the labels and their respective lightning component: View Challenge (Challenges LC), Missions (Chellenges LC), Overview (Incentives LC), Challenge (ChallengesLC), All (Incentives LC), Description (Challenges LC).

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • 2.114.38
  • Fixed [FL-11887] - Date & Time field is being updated only with the date

    Functionality affected: transaction.

    Expected behavior: the Date & Time (FieloPLT__Date__c) field in the Transaction object should be updated with the date & time of when the transaction was created.

    Case: when a transaction is generated by a Challenge Reward, the field called "Fecha Transacción" (Date of Transaction) is completed only with the Date and not with Datetime (as it should). The impact is that when it is used, the day reflected is Day-1 when the country is in any (-) TimeZone.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11885] - Redemption Items with wrong status

    Functionality affected: redemption.

    Expected behavior: when the redemption has a transaction related to it, and a Rule or a Challenge Rewarding assigned to it, its Redemption Items should have the Delivered status.

    Case: in a program, there is a challenge which is rewarding an instant reward. When the member accomplishes the mission, a redemption is automatically created to deliver the instant reward to them. The redemption item related to it should have a Delivered status, but it has a Ready status.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • 2.114.37
  • Fixed [FL-11762] - Active or Scheduled challenges don't change the status

    Functionality affected: challenge.

    Expected behavior:the challenge's status should be automatically changed according to its Start and End dates.

    Case: when the challenge's Start Date is in the past, the challenge doesn't change from Scheduled to Active and, later, to Ended (if the End date is reached without any accomplishments). Likewise, when the End Date is reached, the Challenge's status doesn't go to Ended.

    Is there any new dependency or effect caused by this fix? the Challenge Status batch was improved so that if only a few records return an error, the others will still work as expected. The ones that failed will not be processed and will generate an error Log record.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11753] - Error when extending the Incentives form

    Functionality affected: Extending a form.

    Expected behavior: when the user adds custom fields in the Promotion object and wants to add them to the Incentive form, it should not impact the Challenge.

    Case: admin created 5 custom fields in the Promotion object and added them to the Promotion form by using the incentivesForm_extended.json JSON. After that, they started to receive an error every time that they tried to edit a Challenge.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • 2.114.36
  • Fixed [FL-11725] - Not able to create behaviors for objects that have the same label

    Functionality affected: Behavior.

    Expected behavior: Aside from the objects that cannot be incentivized, the member must be able to create a behavior for the any object.

    Case: In an Org, there are 2 objects with the label "Account". When the user tries to create a new behavior, only one of these objects show up on the "Select the object that you want to incentivize" list.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11732] - AODA compliance for visually impaired people

    Functionality affected: Member Selector lightning component.

    Expected behavior: as major visually impaired people uses the tab key, the focus order needs to follow the proper fields sequence and not focus on what is not useful for the user, as defined by "Accessibility for Ontarians with Disabilities Act" (AODA). Therefore, only elements that are meant to be interacted with should receive keyboard focus.

    Case: the main content within the tab display panel area receives keyboard focus, such as the plain text.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • 2.114.35
  • Fixed [FL-11549] - Not able to choose February 29th as payout date

    Functionality affected: payout.

    Expected behavior: when setting up an incentive, the user can choose February 29th as the payout date. In this case, the system processes payout records on February 28th in common years.

    Case: when trying to create a promotion rule rewarding Cash with the payout date mode set to be annually on February 29th (payout month = 2 and payout day = 29), the system says that the date is invalid.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11610] - Error when using the FieloPLT.TrackerService Class

    Functionality affected: API FieloPLT.TrackerService Class.

    Expected behavior: Whenever the user needs to revert a tracker and uses the API for that, the record should be reverted.

    Case: In a program that has a behavior related to a custom object, there is a challenge that incentivizes this behavior. The challenge gives a reward when the mission is accomplished, considering that the mission's objective is to SUM event value with value mode = dynamic. After the member accomplishes the mission, the admin needs to revert the tracker generated and for that he uses FieloPLT.TrackerService.revertTrackers(new Set< Id >{'TRACKER_ID'}, new Set< Id >{'EVENT_ID'}, null);.

    The API returns the error System.SObjectException: SObject row was retrieved via SOQL without querying the requested field.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  • Fixed [FL-11645] - Fielo install fails on Salesforce Spring '22 version.

    Functionality affected: Salesforce upgrade.

    Expected behavior: Fielo should keep working as expected after Salesforce update to the Spring '22 version.

    Case: when the user tries to install Fielo in an Org with the Salesforce Spring '22 version, the installation fails.

    Is there any new dependency or effect caused by this fix? all references to IsotopeSubscription were removed from Fielo's Page Layout metadata.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11599] - Inactivating a manual segment task doesn't finish and doesn't show errors.

    Functionality affected: segment.

    Expected behavior: the user can't deactivate a manual segment that is being used in an active incentive, Cap, Email Template, Reward, or Email Campaign.

    Case: in a program, there is an active promotion that uses a manual segment. When the user tries to deactivate the segment, the page doesn't finish to load, instead of displaying  a message informing that it's not allowed to deactivate the segment because its being used by a promotion.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • 2.114.34
  • Fixed [FL-11584] - Member is unable to create the second event when using the Cumulative scheme in mission rewarding.

    Functionality affected: mission rewarding.

    Expected behavior: when using the Cumulative Rewarding Based on Performance scheme, the member should be able to accumulate actions in order to reach the rewarding range(s) and win the reward(s).

    Case: a program with a Global challenge has a Compare among members mission which incentivizes the default Generate an Event and Win action and uses the Cumulative Rewarding Based on Performance scheme, with 3 rewarding ranges. When the member creates one event, a challenge member is created to them. When they try to create a second event, an error appears: FieloPLT.Events: execution of AfterInsert.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11553] - Payout is not created when the challenge rewarding's limit is higher than 1.

    Functionality affected: challenge rewarding.

    Expected behavior: when a challenge reward has a limit of 2 rewards per member, the member should receive the reward twice when they accomplish the mission(s), and not receive anything more after that.

    Case: program with a Global challenge has a Based on a fixed metric mission which incentivizes the default Generate an Event and Win action. This challenge has a challenge reward that uses the Just one reward, one or more times scheme

    , with limit = 2, and rewarding a currency that generates payout. When the member creates the first event (accomplishing the mission), they receive the payout, but when they create the second event, the payout is not generated.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11548] - Member doesn't receive mission reward when there are 2 actions using conditions that apply to the record processed.

    Functionality affected: challenges.

    Expected behavior: when the member performs the incentivized action, a challenge member is created and a reward is delivered (if applicable).

    Case: in a program, there are 3 incentives: two promotions and one Global challenges. The challenge and one of the promotions are incentivizing the action Opportunity Closed, while the second promotion incentivizes the action Closed Opportunities. Each of those actions are related to a different Behavior, one setup to track the closed date and the other, the created date.

    When the member closes an opportunity (meeting both the action's criteria), they receive the reward from the promotions, but they are not subscribed to the challenge and don't receive its reward.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11545] - Offline transactions that don't meet any action's criteria are not being discarded.

    Functionality affected: transaction processing.

    Expected behavior: whenever a transaction is processed offline (is asynchronous) and doesn't meet the incentive's segment and/or criteria, it should not be stored in the database.

    Case: in a program that is setup with Online Processing = false, a transaction is created. When the batch runs and evaluates that transaction, it checks that it doesn't meet the incentive and/or its segment criteria, but doesn't change the IsProcessed field from false to true. So, the next times that the offline transaction batch is executed, it will keep processing the same transaction over and over. Eventually, the number of transactions being processed can impact on the org's performance.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • 2.114.33
  • Fixed [FL-11506] - A new version of the challenge is not created when the mission’s criteria is edited

      Functionality affected: versioning.

    Expected behavior: whenever the admin deletes the criteria from a mission in an active challenge and applies the change, it should create a new version where this new change is taken into consideration.

    Case: the admin deletes the only condition set in a challenge mission. Instead of the challenge going to the Edited status so that the admin can click on Apply Changes, it continues active and the change is not saved. Therefore, the member is not being rewarded when they create an event that doesn't meet the condition that was set before.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11498] - After editing the rule’s criteria and applying the change, the old criteria is still being considered

        Functionality affected: versioning.

    Expected behavior: whenever data in the promotion is changed, it should create a new version where this new change is taken into consideration.

    Case: in a promotion, there is a rule with the criteria Event = Registration. After activating the promotion for the first time, the admin deletes the rule and applies the changes. When the member generates a Login event, he still receives the reward from the rule.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11465] - When a member meets the mission criteria, no Mission Member is created, but he receives the reward

    Functionality affected: challenge rewarding.

    Expected behavior: when a challenge with challenge rewarding setup has already finished, the member should not receive the reward.

    Case: in a program, there is a challenge that ended yesterday and that had the Based on performance metrics rewarding scheme setup for its challenge reward. When a member meets the mission criteria, no Mission Member is created, but he receives the reward.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11464] - In a challenge reward using a (1 OR 3) formula, Fielo was saving as if the admin had set the formula as ALL.

    Functionality affected: challenge rewarding.

    Expected behavior: when the admin sets up a formula that the member must meet (related to the completion of missions), the member should be rewarded according to the formula set.

    Case: in a challenge rewarding using the Just one reward, one or more times rewarding scheme, the admin uses the (1 OR 3) formula so that the member must accomplish mission 1 or mission 3 to be rewarded. However, the engine was not considering the formula, saving the configuration as if the admin had selected ALL instead of the formula. As a consequence, the member received more points than he should have.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11459] - Member receives the mission reward twice and missions that were not accomplished are reset

    Functionality affected: challenge and mission rewarding.

    Expected behavior: the challenge rewarding should not reset the progress from a mission that is not related to it or that has not been accomplished yet. Missions using the Just one reward, one or more times scheme should deliver the reward only once.

    Case: in a challenge with 3 missions, there is a challenge rewarding using the Just one reward, one or more times scheme, and the admin uses the (1 OR 3) formula so that the member must accomplish mission 1 or mission 3 to be rewarded. There is also a mission rewarding delivering a fixed amount of points when the member accomplishes mission 2. After meeting the criteria for all missions, the member received the mission reward twice (the mission had its progress reset) and the challenge rewarding reset missions that were not accomplished.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11455] - In a challenge where only the first position should receive the reward, the #1 member doesn’t receive it, but the #2 does

    Functionality affected: challenge rewarding.

    Expected behavior: a challenge rewarding using the Different rewards depending on the order of completion should deliver the reward only to the members who attain the position that has a configured reward.

    Case: there is a challenge that will reward only the member who first accomplishes the missions. 3 members accomplish the missions, but the member who should receive the reward doesn't receive it. Meanwhile, the member who is in the second position receives the reward.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11503] - The adjustment transaction related to an additional reward is not being created

    Functionality affected: additional rewarding.

    Expected behavior:  when the member accomplishes the rule that uses the additional rewarding, an adjustment transaction should be created to deliver the reward.

    Case: in a program, there is a promotion rule using an additional rewarding. When the member accomplishes the rule, the adjustment transaction to deliver the reward for them is not created. The member doesn't receive the reward.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11502] - After deleting a dynamic segment from a program and that was used in a promotion, the admin is unable to create events or to create a new member in all the programs in the org

    Functionality affected: event.

    Expected behavior: event should be created.

    Case: in an Org, there are 3 programs, each of them having a dynamic segment using a related list condition. On the third program, the admin creates and activates a promotion using the segment in that program, but they delete the segment later. After that, they are unable to create events or to create a new member, receiving the FieloPLT.Events: execution of AfterInsert error.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11494] - After being edited, Promotion rewards members who meet the new condition before the admin applies the changes

    Functionality affected: versioning.

    Expected behavior: whenever the admin changes anything in an active incentive, the system should process the incentive with the changes only after the admin clicks on "apply changes" on the edited incentive.

    Case: in a promotion, there is one rule with the Event = Login condition. The admin changes the condition to Event = Registration and doesn't apply the changes after saving. When a member generates a Registration event, they are rewarded.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11461] - In a program with a cap for rewards and that is associated with a segment, an error occurs when processing a promotion that rewards an instant reward

    Functionality affected: promotion and reward capping.

    Expected behavior: after the cap limit is reached and a member accomplishes a promotion rule that should give an instant reward, an empty transaction with Is Capped = true is created and related to the member.

    Case: there is a program set up with a cap for rewards (throughout the program), which is related to a dynamic segment. A promotion rule is giving an instant reward for the members who accomplish it. When a member who applies to the segment accomplishes the rule 2 times - and only the second time goes over the cap limit -, the FieloPLT.Events: execution of AfterInsert error appears and neither the transaction to reward the first time nor the empty transaction are created.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11452] - Member is unable to create an event when it should accomplish missions from 2 challenges, one using Singular Table Type and the other using Time Table

    Functionality affected: challenge rewarding.

    Expected behavior: whenever a member accomplishes the criteria from 2 challenges using different rewarding schemes for the challenge rewarding, the member should receive the reward from both challenges.

    Case: in a program, there are 2 challenges: one using the Just one reward, one or more times scheme rewarding 10 points, and the other using the Different rewards depending on the order of completion rewarding 1000 points for the first position. Both challenges have 2 missions that are set up the same way. When the member tries to create an event to accomplish the missions, the Nullpointer exception error appears.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11415] - After the admin inactivates one of the dynamic segments, the member is unable to create an event that would meet the conditions from a promotion that is not associated with a segment

    Functionality affected: segments.

    Expected behavior: the system should not process an inactive segment when evaluating if a member can or cannot participate in an incentive.

    Case: in a program where there are 2 promotions using 2 dynamic segments (one active and one ended) and 1 promotion without segments (ended), the admin inactivates one of the segments. When a member who does not apply to any segment tries to create an event that meets the promotion criteria, he receives the FieloPLT.Events: execution of AfterInsert error.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11390] - Redemption item codes are duplicated when codes start with 0

    Functionality affected: reward redemption.

    Expected behavior: item codes generated by redemptions should be unique.

    Case: in a program, whenever a member does a reward redemption, the item code is being duplicated. It was analyzed that this behavior was happening with codes starting with 0.

    Moreover, when a program has a great quantity of members, the codes can get duplicated. The way to mitigate this scenario is to define a high number to the redemption code through the Program Settings.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11519] - Mission Reward is being delivered even when the challenge is in Scheduled status

    Functionality affected: mission rewarding.

    Expected behavior: mission rewards should be delivered only when the challenge is active.

    Case: in program, there is a global challenge with a start date in the future and a mission that rewards 10 Points for the members who accomplish it. Even though the challenge is scheduled, the Points are being delivered to the members.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11513] - Deleting a segment that is assigned to a Promotion or a Challenge makes the promotion/challenge to not process any more rewards related to them

    Functionality affected: segments.

    Expected behavior: deleting a segment from the program should not be possible if it is being used in an active, edited, or scheduled incentive or course. Also not when the segment is in a reward or an active cap or email template.

    Case: in program, the admin is able to delete a segment that was applied to a promotion and to a challenge. This was causing an error when processing actions and any rewarding related to them.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11512] - Mission Member is being wrongly reset after getting the second reward when challenge reward limit =2

    Functionality affected: challenge rewarding.

    Expected behavior: when the rewarding limit is reached, the challenge should not deliver more rewards.

    Case: in a program, there is a global challenge with 2 missions and a challenge reward. The challenge reward has the Limit = 2 so that it delivers a maximum of 2 rewards, but after the reward is delivered for the second time, the mission member's progress is reset when it shouldn't be. This is causing the challenge to deliver the reward a third time to the member when they perform the incentivized action.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11538] - Member’s balance is not updated when they receive Points from a promotion and there is a challenge rewarding Miles. Both incentives use the same action

    Functionality affected: promotion.

    Expected behavior: when member performs incentivizes action that rewards them with currency, their balance is updated with the amount of currencies receibed.

    Case: a program has a challenge that rewards the Miles currency (when the mission is accomplished) and a promotion that rewards the Points currency, both incentivizing the same Action, but with different criteria. When the member performs the Action, they receive the reward from both incentives (i.e. transaction is created), but only their Miles balance is updated.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11539] - The challenge doesn’t go to edited status when the admin changes its period, a new version is not created

    Functionality affected: versioning.

    Expected behavior: when the admin changes the mission's date, the Apply Changes button should appear and a new version should be created.

    Case: in a challenge, there is a mission that will start tomorrow and end 30 days from now. After activating the challenge, the admin changes the mission's start date for today. The admin can't apply the changes and the member who performs the incentivized action today does not achieve the mission goal.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11536] - Payouts are not generated in batch processing of transactions

    Functionality affected: payouts.

    Expected behavior: all payout records should have a payout date.

    Case: a program which is configured to process transactions offline has 2 promotions rewarding payouts. The first promotion has a rule with 4 conditions and the payout date is set to immediately. The second promotion has a rule with 4 conditions and the payout date is set to quarterly (periodically).

    The admin uploads a bulk of records that meet the rules' criteria and runs the batch to process offline transactions. Some payout records are not created.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11526] - Capping: error creating a second event when there is a cap for Rewards with Calendar Period

    Functionality affected: reward capping.

    Expected behavior: when the member performs the incentivized action, a transaction is created and they receive the instant reward configured to be given.

    Case: in a program there is an instant reward, a rule that gives this reward to the members who perform the incentivized action, and a capping for quantity of rewards redeemed set to be renewed every month (calendar period mode).

    When the member performs the action for the first time, they receive the reward, but on the second time, a FieloPLT.Events: execution of AfterInsert error happens (the transaction isn't generated).

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.


  • Fixed [FL-11543] - Rounding Issue with capping is allowing the member to receive more points above the limit

    Functionality affected: capping.

    Expected behavior: when the member reaches the cap limit, he should not receive any more currencies.

    Case: a promotion rule is rewarding a payout currency, using the Percentage Conversion Mode. In the same program, there is a cap which shouldn't allow the member to receive the currency above the limit of 5,000.

    However, the engine overlooks the cents in the currency and ends up with a wrong sum of the member's balance. As a result, the member receives more than the cap limit.

    Is there any new dependency or effect caused by this fix? no.

    Are there any new steps to use the affected functionality? no.

  •    

    2.114.29
  • [FL-11429] Fixed

    Case: in a program where there are more than 50 thousand members and a Global challenge, whenever a member performs the action being incentivized by that challenge, the system show the error Error: FieloPLT:Too many query rows: 50001.

  • [FL-11448] Fixed

    Case: a Global challenge with 3 missions and using the Multiple rewards, but granting no more than one of them at the end of the challenge rewarding scheme for a challenge reward. When the member meets the rewarding criteria and the challenge ends, the transaction to deliver the Points reward is not created.

  • [FL-11447] Fixed

    Case: a Global challenge with 2 missions and using the Based on performance metrics at the end of the challenge rewarding scheme for a challenge reward. When the member meets the rewarding criteria and the challenge ends, the transaction to deliver the Points reward is not created.

  • [FL-11444] Fixed

    Case: a Global challenge with 1 mission and using the Based on performance rankings at the end of the challenge rewarding scheme for a challenge reward. When the member meets the rewarding criteria and the challenge ends, the transaction to deliver the Points reward is not created.

  • [FL-11441] Fixed

    Case: a mission using the Cumulative rewarding based on performance rewarding scheme should allow the member to place a limit on how much of a certain currency it will deliver. However, when rewarding a currency that generates payout, the limit was working only when using the Percentage Conversion Mode.

  • [FL-11440] Fixed

    Case: a mission using the Cumulative rewarding based on performance rewarding scheme should allow the member to place a limit on how much of a certain currency it will deliver. However, when rewarding a currency that does not generate payout, the limit is being disregarded: the member receives the full amount.

  • [FL-11425] Fixed

    Case: when using the Just one reward, one or more times rewarding scheme in a challenge reward, the challenge should deliver the reward every time that the member performs the incentivized action. However, the member is receiving the reward only once even when performing the action several times.

  • [FL-11445] Fixed

    Case: when creating a condition within the platform (for levels, segments, rules or missions) the creation/edition form is not loading results for the lookup field when the user tries to use it in a condition.

    For example, Member > Member Level > Level equals Bronze.

  • [FL-11443] Fixed

    Case: when using the Historical Data operator (available for missions based on a fixed metric) and setting it up for 1 day only, the mission does not consider the existing records. Therefore, the member does not receive any reward even if they achieve the mission goal.

  • 2.114.28
  • [FL-11387] Fixed

    The Mission Rewarding page is not loading the Conversion Mode and Conversion Value fields after the Salesforce Winter '22 upgrade.

  • [FL-11407] Fixed

    Case: in a program with 5 levels, where we deactivate two of them, we run the Assign Levels to Members batch so that the members' levels should be recalculated and they should be assigned to active levels. However, members are still assigned to the inactive levels after running the batch.

  • [FL-11410 & FL-11404] Fixed

    Case: a scheduled promotion is being processed and giving the related reward to the members who perform the incentivized action. Instead, the promotion should only be processed when the start date is reached.

  • [FL-11390] Fixed

    Case: when a redemption item is created, its item code (which is a randomic and should be an unique value) is being returned duplicated.

  • [FL-11419] Fixed

    Case: using the Incentives Lightning Component, the member tris to enroll in an opt-in challenge. After they click on the "enroll" button, the platform confirms that they were subscribed. However, the spinner keeps going on, the page doesn't reload, and in the backend, we can see that the member was not enrolled.

  • [FL-11415] Fixed

    Case: in an Org with 2 programs, the FieloPLT.SegmentService.applySegment method is processing and trying to apply an inactive segment from "Program A" to a member in "Program B".

  • 2.114.26
  • [FL-11370] Fixed

    Case: in a program, there is one Global Challenge and one Opt-in Challenge incentivizing the same action.

    The member is automatically subscribed to an Opt-in Challenge whenever they perform the Action being incentivized. By default, they should enroll in an Opt-in Challenge manually.

  • [FL-11346] Fixed

    Case: in a program, there is a Challenge targeted to a dynamic segment and a "Member A" who is part of this segment. The rewarding that the members will receive for accomplishing it is a Challenge Reward.

    When we try to create multiple events, related to Member A, which meets the Mission's criteria, the error FieloPLT.Events: execution of AfterInsert appears. Instead, the event should be created and the reward delivered.

  • Improved

    We enforced Fielo engines to run with administrator privileges. This addresses several permission issues that existed within the platform, since Fielo processing used to validate all the permissions required to use the platform. Now, it prioritizes updating and recalculates records.

  • 2.114.25
  • [FL-11330] Fixed

    Case: all program members were incorrectly assigned to all the active segments existent in the org. This means that the members were able to complete multiple incentives that they should not be able to, because they were not targeted to their segments.

  • 2.114.24
  • [FL-11255] Fixed

    Error "Illegal assignment from String to Date" happens when trying to self register using the Registration Lightning Component and there is a custom Date type field on the registration form, such as "dateofbirth".

  • 2.114.23
  • [FL-11173] Fixed

    Case: global challenge using Historical Data as the mission's objective. When we submit a file with 6k events that match the criteria to receive the mission reward, an error is received.


  • [FL-11214] Fixed

    Case: after we add a way to process mission reward based on a dynamic field when using the Cumulative rewarding based on performance rewarding scheme, an error is displayed when simulating some events with the Simulation API.


  • [FL-11011] Re-evaluated

    Previously corrected for package 2.114.22, it was reopened and correction was added to 2.114.23 version.

  • 2.114.22
  • [FL-11073] Fixed

    Performance issue. In a scenario with a global challenge with a mission based on historical data, the batch that processes the offline trackers is taking too long to complete processing.

    Time to complete the processing of 5k billings = 04hs and 16min.


  • [FL-11150] Fixed

    Unable to edit a mission rewarding.


  • [FL-11091] Fixed

    Case: a mission is using a dynamic field in the aggregation (sum) and the cumulative rewarding scheme. When trying to create a record that meets the mission's criteria, an error shows up (Fielo Exception).

    In order for it to work, It is necessary to create new custom settings.


  • [FL-11011] Fixed

    Case: program with 2 levels. #1 using related list conditions. #2 using one simple condition. After running the batch to assign levels, the member who met the criteria for level #1 was assigned level #2. Going to the cache partition and forcing it to be cleared makes the batch process work properly.

  • 2.114.21
  • [FL-11059] Fixed

    Case: org with Digital Experiences enabled and an active Site had a registration page using the Registration Lightning Component. When a new member tried to register, an error was displayed and the member was not able to register.

    Other than the fix, there are new required permissions for the guest profile.
  • 2.114.19
  • [FL-9074] Re-evaluated

    Previously corrected for package 2.114.13, it was reopened and correction was added to 2.114.19 version.

  • 2.114.13

  • [FL-10830] Fixed

    Case: in an org that has 1 segment for individual members, a promotion and challenge rewarding a currency that generates payout and with Enable More Accurate Maximization = true, the Simulation (partner incentive planner) returns this error: "Argument cannot be null".

  • [FL-10828] Fixed

    Case: an error is displayed when a new member tries to register through the front-end, using the Register Lightning Component. It was concluded that the issue was related to some missing permissions that the Guest Profile and Community (Site) Profile should have.

    The related documentation was updated accordingly.

  • [FL-10824] Fixed

    Case: when trying to create a page in B2B commerce to call Fielo incentive page, an error occurs. It was identified that the error is due to the Member ID not being passed in the method parameter getIncentives.

  • [FL-10822] Fixed

    Case: a promotion rule that has "amount must be greater than 10,000" as the criteria and the reward is based on a percentage of a numerical field.

    Considering that the amount is greater than 10,000, the Simulation presents an error where, when it calculates the amount or potentialAmount, the values considers the percentage on goal value (10,000) instead of the current value.

  • [FL-10821] Fixed

    Performance issue.,

    Case: Mission Based on a fixed metric, incentivizing Event creation and with the aggregate setup of sum up historical data. Every time that the mission member is updated, a batch starts and when we have simultaneous requests it achieves the limit and shows an error.

  • [FL-9074] Improved

    Case: it was not possible to import a program, when the original one used a currency that generates payout.

  • 2.114.11

  • [FL-10776] Fixed

    Case: error appears when trying to save a record that would reward an Organizational Member with payout. In this case, the mission's goal was to sum the amount on Opportunity Greater or Equal DYNAMIC (where dynamic is a custom field on Member, called GOAL).

  • [FL-10772] Fixed

    Case: when using the Challenges Lightning Component for Experience Cloud, the member is not able to subscribe himself into an Opt-in challenge. The error shown says that the member trying to enroll is not the logged in member.

  • [FL-10780] Fixed

    Case: when configuring the segment criteria for a multi picklist value, the screen is showing all the operators when we should display only equal or does not equal.

  • [FL-10727] Fixed

    Case: when we configure more than one rule rewarding funds, where one is not incrementing the budget value and the other increments the value, only one reward is being given.

  • 2.114.7

  • [FL-10719] Fixed

    Case: the Membership model was built in a way that a "manager" (individual member) has its user associated to the organization member, and use the member selector lightning component to switch from its individual user to the organizations member in order to redeem points. However, with the previous package, the manager could not access the organization member.

  • [FL-10720] Fixed

    Case: in a Program, there are 3 Rules that give different rewarding depending on the Event type. However, whenever an Event is created (no matter which type), the member receives the rewarding from all 3 Rules. The problem only happen when you don't have cache allocated to the org or if you clear cache with incentives active.

  • [FL-10721] Fixed

    Case: Challenge with 2 Missions that give different rewarding depending on the Event type. When I try to create an Event of a Type for a member, the transaction created is rewarding the member with missions not applied for him.

  • 2.114.6

  • [FL-10638] Fixed

    When there are more than 10 Actions in the library, none of them are displayed in the Actions list on the platform. This case was discovered when building the condition/query to retrieve the actions list: it concatenates in a way the query ends up malformed.

  • [FL-10635] Fixed

    Case: there is a promotion incentivizing the Login event, which in turn generates another event record which applies to a Global challenge. However, the member does not join the challenge automatically.

    This issue only happens when the challenge has a segment. Without segment, it works.

  • [FL-10629] Fixed

    Error when activating behavior for objects Price Book Entry, Service Territory Location and Service Territory Member. The error showed by Fielo is: "Record rolled back because not all records were valid and the request was using AllOrNone header".

  • [FL-10586] Fixed

    Once a Mission Rewarding is saved, it should redirect to the Challenge landing page where the Mission was created. Instead, it was redirecting to the Mission detail page where the Mission Reward was created.

  • [FL-10555] Fixed

    Case: when a Promotion is set up with a Rule that gives an instant reward from a registration event, an error occurs when using the Registration Lightning Component in the Experience Cloud Site (creating user and member).

  • [FL-10499] Fixed

    Case: when we have a Global Challenge and a Mission with objective using the Different Rewards Based on Member's Level rewarding scheme rewarding funds, the screen shows the reward label as "undefined" instead of "Funds" with the amount that was configured (in the Mission rewarding setup form).

  • 2.114.4

  • [FL-10562] Fixed

    Rewards Catalog component: whenever trying to click on the reward's description an error shows up. An error also shows up when trying to use the filter (sort by or description filters).

  • [FL-10572] Fixed

    Join Program component: when trying to use this component to join a program, the member receives an error and is not able to join. In this case, the member is part of a dynamic segment and belongs to a team.

  • [FL-10581] Fixed

    It was not possible to edit a member (through their record page) when accessing with an user that does not have create permission for the Member object.This was fixed so that Users that do not have create permission are able to edit members.

  • [FL-10582] Fixed

    After doing an upgrade Fielo version, Funds Allocation Rewarding was not activated. Even when receiving a success message, it was not really activated.

  • 2.113.3

  • [FL-10552] Fixed

    There are two cases where the issue fixed happened, related to courses that are segmented:
    1) Course Modules and Segments created on the same latest version. In this case there is no error, but the course is not showing up on the front end.
    2) Course Modules and Segments are NOT created on the same latest version (segment was from a previous version). In this case, the course is appearing on the front end, but when you press the button "take the course now" after completing the course, it comes back to the home page.

  • 2.113

  • [FL-10289] Fixed

    The fields that were available to be used as filter within the Translations (Languages) page is not showing up anymore. With the fix, they are available again.

  • [FL-10385] Improved

    Some issues in different Lightning Components were fixed with this package.

    1. My Profile - the information displayed in the Transactions tab goes over the the box's limit.
    2. Challenges/Program Promotions/Incentives - don't display the images.
    3. Filters for Challenges/Program Promotions/Incentives/Badges - filters not displayed properly (e.g. the "to" is not showing up).
    4. Program Promotions - "view promotion" and description text ovelapping.
    5. Incentives - the component doesn't show up immediately after trying to access it from another page. Only after the page is reloaded.
    6. Badges - component is not rendering properly, the user needs to scroll down the page in order to see the badges.
    7. My Transactions - the table goes over the card limit and screen width.
    8. Incentives/Challenges - not possible to see the leaderboard in mobile. In desktop, user sees only frame and fields with values: without colors and without the position highlighted.
    9. Description are displayed with html characters.

  • [FL-10453] Improved

    FieloPLT Promotion & Challenge Lightning Components were updated in order to comply with AODA (Accessibility for Ontarians with Disabilities Act) Compliant. This act states a set of requirements which must be met to be legally compliant.

  • [FL-10497] Fixed

    Segment not being assigned as expected. It is happening when the segment with multiple criteria has a custom logic condition ("the following expression is met" option).

  • [FL-10503] Fixed

    Whenever user accesses a rewards and tried to upload a image that will represent it, the image is actually not saved. With the new package, images are saved and displayed as expected.

  • [FL-10502] Fixed

    Whenever user accesses a program and tried to upload a image that will represent it, the image is actually not saved. With the new package, images are saved and displayed as expected.

  • [FL-10504] Fixed

    Case: program with a promotion and challenge, both are configured to reward Points and Funds Allocation (20 Points + $10.00 Funds). When the user tries to use the Simulation/Maximization API considering those incentives, the system doesn't process, throwing an error instead.

    Note that the Simulation API works only with currencies, but it should consider and work with the Points being rewarded by the incentives even if Funds are also a reward.

  • [FL-10510] Fixed

    Case: the processing of challenge fails when a member generates an action that subscribes them to 5 global challenges (and that should grant them with a reward) with the same action.

  • 2.110

    First Spring '21 version.

    ELR Package Versions x Issues Fixed

    1.77.13
    Install

  • Fixed [FL-13065] - Button to access an inactive Module is displayed while taking a course

    Functionality affected: Learning LC

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.12
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12996] - Content types making use of external URLs with HTTPS are not showing the content

    Functionality affected: Module Content

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.11
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12967] - Inactive courses being shown as Active

    Functionality affected: Courses

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.10
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Re-evaluated [FL-12629] - Module content is not displaying properly on the Module Response View page

    Functionality affected: Module Content

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.9
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12629] - Module content is not displaying properly on the Module Response View page

    Functionality affected: Module Content

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.8
    Install
    (Note: A newer version is available. We recommend using the newest version of Fielo in production environments.)

  • Fixed [FL-12461] - When cloning a course, an inactive form is displayed instead of the new activated one

    Functionality affected: Clone

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • Fixed [FL-12470] - Carousel images are broken in desktop

    Functionality affected: Module Content

    Is there any new dependency or effect caused by this fix? No.

    Are there any upgrade steps required? No.


  • 1.77.7
  • Fixed [FL-12223] - Custom labels for Subscribe button in PLT and Module # in ELR are missing

    Functionality affected:Fielo Communities Lightning Components

  •   1.77.6  

  • [FL-11997] Fixed

        Case: the Completed On date field was displayed only in American English format, regardless of user's locale.

    The format of the date displayed now corresponds to the language and locale of the user.
  •      

      1.77.4  

  • [FL-11907] Fixed

        Case: in a program, which has a portal built on Salesforce's Experience Cloud, the admin needs to translate the Fielo lightning component labels. However, some labels cannot be found.

    This is a list of the labels and their respective lightning component: Courses (Courses LC), SelectAnOption (Courses LC).
  •        

  • [FL-11847] Fixed

        Case: in an Org that has a portal built on Salesforce's Experience Cloud Sites, the program has a challenge incentivizing the course's completion. The admin uses the Course lightning component for the member to access the available courses on the programs that they are participating in. However, the component is not displaying the number of Points that the member has earned through the course.
  •      

  • [FL-11865] Fixed

        Case: program members are unable to join a course using the Course Lightning Component for Sites. The button appears as disabled when the component uses pagination.
  •          

  • [FL-11851] Fixed

        Case: in an Org that has a portal built on Salesforce's Experience Cloud Sites, it uses the Courses lightning component to display the available courses that the member can participate in and that he is already participating in. However, the courses tile's frames were almost overlapping each other and the navigation buttons (next and previous) were also almost overlapping with the courses tiles. The new package fixes those UI points.
  •  
            

  • [FL-11927] Fixed

    The Custom Label label daysLeft, used in the Course lightning component to display the number of days until the Course's end date, had its value changed. Previously, it was "[number] left days"; but with the new package, the value is now "{0} days left".

    This allows the user who needs to transalate this label to change the order in which the number is displayed, making it comply with the Language sentence structure grammar rules. For example, 4 days left or days 4 left ( {0} days left or days {0} left ).
  •  

    1.77.1

  • [FL-11699] Fixed

    Case: when the members submited an answer to a module, the Module Responses were being displayed with the previous day's date instead of today's date in the Course page. The data was correct in the database.

    With the fix, the system will store the date associated to the User.

  • 1.77

  • [FL-11501] Fixed

    Case: in an Org, there is a custom picklist field in the Courses object and the Courses Lightning Component uses only this field as a filter (in the Course Filter Fields settings option). The portal user is not able to use the filter properly: if they select one of the picklist's options, the courses are not filtered.

    Note: adding the Status filter back with the custom picklist field seems to work properly, but only when the status is part of the filtering.

  • [FL-11634] Fixed

    Case: when a Course ends on the current day (i.e. today), the member is not able to participate in it, but they should be.

    Regarding the message that the member sees in the Courses Lightning Component, which informs how many days there are until the end of the course, it should be "0 days left" when the course ends today. Before the fix, the message said "1 days left".

  • [FA-689] Fixed

    Case: the admin is able to deactivate and delete a segment that is assigned to a Scheduled or Active Course. After the fix, the system won't allow the segment's deactivation and deletion in this scenario.

  • 1.76.4

  • [FL-11547] Fixed

    When the user creates a course with start set to the current day (i.e. today) and clicks on "Activate", the course status changes from Draft to Scheduled, instead of Active.

    Note: if the user has a PC timezone different than the org timezone an issue can occur. We suggest using the same timezone both on your device and in your Salesforce settings.