Spring '20 Technical Release Notes & Changelog (v2.92 to v2.96.21)
June 29th, 2020 by Eric Pinheiro
With Spring '20, platform now includes the following changes:
- All Teams created before the upgrade have the field Team Type set to Individual automatically.
- All Programs created before the upgrade will have the Cap adjustment transactions field set to enabled automatically.
- All Caps created before the upgrade will have both the Cap Mode field set to Hard and the Cap by period or by record? field set to By Period automatically.
- Two Lookup relationships have been added to the Agreement object, and now it shares data with Challenges and Promotions. This is to allow for specific incentive-level agreements.
- The object Audit Cap has been deprecated. A new Lookup relationship between Points and Cap has been created, and now Points fetches the Currency and the Point Accrual information directly from Caps.
Changelog
- Added: Budget Management [FL-8067]
- Added: Soft Cap [FL-7954]
- Added: Cap by record [FL-7961]
- Added: Capping for CIPM [FL-7877]
- Added: Incentives lightning component [FL-7904]
- Added: Agreement for challenges and promotions [FL-7728] [FL-7977]
- Added: Eligibility for program promotions, challenges and incentives lightning components [FL-8051] [FL-8264]
- Added: Permission Set for Member Community [FL-8305]
- Improved: Report tracking for Cap [FL-8187]
- Improved: Add Organization Members to a team [FL-7986]
- Improved: Choose whether to cap adjustment transactions or not [FL-7960]
- Improved: Audit Cap for Caps on Redemptions deprecated [FL-8191]
- Improved: Validation rule for using external image URL in challenges, promotions and reward
- Improved: Enable Related List Conditions in Levels [FL-7874]
- Improved: Save as Model/Export Program should consider Agreements for Program and agreements for incentives [FL-8152]
- Improved: Points record shows the original amount, amount with capping applied, and final amount [FL-8030]
- Improved: Creating Dynamic target goals configuration [FL-7731]
- Improved: Edit Mission Reward Redesigned [FL-8346]
Package Versions x Issues Fixed
2.96.21
Install
(Previously corrected for package 2.96.19, it was reopened and additional flexibility was added to 2.96.21.)
Functionality affected: Points Expiration
Is there any new dependency or effect caused by this fix?
New flexibilities have been added to the
PointsPartialExpirationBatchSchedule:
- FieloPLT__PointExpirationBatchSize__c (Integer): to control how many (Member) records are processed at each run. (Default: 200)
- FieloPLT__PointExpirationFromDate__c (Date): to execute the query from this date and build a range of expiration date from here. (Default: null)
- FieloPLT__PointExpirationMaxRange__c (Integer): to control how many dates will be ranged for each chunk of batch. (Default: 200)
PointsPartialExpirationBatchSchedule.
2.96.20
Install
Functionality affected: APIs (getMemberSegment)
Is there any new dependency or effect caused by this fix? No.
Are there any new steps to use the affected functionality? Run this command in the Developer Console:
update [SELECT Id FROM FieloPLT__Segment__c WHERE FieloPLT__IsActive__c = true AND RecordType.DeveloperName = 'Dynamic'];2.96.19
Previously corrected for package 2.96.18, it was reopened and correction was added to 2.96.19 version.
2.96.18
Previously corrected for package 2.96.17, it was reopened and correction was added to 2.96.18 version.
2.96.17
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.96.16
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.
Functionality affected: Points expiration.
Expected behavior: the Points expiration date should be displayed within the Debits & Credits tab (in the Member's page) as it was defined.
Case: in a program, the administrator creates an adjustment transaction for the member, in order to give them 50 Points. The admin defines that these Points will expire on December, 25th. However, if you enter the Debits & Credits tab (in the Member's page), the Points record there shows that these Points will expire on December 24th.
Is there any new dependency or effect caused by this fix? no.
Are there any new steps to use the affected functionality? no.
2.96.15
Previously corrected for package 2.96.14, it was reopened and the correction was added to the 2.96.15 version.
2.96.14
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.
2.96.13
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.
2.96.12
Functionality affected: Redemption.
Expected behavior: Whenever the user needs to create a new redemption for the member, or the member creates a new redemption, the redemption record is created.
Case: In a program that has a reward called "Product Bundle" and an existing redemption for this reward related to a member after that, the admin decides to revert this redemption. However, when they try to create a new "Product Bundle" redemption related to the same member, they receive the FieloPLT.RedemptionItems: execution of BeforeInsert error. The new redemption is 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.
2.96.11
Functionality affected: redemption.
Expected behavior: when Fielo has to process many redemptions for the same member at the time time, Fielo should ensure the update of the member balance properly. Then, just one redemption will be processed at a time and the others will fail.
Case: the case is considered an integration issue related to redemption concurrency for the same member.
A member who has a previous balance of 100 Points, performs 20 redemptions (each costing 90 Points) at the same time. As Fielo processes all the redemptions in parallel, it considers the original member's balance for all the redemptions, delivering all 20 redemptions instead of only 1.
Is there any new dependency or effect caused by this fix? yes, for the users who consume Fielo's APIs. With the fix, Fielo will lock the member record to ensure the proper update of their balance when processing several redemptions, processing one redemption at a time. In this process, if there is a parallel request to process several redemptions for the same member at the same time, the system will grant exclusive access to the first request to retrieve the member records. From then, there are 3 possibilities:
- If any of the subsequent requests have to wait more than 10 seconds to obtain exclusive access to the member record it will throw an error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record [or N records]. In this scenario, the member would have to do the redemption again.
- If all the subsequent requests have the time to be processed, the system will then process all Fielo validations (e.g. member has sufficient balance, a reward has sufficient stock, and so on). If any validation fails, an error will be thrown: insufficient stock, insufficient points, and so on.
- If the system is able to place all the redemptions, no error will be thrown and the member's balance will be decreased accordingly.
2.96.10
In an Org with more than one program, it was not possible for a User (other than the System Administrator) to create incentives for more than one program. To be able to do this, the User needed to have the permission to edit the Custom Settings related to that feature. In that regard, the 2.96.10 version no longer checks if the User has the Custom Settings permission to work with other programs.
2.96.9
When choosing some specific rewarding schemes (e.g. based on performance metrics) for Missions, the rewarding page does not load the Conversion Mode and Conversion Value fields for currency rewards.
2.96.8
When accessing a Rule for any promotion and trying to enter a criterion using a Related List condition, it shows up as expected. However, when the attempt is made with an user with the "Salesforce Platform" licensing which has a custom Permission Set (based on the default FieloPLT Admin), the related list appears blank.
2.96.7
Sporadically, the error System.NullPointerException: Attempt to de-reference a null object is happening before updating a member.
2.96.6
Fielo package unhandled exception. In this case, Apex exception emails from Fielo package unhandled exception were being repeatedly sent. With the new package, the errors are not happening anymore.
2.96.5
It is not possible to properly configure a Behavior and Action that use an object with API name of Transaction__c. The Behavior creation wizard shows fields from the FieloPLT__Transaction__c object (not the correct object) and thus the Behavior cannot be deployed.
It is not possible to create a new Behavior for the object Account for Promotion, Challenge and Communication. Enable automatic deployment option. When trying to deploy the behavior, the deployment fails. The org in which this occurred has Person Account activated.
A research in our code discovered that in the SObjectService class, we have a query on the prefix (first 3 characters) of the objects ID's. In the issue's case, the Objects Event (a0h) and AFH_Promotion_Product__c (a0H) had almost the same Prefix, however as our SF query isn't case sensitive, it returned both Objects, instead of the one that was expected. This happens, because the SObjectService processEngine function search for Rules Triggers for the specified objects in ‘records’ parameter using the object prefix as query parameter.
This caused an error when trying to the object AFH_Promotion_Product__
2.96.4
Improved
Package launched due to Security Review adjustments required.
2.96.3
ELR v1.73.2 - which requires the ORG to have Spring '20 installed - is not able to be installed with PLT 2.96, 2.96.1 or 2.96.2 packages, giving the following error: "Your request to install package "FieloELR Fielo ELR 1.73.2" was unsuccessful. None of the data or setup information in your salesforce.com organization was affected."
This issue was fixed with PLT v2.96.3.
2.96.2
Case: the Program has 2 levels and 2 members, each in a different level. When a Challenge Mission is compare among members (without objective) and uses the rewarding scheme 'Different rewards based on member's level', one member receives the mission reward, but the other doesn't.
Case: the Program has a Program Currency with a partial expiration set. When editing an existing Rule or Challenge Rewarding and more than one reward was selected when it was created, the expiration value shown for all currencies that have partial expiration is not what was defined before. It is automatically showing the Program Currency default value, instead of the saved/stored value.
Challenge Lightning Component UX fixes:
- Default Status picklist field is 'Select an option'. Change to 'Active'.
- Mission leaderboard images showing as broken. Fix the images, so that it is possible to see the Members' pictures.
- Show leaderboard in Challenges Missions where Status = 'Ended'. For some reason Challenge Missions which contain a leaderboard and Status='Ended' don't show the leaderboard.
- Once user clicks on a challenge, there's no way to navigate back to the challenge list. Fix that, so that the Member doesn't need to reload the page in order to return to the challenge list.
Case: when you edit a Member, save the edition made and then edit again, the form shows the old value. For example, when you change the Member's email and, after a while, click on Edit again, the form shows the old email as if it wasn't changed.
2.96.1
Case: there is a Promotion rewarding an instant reward. After the member earns it, the user cannot revert the Redemption / Redemption Item. Error: System.DmlException
Case: the program agreement continues to be presented in the community every time that we go to another page, even after it has already been accepted by the member (and the acceptance has already been recorded on the backend). It just doesn't appear anymore if we refresh or close the page and then come back.
2.96
Case: there is a Promotion using the Generate an Event and Win action and rewarding an Instant Reward that is segmented (criteria Event > Type equals Login, Count greater or equal 1), the user creates 1 Event and 1 Login Event. When user tries to create a second Event for the Member, error System.SObjectException.
Case: Member has received a currency that generates payout through a Promotion that incentivizes the opportunities. When user tries to ban the Member, error FieloPLT.Members: execution of AfterUpdate caused by: System.DmlException: Insert failed.
2.95.13
Previously corrected for package 2.95.10, it was reopened and correction was added to 2.95.13 version.
2.95.12
Previously corrected for package 2.95, it was reopened and correction was added to 2.95.12 version.
After creating a team with some members and someone tries to edit it, its members are not displayed (so that they can be removed or reviewed). After the correction, the members are shown.
2.95.11
Not able to use a decimal number in the Missions aggregation's value field when using the Sum up the Aggregate Field option. After the correction, it is possible now.
When trying to create an Email Template, once type = Transaction is chosen, the page freezes. Once the system returns, the form is broken, leaving the user unable to choose any value for the Data class or Email Template fields. They appear empty. After the correction, the user can add value for those fields.
2.95.10
Member tries to create an Event record to join the Challenge, but an error says he's already part of it, when he's not. It is assumed this is a problem with every Challenge that checks more than one action from their missions and a record triggering more than one action.
WARNING
=> We strongly advise anyone to not incentivize Fielo objects because it may result in a processing loop that may easily hit a Salesforce governor limit. If a limit is hit because of this that we can no longer support you.
=> A way to avoid hitting a governor limit in situations like this is to use asynchronous calls to the processing engine like Future Methods, Platform Events or Change Data Capture.
=> But keep in mind that this is not an Official way to incentivize behaviors with Fielo Platform.
System does not allow navigation to Reward detail view, when page settings has been altered (custom rich text field type). After the correction, the detail view can be accessed.
Not able to create a behavior for objects from managed packages such as Cloudcraze, or any managed package that has objects with Namespace Prefix (e.g. ccrz_E_Order_c). The error displayed is: Field E_Order__c of object Point not created yet. Please try again later.
After the correction, it is possible to create the behavior.
2.95.9
New members are not able to register in community through Registration Lightning Component, when Program has at least one dynamic segment with the option Update in real time = true. After the correction, the Lightning Component is working as expected.
Community's logged members are being blocked from seeing Fielo Community components after ORGs were updated with Salesforce Winter '21 release. New manual configurations were added in DOCs, within Build an Experience Cloud Site section.
Previously corrected for package 2.95.6, it was reopened and correction was added to 2.95.9 version.
2.95.8
- When trying to save an email campaign and a Segment is assigned to the Promotion, an error is displayed and record cannot be saved. Error: FieloPLT.EmailCampaigns: execution of BeforeInsert caused by: System.NullPointerException: Argument cannot be null.
- When taking out the segment from the Promotion, it is possible to save, but not view the record saved (spinner icon keeps loading).
After the correction, the email campaign can be created without issues.
Not able to use Rule with an action based on a partner custom object. Error message is displayed when try to activate the Promotion: "Record cannot be 'Active'. At least one Rule Criterion includes an invalid 'Field Name' on Partner Fund Claim.". The rule condition uses a custom picklist "Incentive Type" field.
Previously corrected for package 2.95.6, it was reopened and correction was added to 2.95.8 version.
2.95.7
Previously corrected for package 2.95.6, it was reopened and correction was added to 2.95.7 version.
2.95.6
The necessary data is not being stored in the "Summary" field present in Mission Members pages. This is important for Mission processing. After the correction, the Summary field is populated.
Previously corrected for package 2.95.5, it was reopened and correction was added to 2.95.6 version.
Previously corrected for package 2.95.5, it was reopened and correction was added to 2.95.6 version.
2.95.5
Previously corrected for package 2.95.2, it was reopened and correction was added to 2.95.5 version.
Unable to create an Opportunity when it has a custom field ("Member") and you add a contact to this field when creating the Opportunity.
OBS: "The issue was related to ConditionType being empty. A new type was added also in the fix, so in order to test it, use a field in action with type Text, STRING and empty. Look at the fields available and use fields that were created in SF as Picklist and Text (Please, look in Object Manager to use proper fields that match with those types). For the empty case, please edit the action by force"
2.95.4
When having a behavior related to a custom object (Campaign) with one action, and using it for a Promotion Rule, the object specified in "use the same object or related list?" is randomly changed for a related list as the user tries to edit the Rule. And the system does not process it anymore.
When creating a new redemption, if the user selects a member but then changes their mind, deselect the member and selects another, the first member's currencies are still displayed in the side, instead of being replaced by the second member's currencies. They just keep being added if the user repeats the process.
Grammar mistake in the Help Text for a field in "Create Badge" form. Corrected with the fix.
Typo in Help Text for a field in the Email Template object. Corrected with the fix.
There was a typo in the Help Text for a field in the Challenge object. Corrected with the fix.
Member NAME, ITEMS and POINTS data aren't being displayed in the Redemption page header. After the corrections, they are now being displayed.
When creating a new Promotion Rule with type being Only when it awards the most points, in the Reward Type section it is not possible to deselect Points after selecting it. After the correction, it is now possible to deselect the Points option.
If the user edits a segment (more specifically the second level field in a related list condition) without changing the object, the options in the Operator picklist are kept the same (Equals, Does not equal, Contains and Does not contain). However, Quantity field type should display different options for the Operator picklist: Equals, Not equals, Greater than, Greater or equal, Less than, etc.
Incentive type section was showing up twice in the Save as Model form, for an Incentive. After the correction, is it now displayed only once.
2.95.3
It is impossible to Activate a Behavior related to a custom object in an ORG, due to an error related to the look up field automatic creation when first activating the Behavior (new to Spring '20 release). This happens when some fields already exists in the object the user is creating the Behavior for. They are Lookup Relationship type fields from the custom object to Member or from other objects to the custom object.
Budget Batch was impacting on Promotions Performance.
The fix of this issue was restrict the points' search created after the last time the batch ran. Changes to the DOCs can be seen here.
Records related to Rules not being processed.
The issue happened when the Rule gives a currency that generates payout and the Payout Date Mode was = 'Immediately after the action is performed', which triggers an approval process that the user had. If the payout doesn't have approval process, the system shows an "internal Salesforce error". This is related to the Salesforce Winter '21 release and was corrected.
2.95.2
When creating a segment that uses more then one related list condition, the user is unable to set an expression that has to be met. Error: "Match criteria" logical expression is invalid.
In the example, there were 6 conditions and the user tried to use this expression: (1 AND 2 AND 3 AND 4 AND 5 AND 6)
However, they should have used "all conditions are met" instead of custom or another logical expression such as ((((1 AND 2) AND 3) AND (4 OR 5)) AND 6). This was decided on being altered to an improvement in order to make the custom logical expression use more friendly.
Every time that the user tries to access the program view page, they receive an error and cannot enter it. The error was: No such column 'IsActive__c' on entity 'FieloPLT__KPI__c'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
After the fix, the user can enter the Program page.
The user is unable to create a Promotion Rule when he tries to use a percentage field type in the Rule's criteria. Such as: PIP MDF Pipeline Percentage greater or equal 45%.
2.95.1
When the user has a segment that he created leaving the active option unchecked, as he goes to edit the segment, the same option shows up checked. After the correction, the option remains unchecked.
When creating and editing a Reward, all the Program's segments are displayed. Even the inactive ones. After the fix, only the active ones are displayed as options to select.
When a segment has more than one condition and the process when is set to "Any condition is true", the segment isn't assigned to the member who has accomplished the condition. After the fix, the segment is assigned.
2.95
There is an error when clicking "New" on email campaign Promotion and Challenge related object. A message asking to contact Salesforce shows up.
This happens when enabling Partner Marketing Budget standard object in Salesforce and creating a custom field lookup to Partner Marketing Budget on Promotion or Challenge.
The program's name is not displayed in the new incentive form.
Previously corrected for package 2.94.1, it was reopened and correction was added to 2.95 version.
Unable to set an instant reward as the reward for a Promotion Rule. The reward find return empty. After the fix, the instant rewards available in the program show up.
2.94.1
Consider creating a new Level, Segment, Rule or Mission, where the condition uses a related object and the operator option is different from "Equals" or "Do not equal". For example, "Less than", "Contains", etc.
When editing it, the condition operator is displayed always as "Equals", when it should be the one selected before.
When a user has a Member and a Contact in their ORG and wants to related them with each other, they receive an error: id value of incorrect type. This was tested when the Contact and Member were already created and the user tries to edit the Member record in order to add the Contact.
It is not possible to add a user to a member, when creating or editing it. Steps: Target Audience tab > New Member > Try to add a user in the User field.
2.94
When trying to edit a segment which has a related list object criteria, the information regarding the condition was not displayed and the user was also not allowed to change the criteria.
This happens when using a custom object related to the Member object.
During the configuration of the action, in the section "MEMBERS TO INCENTIVIZE" there are some labels that need to be changed because it generates confusion about the configuration.
"What type of member?" needs to be replaced for "Who will receive the rewarding?". And replace "Individual Member" for "Same Member". Also, "Organization Member" for "Organization Member Related".
The changes done in the documentation regarding this can be seen here.
User added a lookup to the incentive layout to Partner Marketing Budget object, but the search field does not work and he can't relate it to a budget in Fielo Incentive Layout.
To test: there is no "Name" field on the Partner Marketing Budget. Should use the "Title" field.
Removing one related list condition from a segment (when editing it), ends up removing all other related list conditions.
Null pointer exception in challenges. Found when configuring a challenge, for multi program incentives, and when trying to set the member in the order (there are three actions in orders for different members of different programs), an error was displayed.
2.93
Not able to save segments when using related list condition, together with Salesforce standard objects. Example:
1 - Member -> Event -> Created By ID -> Active equals True
Count equals 1
Adding a condition related to Member Account in a segment causes any fields from Salesforce objects to not load. However, fields from Fielo objects do load. Changing criteria back to Salesforce keeps previous object fields and does not update.
2.92.6
First Spring '20 version.