A company called Universal Containers would like to track bugs within Sales force.
The company needs to track the bug's severity and type as well as its status and description.
Bugs should be related to Cases, but the bug's owner will be different than the owner of the case.
How can the Universal Containers administrator meet these requirements?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
The relationship would be established using a look up to the cases object so that independent ownership can be established.
It will also allow the related bugs to be visible as a related list on the cases screen.
To track bugs within Salesforce, Universal Containers can meet their requirements in several ways, as follows:
A. Create a section on the case page layout: This option is useful if the Universal Containers only need to track basic information about bugs, such as severity and type. The administrator can create a custom section on the case page layout and add fields for these bug attributes. However, this option does not allow for the tracking of additional information about bugs such as status and description. Additionally, this option does not create a dedicated object for bugs, which could limit the ability to report on bugs.
B. Create a field on cases: Similar to option A, this option can be useful if the Universal Containers only need to track basic information about bugs. The administrator can create custom fields on the case object for attributes such as severity and type. However, as with option A, this option does not allow for the tracking of additional information about bugs and does not create a dedicated object for bugs.
C. Create a custom object for bugs and relate it to cases: This option provides the most flexibility and granularity for tracking bugs. The administrator can create a custom object for bugs with fields for severity, type, status, and description. The bugs object can then be related to the cases object via a lookup field. This approach allows for the tracking of additional information about bugs and enables more robust reporting on bugs. Additionally, because bugs are tracked in a separate object, they can have their own owner field and ownership rules.
D. Create a relationship between the standard bug object and the standard case object: This option is not recommended since there is no standard bug object in Salesforce. While it is possible to create a custom object for bugs and relate it to the case object, as described in option C, there is no pre-existing standard object for bugs in Salesforce.
In conclusion, Option C - Create a custom object for bugs and relate it to cases - is the most appropriate solution for tracking bugs within Salesforce for Universal Containers. This approach allows for the most flexibility in tracking and reporting on bugs while still maintaining a relationship to the case object.