you need to implement a new custom field, and that the field will need to be available to agents to enter and maintain the values

Your customer wants you to separate their contact records by development. You determine that to
enable this functionality, you need to implement a new custom field, and that the field will need to
be available to agents to enter and maintain the values. Select the four steps to accomplish this.

Your customer wants you to separate their contact records by development. You determine that to
enable this functionality, you need to implement a new custom field, and that the field will need to
be available to agents to enter and maintain the values. Select the four steps to accomplish this.

A.
Create a “department” custom field in the incident table.

B.
Set the custom field data type to Text Field.

C.
Create a navigation set that includes the “department” custom field.

D.
Update the Context Workspace with the new “department” custom field.

E.
Create a “department” custom Field in the contact table.

F.
Add a name and a column name for the new custom field.

Explanation:

Note:
* Custom Fields
Custom Fields are created in the knowledge base to allow the collection of business-specific
information, to best meet the organization’s needs.
After being created, custom fields can be added to workspaces (D) and scripts, be used as search
filters in reports, or as audience filters in RightNow Marketing and RightNow Feedback.
When creating a custom field, Admins can specify whether it is visible and editable on the Agent
Desktop and, for some custom fields, visible and available to gather details on the Customer Portal.
Admins can also specify a data type for the field, choose whether the field is required or not, and set
a default value.
Text field data types allow you to create an input mask to require that information entered in the
field matches a defined format.
When Admins add or edit custom fields, those modifications may be completed in real time or
scheduled and performed in the background.
* When adding custom fields, there are several visibility options. The visibility options define where
and how custom fields are presented on the Agent Desktop and the Customer Portal. For example,
you can make a contact custom field visible to staff members when adding an incident, but restrict
their ability to edit it.
Custom fields with end-user visibility are displayed on the Customer Portal. If you display a custom
field that is not editable by customers, it does not appear on the Ask a Question page. There are
other ways to determine visibility on the Customer Portal, such as widgets and page code.
Answer, incident, contact, opportunity, organization, sales quotes, and tasks custom fields must also
be added to the appropriate record’s workspace.



Leave a Reply 5

Your email address will not be published. Required fields are marked *


Suchitra Prakash

Suchitra Prakash

Questions clearly states “Your customer wants you to separate their contact records by development” so, why should the custom field be created in incident table. It should be created in Contact table and rest of the answers are right.

Please provide correct answer for this question.