Skip to content

Global Config Settings

Johannes Fischer edited this page Dec 16, 2024 · 7 revisions

rflib_Global_Settings is a Custom Metadata object with configuration settings that are not allowed to be overwritten by Profile or Users. These settings are Global to the org. Please note that if you are overwriting those settings, those values may be reset when installing a new version of RFLIB. Hence, it is recommended to make it a manual task to validate the Custom Metadata records upon package installations.

Setting API Name What is it for? Default Value Valid Values Since Version
Application Event Retain X Days Application_Event_Retain_X_Days Used by the Application Event Log Archiver to determine which Application Events need to be moved to the Big Object archive. Events older than the days configured in this setting will be copied over to the Big Object and deleted from the Custom Object. 45 Any number larger than 1 5.0
Archive Log Query Limit Archive_Log_Query_Limit Used by the Application Event Log Archiver to determine how many records should be retrieved in a single search request. This helps to avoid Governor Limit exceptions such as heap issues. 50000 1-50000 6.1
Permissions Explorer REST API Enabled Permissions_Explorer_REST_API_Enabled Used by the Permission Explorer to determine whether to use the REST API connector or the standard queries. Standard queries have a limit of returning only 50,000 records. Use this setting to retrieve more than 50,000 permission records. Please see the associated Wiki page for more details. FALSE TRUE, FALSE 2.6
Publish Platform Event Transaction Limit Publish_Platform_Event_Transaction_Limit Used to limit RFLIB's usage of Platform Events. This setting limits the number of Application and Log Events that can be published per transaction to ensure that an org's business logic has enough events available for all of its features, preventing Governor Limit exceptions. 150 1-150 4.0
Trace ID Header Name Trace_ID_Header_Name Name of the HTTP request header that will contain the RFLIB Trace ID value when making outbound HTTP calls out of Apex using the rflib_HttpRequest class. All requests will contain this header name and value and can use the Trace ID to track log statements back to the original Apex transaction and corresponding RFLIB Log Events. X-Trace-ID Any string representing a valid HTTP header name with less than 255 characters. 1.0
Trace ID Value Format Trace_ID_Value_Format Format of the Trace ID value. The Trace ID will either be the Salesforce Request ID or a concatenation of the current user's record ID in either 15 or 18 character plus the Salesforce Request ID. USER18_REQUEST_ID USER15_REQUEST_ID, USER18_REQUEST_ID, REQUEST_ID 7.1
Use Default Workflow User for Log Events Use_Default_Workflow_User_for_Log_Events Salesforce's Spring 24 release introduced a new setting for record triggered Flows to set a Default Workflow User to execute the Flow, which specifically applies to Platform Events. When there is a Default Flow User set and this setting is TRUE, email notifications do not require an Org-Wide Email Address to be configured. FALSE TRUE, FALSE 6.3
HTTP Request Mocking Enabled Http_Mocking_Enabled Enables or disables HTTP request mocking globally. When enabled, HTTP requests can be intercepted and mocked according to predefined mock endpoints, allowing for testing without actual HTTP callouts. FALSE TRUE, FALSE 6.6
Allow HTTP Mocking in Production Http_Mocking_Allow_In_Production Allows HTTP request mocking to be used within production environments. This setting is considered only if HTTP request mocking is enabled. FALSE TRUE, FALSE 6.6
Throw Error If Mock Is Not Found Http_Mocking_Throw_Error_If_Mock_Not_Found Determines whether to throw an exception when no mock configuration matches the current, outgoing HTTP request. If set to FALSE, the standard Apex HttpRequest object is used and an actual callout will be made. FALSE TRUE, FALSE 6.6
Development Mode Enabled RFLIB_Development_Mode_Enabled Controls the behavior of the rflib_LoggerUtil.logInternal() methods. When enabled, logs are written at the INFO level; otherwise, they use the DEBUG level. This setting should only be set to TRUE when developing new components for RFLIB's Ops Center or when debugging UI issues in RFLIB. FALSE TRUE, FALSE 8.0
Clone this wiki locally