Child Sections
If there are more than 5 child sections, consider splitting the transaction into multiple SFM transactions, each focused on specific functional aspects. This is because when there are multiple child sections and/or scores of records per section, in customer orgs with other customizations such as large number of custom fields, triggers, and workflows, Salesforce governor limit issues can be encountered. For better user experience, the transactions can be defined as a logical flow in SFM Wizard, by configuring handover from one transaction to another.
An example of such splitting can be seen with the standard transactions designed to manage Terms and Coverages of Service Contracts. There are separate transactions to manage coverages such as Products, Contacts, Locations, and Services, configure Parts Pricing with associated discounts, edit Labor Pricing and Expense Pricing, and define Travel Policy and PM Offerings.
Was this helpful?