What does the Flow field do on the HR Service Config Form?

[Balazs Borzovan]

We are trying to run a flow for whenever a HR service is created - we found the fulfillment type can be Flow and we can select a Flow (or Subflow) from a reference table. - but why? What does this do? We assumed that it would start the flow, but it does not (or we are doing something wrong).

When creating a flow, we MUST add a trigger - and we can't select "from HR service" like with Catalog items. So how does the flow get triggered from the HR Service?

We are on Zürich.

[prajaktajga]

Hello @Balazs Borzovan ,
You can refer the below links,
https://www.servicenow.com/docs/r/employee-service-management/hr-service-delivery/hr-flows-and-trigg...

https://www.youtube.com/watch?v=NK2zRCW1GhU
How the flow will get executed:-

• The HR Case is created

• HRSD fulfillment logic runs

• If fulfillment type = Flow → the platform calls Flow Designer and starts the selected flow explicitly, passing the HR Case record as input

This is why:

• The Flow does not need  a trigger

• The Flow is not waiting for an event

• The Flow is invoked directly

[Kohei Tominaga1 · Accepted solution]

Hi, @Balazs Borzovan 

The "Fulfillment type can be Flow" option on an HR Service, which allows you to select a Flow or Subflow, is primarily for documentation and administrative purposes only.

It does not automatically trigger the selected Flow. Unlike Catalog Items where a specific trigger might link directly to an HR Service, for standard HR Services, you must explicitly configure the Flow's trigger yourself.

To trigger a Flow based on an HR Service creation, you need to set up a trigger within your Flow designer. For example, your Flow's trigger condition could be: "When a Record is created" on the HR Case table, with additional conditions like "HR Service is [Your Specific HR Service]".
Please mark any helpful or correct solutions as such. That helps others find their solutions.

[Balazs Borzovan]

Thanks for the answer!
I see, I find it a bit misleading especially compared with Requests, but if that's the way it is, then fine. We ended up triggering the Flow with on Creation -> if Hr Service.Flow is <flow-name> which now (kind of) uses the Flow added in the HR service at least on an info level.

[Nayara Gomes da]

Do you can use the sn_hr_core_service table with a trigger or is a specific HR Service? If is a specific do you can put the sysIDs of the HR service in a property separate with commas if are more than 1 and create a subflow that is call in the flow like inputs passing theses sysID trigger from sn_hr_core_service. Is more than 1 HR Service? Is they used in a record producer, template or any other component?