HR Task is created with errors. (HR Task is of type collect employee input)

satya30
Tera Contributor

Hi all,

I have an issue with the HR Task of type collect employee input form. I created flow to collect the metric results and map them to the HR Case fields. 
This employee form is the existing form with 4 string fields. I added two additional fields "is the applicant from California? Yes or no field and specify a state or country string field
After the HR Task is created, the assigned person can see the employee form and complete it.
HR Task is created with errors. (HR Task is of type collect employee input) but then the values are updated to the HR case correctly.

satya30_0-1768195684931.pngsatya30_1-1768195700969.pngsatya30_2-1768195739191.pngsatya30_3-1768195751549.png

 

satya30_4-1768195828261.pngsatya30_5-1768195849257.png

 


Please help me with the issue on what I can do? 
@Ankur Bawiskar please help me

 

3 REPLIES 3

Mark Manders
Mega Patron

I really don't know why only Ankur should answer, so here are my two cents:

 

You have error messages. Those already tell you where to look. Your conditions aren't set correctly (they return too many records, causing the system not to know the record it should get) and you have an ACL issue on your custom field (if the user isn't allowed to write to it, it can't be updated, since the flow runs as the user (probably)).

What happened after you set the conditions correctly and created/updated the ACL?


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Kohei Tominaga1
Tera Guru

Hi, @satya30 

The "Employee Form Error" you're seeing likely indicates an issue with the native field mapping functionality of the Employee Form itself. Since you've successfully implemented field mapping using a Flow and your HR Case fields are being updated correctly, you can safely ignore this error.

To prevent this error from appearing, you might consider reviewing the Employee Form's configuration and disabling the field mapping settings there, as your Flow is already handling this.

KoheiTominaga1_0-1768266236882.png

Please mark any helpful or correct solutions as such. That helps others find their solutions.

Tanuja S1
Tera Contributor

Hello,

 

Always make sure the Employee form conditions are set to conditions which always returns unique ID.  In case there are multiple records identified as part of the conditions defined (as per the error message in screenshot), it will throw error.

 

Thanks,

Tanuja S