How to handle 1-to-N mapping between a single Global Call Activity step and multiple country-localized sub-processes in Celonis Process Designer (Symbio)

Hi Zanelk,

This is exactly what Symbio's Core-Plus-Delta capability is built for. The 1:1 Process reference is by design: it keeps every link clean and governable, and Symbio gives you a purpose-built way to fan one global step out to many localized processes through variants, attributes, and scope filters.

Linking one global step to ten country sub-processes

Keep Step 16 as a single node in HR-7-3-1a with a single Process reference. Then choose the pattern that fits your governance model:

Variant-based (ideal when the deltas are "the same step, localized"): point the reference at one logical localized-task object, and model the ten country deltas (CN-1a, MY-1a, SG-1a, …) as variants of that object. Each variant carries a value of the Locations attribute, and the scope filter resolves the right one per user. Clean, single-source, fully governed.

Router/hub (ideal when the country processes are substantial and locally owned): Step 16 references a single "Localized Hub" process, which holds the ten country call activities, each tagged with its Locations value. This keeps Core ownership central and Delta ownership with the local teams — a great fit for a 10-country APAC model.

Seamless 1-click experience in Process Navigator

The Locations attribute is what makes this effortless for end users. Define it once as a governed attribute (a controlled value list of your 10 APAC codes), apply it to every Delta variant/sub-process, and configure Locations as a scope filter in Navigator. When a user's location is set, Navigator resolves Step 16 straight to the matching country variant — the global master and Core steps render once, and Step 16 becomes a single clickable step that opens SG-1a for a Singapore user, CN-1a for a China user, and so on. One click, no duplicated global steps.

A few best practices to get the most from it: keep Core steps unscoped so they always show for everyone, and scope only the Delta objects. Give each Delta variant a single Locations value so resolution is precise. And set a sensible default for users whose location has no delta — typically the Core step on its own.

This gives you a single global master, cleanly governed country deltas, and a seamless localized experience for every user. Let me know if you need more clarity on this.

Thanks!