How is the ECC variable created for chat, inbound and outbound email activities?

Question

Options

• AUser.ece.email id
• BUser.ece task id
• CUser.ece.activity.id
• DUser.ece. .customer.name

• A
  3% (1)
• B
  6% (2)
• C
  91% (30)

Explanation

Option C (User.ece.activity.id) is correct because Cisco Enterprise Chat and Email (ECE) uses a unified concept of an activity to represent any interaction - whether it's a chat session, an inbound email, or an outbound email. The ECC variable User.ece.activity.id carries the unique activity identifier from ECE into the Unified CCE routing script, linking the two systems regardless of channel type.

Why the distractors are wrong:

• A (User.ece.email id) is channel-specific and uses broken syntax (space before id), making it invalid for all three activity types.
• B (User.ece task id) incorrectly uses "task" instead of "activity" and is missing proper dot-notation delimiters.
• D (User.ece. .customer.name) has an illegal space in the variable path and references customer name - a different data point entirely, not an activity identifier.

Memory tip: All three channel types (chat, inbound email, outbound email) share one thing in common - they are all called activities in ECE. So the variable naturally ends in .activity.id, not .email.id or .task.id. If you remember "ECE = activities," option C follows logically.

No community discussion yet for this question.