To make a custom component available for the utility bar in Salesforce, the component needs to be explicitly tagged for use in the utility bar. Salesforce components require specific configurations to be available in different parts of the application, such as the utility bar, record pages, or app pages.
Option C: For use on the utility bar: When a custom Lightning component is developed, it must include a specific target tag in its .js-meta.xml configuration file that marks it as usable in the utility bar. This is done by setting the target to "lightning__UtilityBar". Without this tag, the component will not appear as an option to add to the utility bar in the App Manager.
Example of how the component is tagged in the meta.xml file:
xml
Copy code
<targets>
<target>lightning__UtilityBar</target>
</targets>
Reference:
Option A: For use on record pages: This tag makes the component available only on record pages, but not the utility bar. The component would have a target for lightning__RecordPage in this case.
Option B: For use in Lightning App Builder: This option would allow the component to be used in the Lightning App Builder, but it wouldn't make the component available for the utility bar. App Builder placement is typically for page layouts.
Option D: For use in App Manager: This is incorrect, as App Manager is used for managing apps and not for tagging components for availability.
In summary, to make the component available for the utility bar, it needs to be specifically tagged for that purpose using the lightning__UtilityBar target in the component's metadata file.
Reference:
Utility Bar Metadata Configuration