Before
A team member would likely initiate upgrades for each firewall individually, check the result of every operation, and record failed upgrades for follow-up. Someone would then compile the results and send a summary to the team.
How it works
- Receive the triggering email and prepare the designated list of firewall equipment.
- Initiate an upgrade for each firewall, evaluate the result, and track unsuccessful operations.
- Send the team a completion summary covering the upgrade results and tracked failures.
Workflow details
- Trigger and preparation: The workflow starts when an email is received and prepares the designated list of firewall equipment for processing.
- Equipment-by-equipment execution: Each firewall is handled sequentially, with the workflow initiating an upgrade request for the individual equipment.
- Result validation: After each upgrade request, the workflow evaluates whether the operation succeeded and routes unsuccessful results to failure tracking.
- Failure monitoring: Failed upgrades are recorded for follow-up while the workflow continues according to the configured processing path for the equipment list.
- Team handoff: Once the list has been processed, the workflow sends a resume message to the team containing the upgrade results and any tracked failures.
What changed
Upgrade initiation and outcome checking now happen sequentially for each firewall, with failed operations routed to tracking and the final results delivered to the team in an automated summary.
Work removed
Manually initiating each firewall upgrade, checking each upgrade result, recording failed upgrades, compiling the outcome list, and sending the team summary.
Expected outcome
For each firewall in the designated list, the workflow automates one upgrade request and one outcome check, followed by one team summary; exact time savings are not supported by the available definition.
