CCP ediEnterprise & Trigger Automation 3 — Questions and Answers
Question 1: In CargoWise Trigger Automation, what is the difference between an 'Event' trigger and a 'Scheduled' trigger?
- Event triggers only work for air freight; scheduled triggers only work for sea freight
- Event triggers fire in response to a data change or action in the system; scheduled triggers fire at defined times (Correct answer)
- Event triggers require admin approval; scheduled triggers run automatically without approval
- Event triggers send emails only; scheduled triggers can perform any action
Correct answer: Event triggers fire in response to a data change or action in the system; scheduled triggers fire at defined times
Event triggers respond to real-time system actions (e.g., status changes, record creation), while scheduled triggers execute at pre-configured time intervals.
Question 2: When building a Trigger in CargoWise, what is the purpose of a 'Condition' (or filter)?
- To define who receives automated email notifications
- To restrict which records the trigger acts upon based on specific criteria (Correct answer)
- To set the priority order of triggers when multiple fire simultaneously
- To specify the EDI message format used in the automation
Correct answer: To restrict which records the trigger acts upon based on specific criteria
Conditions filter the records the trigger evaluates, ensuring the automation only fires on records that meet the defined criteria.
Question 3: Which CargoWise Trigger action would you use to automatically update a field value on a shipment record when a milestone is reached?
- Send Notification
- Create Event
- Update Field (Correct answer)
- Generate Document
Correct answer: Update Field
The 'Update Field' action modifies a specific field value on the target record, allowing automated data entry when trigger conditions are met.
Question 4: In CargoWise Trigger Automation, what does 'Trigger Chaining' refer to?
- Linking multiple EDI trading partners into a single transmission path
- An outcome of one trigger's action satisfying the event condition of a subsequent trigger (Correct answer)
- Scheduling triggers to run in a fixed sequence during off-peak hours
- Connecting CargoWise triggers to external REST APIs
Correct answer: An outcome of one trigger's action satisfying the event condition of a subsequent trigger
Trigger chaining occurs when the action performed by one trigger causes a record change that in turn fires another trigger, creating a cascade of automated actions.
Question 5: Which of the following is a valid 'Action' available in CargoWise Trigger Automation?
- Automatically reclassify HS codes based on product description AI
- Send an eAdaptor XML message to an external party (Correct answer)
- Calculate customs duty amounts from tariff schedules
- Merge duplicate organization records
Correct answer: Send an eAdaptor XML message to an external party
CargoWise Trigger Automation can send eAdaptor XML messages to external parties, enabling integration with partner systems without custom coding.
Question 6: When a CargoWise Trigger is set to fire 'On Save' for a shipment, what determines if the trigger actually executes?
- The trigger executes for every save regardless of what changed
- The trigger only executes if the record is saved by a supervisor-level user
- The trigger evaluates defined conditions; it only executes if those conditions are satisfied at the time of save (Correct answer)
- The trigger executes only on the first save after record creation, never on subsequent saves
Correct answer: The trigger evaluates defined conditions; it only executes if those conditions are satisfied at the time of save
An 'On Save' trigger evaluates its conditions each time the record is saved and only fires the action if all conditions are currently met.
Question 7: What is the recommended approach to prevent infinite loops in CargoWise Trigger Automation?
- Set a global trigger execution limit of 100 per day in system settings
- Use conditions to ensure the trigger only fires when the target field is not already set to the updated value (Correct answer)
- Disable all triggers during batch import operations
- Configure triggers to only fire during business hours using time-of-day filtering
Correct answer: Use conditions to ensure the trigger only fires when the target field is not already set to the updated value
Adding a condition that checks whether the field is already in the desired state prevents the trigger from firing repeatedly on its own updates.
CCP ediEnterprise & Trigger Automation 3
In CargoWise Trigger Automation, what is the difference between an 'Event' trigger and a 'Scheduled' trigger?