SFM Transaction Manager - SFM Transaction Designer
1. Navigate to > > .
2. Click Org Profiles tab.
3. Select the Active profile.
4. Click Settings tab.
5. Expand the module and the submodule to view the relevant settings.
Module: SFM Transaction Manager; Submodule: SFM Transaction Designer
|
Setting ID
|
Setting Name
|
Description
|
Data Type
|
Default Value
|
||
|---|---|---|---|---|---|---|
|
SET001
|
Enable auto-suggestion on mapping
|
Enable auto-suggestion on mapping
|
Boolean
|
True
|
||
|
SET002
|
Salesforce API Version for partner server URL
|
Salesforce API Version for partner server URL
|
Text
|
39
|
||
|
SET003
|
Maximum number of sort fields which can be configured for detail sections.
|
This setting specifies the maximum number of sort fields which can be configured for details sections in SFM page layouts. As of Salesforce Spring 13 release, maximum number of sort fields is limited to 32.
|
Number
|
5
|
||
|
SET005
|
Max number of fields processed in one API invocation.
|
Number of fields retrieved in an API call.
|
Number
|
500
|
||
|
SET006
|
SFM Designer Page
|
When this setting is set to HTML, the new HTML-5 based designer pages are launched. When set to Flash, old Flash based Visualforce pages are launched. Note: Keep this setting as HTML as Flash based designer pages will no more be supported with Flash EOL.
|
Picklist
|
HTML
|
||
|
SET007
|
Manage Object Batch Size for Designer.
|
This is an internal setting used to fetch Objects in multiple batches when loading Designer screen. Useful when objects have large number of custom fields or has Picklist with large volumes of values. Default value 5 indicates that each batch will have maximum 5 objects or objects in the batch has total fields less than or equal to 800 fields.Reduce this value when blank page loads or fields are missing in the designer editor screen due to Salesforce governor limit exception.
|
Number
|
5
|
