Employee Onboarding assignment not using HRSD

[Nancy34]

I am working on a ServiceNow Employee Onboarding use case using Service Catalog + Flow Designer.

Can someone please help me with this requirement. Atttahced is the requirement im trying to do from my end 

[mza-guille]

<p>Hello Nancy34,</p><p>For Employee Onboarding without HRSD, you can use Service Catalog + Flow Designer. Create a catalog item with variables for manager, department, and start date. Then build a flow that triggers on catalog request and creates tasks for IT, HR, and facilities using Create Catalog Task actions. Use Look Up Record to find the manager from the assignment group and set dynamic assignments.</p><p>Would you like more details on the Flow Designer configuration?</p>

[Nancy34]

I have been doing that ! that is requirement 

[mza-guille]

Thanks, Nancy. Understood.

I cannot open the Assign.docx attachment from my side, so I do not want to assume what the requirement actually says. Could you share the key points here, especially:

• Which specific tasks or groups need to receive the new-hire onboarding work (IT, HR, facilities, manager, etc.).
• Whether assignment should be based on the new hire, the manager, the department/location, or a combination.
• Whether the routing should be different per new-hire type (office, remote, contractor, intern).
• What the exact issue is today (for example, the wrong group is assigned, no group is assigned, the same task is created multiple times, or the flow stops at a specific step).

In the meantime, a clean, maintainable pattern that I usually recommend for this type of requirement is:

1. One Service Catalog item as the entry point (for the requestor or HR coordinator to fill in new-hire data).
2. One central onboarding routing table, for example u_onboarding_routing, with at least:
3. - trigger condition (department, location, employee type),
4. - fulfillment group,
5. - approver group,
6. - sequence or SLA,
7. - active flag.
8. One Flow Designer flow that:
9. - triggers on the catalog item submission,
10. - looks up the routing record(s) matching the new-hire attributes,
11. - creates one Catalog Task per matching group,
12. - sets the assignment group dynamically from the routing record,
13. - sends approvals to the matching approver group.

This avoids hard-coding if/else branches in the Flow and makes it easy for HR/IT to add new departments or roles without changing the Flow.

If you can paste the requirement summary, I can map the rule structure and the Flow Designer steps specifically to your case.