Demo Core Utilities

Demo Core Utilities groups 13 related components across Scripts. The configuration centers on scripts and includes 13 scripts that support the process.

How the pieces work together

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

Components

Component	Type	Role in this configuration
Demo Core Utilities Client	Client Script	Runs automation logic for demo core utilities.
Demo Core Utilities Suitelet	Suitelet	Runs automation logic for demo core utilities.
Demo Core Utilities User Event	User Event Script	Runs automation logic for demo core utilities.
Demo Core Utilities Scheduled	Scheduled Script	Runs automation logic for demo core utilities.
Demo Core Utilities Workflow Action	Workflow Action Script	Runs automation logic for demo core utilities.
Demo Core Utilities Suitelet	Suitelet	Runs automation logic for demo core utilities.
Demo Core Utilities User Event	User Event Script	Runs automation logic for demo core utilities.
Demo Core Utilities Map Reduce	Map/Reduce Script	Runs automation logic for demo core utilities.
Demo Core Utilities Scheduled	Scheduled Script	Runs automation logic for demo core utilities.
Demo Core Utilities Map Reduce	Map/Reduce Script	Runs automation logic for demo core utilities.
Demo Core Utilities Scheduled	Scheduled Script	Runs automation logic for demo core utilities.
Demo Core Utilities Map Reduce	Map/Reduce Script	Runs automation logic for demo core utilities.
Demo Core Utilities Client	Client Script	Runs automation logic for demo core utilities.

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.