問題文
A national insurance carrier writes auto policies and life policies. The two lines share only 6 of about 40 attributes, each line is measured with its own set of metrics, and each underwriting team asks for different validation and different automation. An architect must decide between one object with two record types and two separate custom objects. Which approach fits these requirements?
選択肢
- Build one object with two record types, because record types always keep related processes together, and a record type carries its own validation and its own automation for each of the two lines.
- Build two separate custom objects, because the attribute overlap is small and each line is measured on its own, and bring the few shared measures together in a report or in a summary object.
- Build one object per line of business and also a third object that duplicates every attribute of both lines, so that reporting always runs against the third object while the two source objects keep the line specific validation and automation rules in place.
- Build one object with two record types and hide the unused attributes with page layouts, because a single object guarantees that every future report can span both lines without extra work, and the two underwriting teams work from the same layout set.