Hi @svedok, 

could you please send a screenshot of your configuration rule or JSON so we can investigate the case? 

Kind regards,

Nika

Hi @svedok,

while waiting for your configuration, I attempted to replicate the described case to identify the root cause of the issue. I’m sharing my conclusions with you to help speed up the process if you’re in a hurry.

If you’re searching for an employee whose role matches any value from the object you’re currently creating via Object Operations, this won’t be possible, as the object does not exist yet. For example, searching for an employee where the role equals the name of the task is not possible because task hasn’t been created yet.

As a workaround, I suggest creating the Task object first and then configuring another rule in Property Operations module that triggers when the Task object is created. In that way, you’ll be able to set up the property value to the specific person responsible for the newly created task.

I hope this helps! If you need further assistance or a JSON example, feel free to reach out.

Best regards,

Nika