Fielo Platform Limits

Fielo offers a plethora of features that you can use to make a great incentive or loyalty program. Some of these have important limits that you must be aware of.

Rules Engine Batch Size

If your implementation calls the Process Records method as part of custom logic, be sure to do so in chunks of no more than 200 records at a time. We cannot guarantee against CPU timeouts beyond that batch size.

Related List Criteria

When using criteria that count records or sum up a value from records of a related list, Fielo can process a maximum of 200 records per criterion, by default. This is to protect your org from exceeding Salesforce's 50,000-row query limit.

You can change this value by navigating to Public Settings (FieloPLT namespace) in the Custom Settings area of Salesforce Setup. The setting is called Related List Limit. However, be aware that increasing the limit may result in your org exceeding Salesforce's 50,000-row query limit, in which case an uncatchable error will be thrown.

(Note: When using Levels, if Levels Settings are enabled, this limit does not apply.)

Incentive Criteria

It is not possible to activate incentives that contain more than 33 criteria and use custom logical expressions. If you need more than 33 conditions, consider splitting those conditions into more than one promotion.

For example, consider that you have a rule with 20 conditions and another with 15 conditions. Instead of grouping these two rules in one promotion, create two promotions with one rule each.

Note that this limitation is related to the JSON that is generated from the rule and mission criteria and stored on the incentive (Promotion or Challenge) record, so the number mentioned above is a conservative estimate that assumes you are using custom logical expressions.

Criteria Across Your Org

Fielo supports up to 10,000 criteria per org. This limit applies to criteria in your rules, missions, segments and levels across all of your programs.

Bulk Loading with Challenge Reward Limit

When using Limit to limit the number of times a Challenge Reward can be given to a member, Fielo considers a limit to be used up when the Challenge is accomplished and the member is rewarded. If many records are loaded in bulk and are processed at the same time, the Challenge will be accomplished once, even if those records were sufficient to accomplish the Challenge multiple times.

Concurrency with Order of Completion Leaderboards

For Missions with leaderboards that position members based on order of completion, Fielo is unable to support concurrency. This could happen with large (10,000+ member) challenges and in integrations or bulk loading that use multi-threading.

Dynamic Segmentation

Each program allows up to 50,000 active dynamic segments. It's important to note that this limitation includes global segments, which are not tied to a specific program.

Criteria Date/Time

Dynamic segments, rules, missions, and levels can have criteria that use fields of type Date/Time. However, when evaluating those criteria, Fielo discards the time and evaluates criteria using the date at 12am GMT. So, Fielo criteria cannot evaluate Date/Time fields at the precision of hours or minutes (just days).

Criteria Combinations

A dynamic segment, rule, mission, or level criteria - which the member must meet to be part of them or to receive a reward -, can have several conditions and/or related list conditions. Following the definition of the conditions, and whenever you add more than one, the next step would be to specify how they will be evaluated as a whole.

You can decide if the member must meet ALL conditions, ANY, or a custom expression such as ((1 AND 2) OR 3). If you choose to write an expression, note that it cannot surpass 255 characters.

Multi-picklist

Multi-picklist fields cannot be used in criteria (rule, mission, level, segment) or in configuration forms that can be extended.

Moreover, you cannot use this field type in Fielo's components for Experience Cloud Sites.

No More Than 24 Non-Payout Currencies

Fielo Incentives supports up to 24 non-payout currencies.

Auto-Linking Individual Members to Organization Members

When creating an Organization Member, Fielo will attempt to link it to the Individual Members that are registered to the same Account, but will only query up to 200 Individual Members to do so.

Negative Accruals

By default, the rules engine does not support "awarding" of negative values. If your use case requires this, contact us.

Negative Balances

By default, Fielo Incentives does not support negative currency balances. If your use case requires this, contact us.

Import/Export Tool

The Import/Export tool is subject to a CPU time limit of 60,000 milliseconds and a SOQL query limit of 200 rows (both are Salesforce governor limits). The tool also does not migrate simulation settings at this time.

Quickstart Incentive Wizard

The simplified incentive wizard on the Home tab has the following limitations with respect to the advanced wizard on the Incentives tab:

