Which two features should a consultant keep in mind when proosing the use of JSON-based mapping over object-based mapping for contract templates?

Which two features should a consultant keep in mind when proosing the use of JSON-based mapping over object-based mapping for contract templates?
A . documents cannot display attribute data unless the custom section in the document template is used
B . JSON-mapping allows for filtering individual line items or repeatable content items to display in a document, but object-based mapping does not
C . the consultant can use the item section for any type of item list, not only for line items
D . only contract, opportunity, order, and quote objects are supported when mapping fields is JSON-based mapping
E . the data to extract and merge into the template must exist in standard objects

Answer: B, C

Explanation:

When proposing the use of JSON-based mapping over object-based mapping for contract templates, a consultant should keep in mind the following features:

JSON-mapping allows for filtering individual line items or repeatable content items to display in a document, but object-based mapping does not: This feature provides greater flexibility in customizing the content that appears in the document, allowing for more targeted and relevant information to be included.

The consultant can use the item section for any type of item list, not only for line items: This versatility enables the inclusion of various types of data lists in the document, beyond just standard line items, enhancing the document’s comprehensiveness and relevance to the specific use case.

Reference: Salesforce Documentation on JSON-based mapping: https://help.salesforce.com/

Salesforce Developer Guide on JSON and Object Mapping: https://developer.salesforce.com/