Customer Duplicate Review groups 14 related components across Scripts. The configuration centers on scripts and includes 14 scripts that support the process.

How the pieces work together

  • This configuration has 14 documented components, with the strongest activity in Scripts.
  • Review the scripts and workflows first when changing how customer duplicate review behaves.
  • Use the fields, lists, records, and searches as supporting configuration for the process.

Components

ComponentTypeRole in this configuration
Customer Duplicate Review ScheduledScheduled ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review SuiteletSuiteletRuns automation logic for customer duplicate review.
Customer Duplicate Review RESTletRESTletRuns automation logic for customer duplicate review.
Customer Duplicate Review User EventUser Event ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review User EventUser Event ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review ClientClient ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review User EventUser Event ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review RESTletRESTletRuns automation logic for customer duplicate review.
Customer Duplicate Review User EventUser Event ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review User EventUser Event ScriptRuns automation logic for customer duplicate review.
Customer Duplicate Review SuiteletSuiteletRuns automation logic for customer duplicate review.
Customer Duplicate Review SuiteletSuiteletRuns automation logic for customer duplicate review.
Customer Duplicate Review SuiteletSuiteletRuns automation logic for customer duplicate review.
Customer Duplicate Review ClientClient ScriptRuns automation logic for customer duplicate review.

What to review first

  • Confirm the process owner understands the components listed above.
  • Review scripts and workflows before changing supporting fields or searches.
  • Validate saved searches and fields after any workflow or script change.