Create Custom Field Customer Card

Creates a new custom field in the customer card.

Dependencies

• This action requires Digital Experience.
• Before working with digital scripts, learn about the differences between traditional ACD scripts and digital scripts.

Supported Script Types

Digital

Comparison of Similar Actions

The following actions allow you to access Digital Experiencecustomer cards from digital scripts types: 

• Get Customer
• Create Custom Field Customer Card
• Get Custom Field
• Update Custom Field

To perform the same tasks in supported non-digital scripts, use: 

• CC Create
• CC Custom Fields
• CCPostMessage

Input Properties

These properties define data that the action uses when executing.

Property	Description
Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.
Ident	Enter the name or ID that you want to use to identify this field.
IsEditable	Select True or False to indicate whether the agent can edit this field.
IsVisibleInCustomerCard	Select True or False to indicate whether you want this field to be visible in the customer card.
IsVisibleInPostDetail	Select True or False to indicate whether this field should be visible in the customer card preview visible in the right panel in MAX. This field only applies if your agents use MAX.
Label	Enter the label for this field. This is the text that the agent sees in the customer card or any other location where the field appears.
Required	Select True or False to indicate whether this field is required.
Type	Choose from String, Numeric, or Datetime. The type you select here changes the Value property to interpret the data entered in the Value field. For example, if you select String and enter the value 1+1, the actual value assigned to the variable is 1+1. However, if you select Numeric and enter the value 1+1, the value assigned to the variable is 2.
Value	The value or data to be stored.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition	Description
Default	Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
Error	The path taken when the action doesn't execute properly. For example, when there's an unexpected problem, such as poor connectivity, syntax errors, HTTP error codes, and so on. The ERR variable should be populated with a condensed explanation of the problem.
Success	Path taken if the action completes without errors and any API calls or data returns were successful (2xx response codes).