• No related list criteria
• Access only to fields on behavior object
• Behavior object must have only one lookup to Member
• Only Challenges with fixed goal that reward upon reaching that goal

Redemption Code

In a case where a program has a great number of members and generates more than 20 transactions per second, we suggest you configure the program's redemption code to be generated with a high number of digits: 7 digits or more, depending on the number of members. This makes it less possible for any code to get duplicated due to the heavy concurrency of codes being created.

To define the number of digits, go to the Programs tab, access your program, and go to Settings. The field you must complete is the Number of Code Digits.

Learning

If you use the Learning app, you might face some limitations regarding the number of characters that you can use in some of the fields. Check below which are the fields and their respective limitations.

Course Modules

• Module Name: 80 character limit.
• Description: 255 character limit.
• Content field: 255 character limit. There is also a 6 images limit if you are using the Carousel option.

Questions

• Answer Option Text: 255 character limit.
• Matching Text: 255 character limit.

File size & storage limits
Any file that you upload to your Module (images, videos, PDF) will follow Salesforce's upload limits and will count in your Org storage usage.

If the files are externally stored, you'll need to check with your external provider for more information on their storage limits.

RevOps with Enterprise Territory Management Enabled

Fielo RevOps supports up to 1,000 active territories (when using with Enterprise Territory Management).

Invoicing

When you create a new Invoice, one of the available fields for you to complete is the description. Note that this field has a maximum limit of 255 characters.

Images

The allowed formats for photos and pictures are jpeg, jpg, png, gif, webp, SVG, and tif.

Other than that, any file (images, videos, PDF) that you upload to be used by any Fielo feature will follow Salesforce's upload limits. Note that, if the files are externally stored, you'll need to check with your external provider for more information on their storage limits.

For community components:

• My Learning: we suggest you upload images with the proportion of 600 x 360 pixels (width x height).
• Join Program: we suggest you upload images with 200 pixels as the height and with width up to 800 pixels.
• Program Promotions: we suggest you upload images with 200 pixels as the height and with width up to 800 pixels.
• Challenges: we suggest you upload images with 200 pixels as the height and with a width up to 800 pixels.
• Incentives: for this component, we suggest you use the proportion of 700 x 300 pixels (width x height).
• Catalog: this component will adapt to any image proportion.
• Profile: we suggest using an image with 1:1 proportion (e.g. 600 x 600 pixels).
• Badges: we suggest using an image with 1:1 proportion (e.g. 600 x 600 pixels).

Currency Accumulation Processing

Whenever records belonging to the same member - and that should deliver currencies to them - are created through more than one system, Fielo might not update the member's balance as expected. This happens due to the concurrency of more than one integration process trying to complete the same task at the same time.

For example, imagine that in a program there is a Rule that delivers points to the members who close opportunities. When a member logged in to the portal through mobile and desktop closes opportunities from these two systems, the member's balance might not get updated with all the points that they should receive from all the opportunities that they closed.

There are some ways to mitigate the possibility of this scenario happening:

• Send the records sorted by Member ID
  If you sort all the records being delivered by the Member ID, you would almost entirely eliminate the probability of records created by the same member falling into different threads of the integration process. If the records don't fall into different threads, there isn't any risk of the member's balance not being updated.

• Process the integration records offline
  Create a Custom Setting related to the integration user to define that the records created by the integration are processed offline. After that, set up the offline batch processing to automatically run in the frequency that makes the most sense to you (e.g. every 6 hours) or at a specific time.
  This will reduce the "concurrency window" of more than one online process trying to update the member's balance.

• Develop a detection process
  Once you complete the steps above, there could be a small number of cases where the member's balance is not updated as expected still. For that, we suggest you develop a small process to detect those issues (if they happen) and if so, to adjust the balance of the member affected.

Supported Browsers and Devices

Find below an overview of the browsers and devices supported by Fielo.

• Browsers
  • Fielo recommends using Google Chrome or Apple Safari.
• Mobile
  • Fielo Lightning Components are tested using the iPhone X (375x812 / 5.65in) screen size as the baseline for mobile phones and tablets. Other devices and sizes might experience compatibility issues.