Before
Administrators likely translated each application decision into separate URL-category and application-tag changes. They then removed outdated assignments, activated the configuration where required, and checked both consoles individually before reporting the outcome.
How it works
- Receive the application decision and validate the name and supported policy status.
- Remove old policy assignments and apply the matching category and tag across the enforcement consoles.
- Activate the Zscaler configuration, verify both update results, and return a consolidated summary.
Workflow details
- Trigger and validation: The workflow starts when it receives an application name, status, and optional comma-separated domains. It validates that the name is present and that the status is one of the supported policy states.
- Policy translation: The status is mapped to a corresponding enforcement category and application tag. For valid inputs, assignments associated with the other policy states are prepared for removal so the application has one current classification.
- Console updates: For applications with domains, the workflow updates the relevant URL categories; it also updates the application tags. The demonstration uses simulated responses for these update operations.
- Activation and verification: The Zscaler configuration is activated after category changes. The workflow evaluates returned identifiers, activation status, and tag-update statuses to determine whether each policy update succeeded, failed, or required no action.
- Result delivery: A final summary reports the Zscaler and Netskope outcomes, the selected policy state, and relevant category, tag, and domain details. Unsupported or incomplete policy decisions produce a no-policy action result rather than an update.
What changed
A single event now drives the status mapping, cleanup, cross-console updates, Zscaler activation, and result checks. The caller receives separate outcomes for both enforcement systems without manually switching between consoles to reconcile the decision.
Work removed
Manually translating statuses, removing obsolete categories and tags, adding the current assignments in separate consoles, activating the Zscaler configuration, checking update results, and compiling a status summary.
Expected outcome
For each valid decision, one automated run replaces at least two separate policy updates plus a follow-up activation and result check, helping keep application classifications aligned across both enforcement consoles.
