service-omni-routing-flow-deploy
service-omni-routing-flow-deploy
Voice runtime proof depends on a provisioned Contact Center. Flow redeploys report
Changedeven when the deployed configuration is unchanged.
Deploy an Omni-Channel routing Flow via the Metadata API, confirm it lands Active, and prove it routes work — either by CLI invocation (the autolaunched dry-run) or by observing real routing side effects (the record-triggered variant). service-omni-channel-setup-coordinate wires it in after service-omni-queue-deploy has produced the target queue and its members are bound.
Variants
Four assets ship under assets/force-app/main/default/flows/ — an autolaunched and a record-triggered variant for each of Case and VoiceCall. Selection is by --target Case|VoiceCall (default Case) and --trigger.
| Variant | Shape | Proves | Routes real work? |
|---|---|---|---|
Omni_Route_Cases / Omni_Route_VoiceCalls (default) |
Autolaunched, dryRun gate |
CLI invocability via Actions REST, no side effects | No |
Omni_Route_Case_Trigger / Omni_Route_VoiceCall_Trigger (--trigger) |
Record-triggered on insert, calls routeWork |
Real routing — the insert creates PendingServiceRouting/AgentWork |
Yes |
The autolaunched variant de-risks the headless CLI path cheaply; the record-triggered variant proves real records reach a queue. A full steel thread deploys the record-triggered variant.
With --trigger --routing-type SkillsBased, the record-triggered variant is drawn from a sibling <FlowDN>.SkillsBased.flow-meta.xml asset that emits routingType=SkillsBased plus a non-null skillOption. The base trigger flows hardcode routingType=QueueBased, so a skills-based-routing org config never takes effect at runtime — this variant is what makes it route by skill (W-24069467).