Skip to main content
SalesWings Toolbox package custom settings

Technical documentation on SalesWings Toolbox package custom setting objects in Salesforce Setup.

Pauline from SalesWings avatar
Written by Pauline from SalesWings
Updated over a week ago

The following SalesWings Toolbox custom settings objects can be used to modify app behavior, and should only be performed by a Salesforce Admin after confirming the behavior with SalesWings technical support.
โ€‹

Name

Purpose

Visibility

Since

SWT Logger Options

It defines the level of logging that will be output (and also received by the backend)

Public

4.0

SWT Report Column Mapping

It defines custom report column name mappings

Public

1.27

SWT Settings

It defines the general options that influence the appplication behavior

Public

1.0

SWT Trigger Handler Routine

It defines which SalesWings triggers are allowed to run. This functionality is currently not in use.

Public

4.0

Below all the custom settings with respective description/function.

SWT Logger Options

It fine controls the amount of logging output by the managed package, as well as communicating it to the backend.

Multiple profiles can be defined to tweak the logging level of specific namespaces or classes.


The Fields

Name

Description

Default Value

Since

Appenders

The appender class names that will invoked when logging.

Multiple appenders, separated by a comma, can be specified.

4.0

Class Names

The classes that will be enabled for logging.

Multiple class names, separated by a comma, can be specified.

4.0

First Caller Override

This options will override any other logging profile defines as long as the first call to the logging framework was performed by a class belonging to the namespace specified, if any, or class names specified.

4.0

Is Disabled

It determines whether the logging profile will be evaluated by the logging framework

4.0

Namespaces

The namespaces that will be enabled for logging.

This is a quick way to enable logging for all the classes belonging to the same namespace.

Multiple namespaces, separated by a comma, can be specified.

4.0

Threshold

The threshold level that will be considered for logging.

The logging levels supported are the Salesforce ones.

4.0

Users

The users that will be considered by the logging framework. If specified only code executed by such users will trigger the logging.

Multiple users, separated by a comma, can be specified.

4.0

SWT Report Column Mapping

It defines custom report column name mappings.

The Fields

Name

Description

Default Value

Since

Name

Name that uniquely identify the mapping

1.27

Base SObject Type

The base object on which the report is based (e.g. Contact)

1.27

Column Name

The value as reported in the error message for the rule (e.g. ADDRESS2_STATE_CODE)

1.27

Field API Syntax

The correct syntax that would be used when referencing the field in a regular SOQL query

SWT Settings

It stores the general preferences that influence the application behavior.

The Fields

Name

Description

Default Value

Since

Advanced Mode

It enables the creation of rule based on custom SOQLs. Once the setting is set to true the rule form will show the checkbox use custom SOQL.

false

1.0

Default Rule Status

It determines the default status for when a new rule is created through the SalesWings Rules Center page

Inactive

1.0

Default Rule Set Status

It determines the default status for when a new rule set is created through the custom SalesWings Rules Center page

Inactive

1.0

Exclude Converted Leads

It instructs the engine to exclude converted leads from the process. This is done in order to avoid potential issues where, without specifying any additional permissions, converted leads cannot be updated (Salesforce flags them as read-only).

Note: This setting is Lead object-centric. It doesn't apply to any other object set for a rule set.

true

1.0

Execution Batch Size

It determines the batch size used to process each single rule.

2000

1.0

Execution Batch Error Threshold %

It defines the batch error threshold percentage over which a given rule will be marked as invalid. For example, if the batch size is 1000 and the percentage is 25, the rule will be marked as inactive if more than 249 records cannot be updated for some reason (permissions, validation rules, etc.)

50

1.27

Execution Buffer Size

It determines the number of execution records to keep (as history).

Note: Every time the process run a new set of execution records get created. At the beginning of a new execution the execution records in excess to the value of this record get truncated.

100

1.0

Revert Deleted Rule Set Def. Behavior

It determines the default engine behavior regarding reversal process of deleted rule sets.

Note: This settings is also applied to the each single rule under the rule set.

false

1.0

Revert Inactive Rule Set Def. Behavior

It determines the default engine behavior regarding reversal process of deactivated rule set.

Note: This settings is also applied to the each single rule under the rule set.

false

1.0

Rule Engine Batch Minutes Interval

It determines the interval in minutes to apply between engine executions.

60

1.0

Show Unsupported Reports

It determines whether to filter out reports that result incompatible. This is normally due to their being based on objects different from the ones that the engine currently supports (Account, Contact, Lead, Opportunity, Campaign) or using an unsupported scope (My Records).

true

1.0

Deprecated Fields

Name

Since

Job Monitor Batch Delay

1.27

Throw Permission Exceptions

5.0

SWT Trigger Handler Routine

This custom setting is currently unused.


The following SalesWings Toolbox Options are currently obsolete:

The following SalesWings Toolbox Options are currently obsolete:

Name

API Name

Since

SWT Rule Data

swscore__Rule_Data__c

1.28

Don't hesitate to schedule a Training Call with us!

Did this answer your question?