Hi.

Sounds like an interesting idea.

As I understand, it is currently working as designed. So, if it won’t find a specific entry, it won’t process anything against to.

I currently have some similar setup like yours, but it does not have sooo many entries like yours, and I have made it one by one.

I haven’t tried myself if it would be possible to combine it with standard conditionals and process against them.

Viewing again your screenshot, I’m also thinking of:

The Reader node is instructed to read from (again, it is working as designed), so, would you evaluate not filling specifics in the reader node (Don’t specify Jira), so it might work your desired way. Haven’t tried this on my side either, but I’ll sure try later.

Hope this helps.

Regards,

Thanks but the problem is that the last node in the dependent field is mandatory as well. So it is not possible to stop one level above. I cannot leave it blank.
And also I have the impression that this worked some months ago...

oops. I clicked best answer instead of like

Hello @msconfig87 I also would like to see some further development in relation to the Reader node. What would be amazing is if we could build out custom objects in such a way where we reference other Custom Objects in a “Main” object using lookup fields, and then were able to have the Reader node return a record based on values found in those other custom objects. That alone would significantly enhance the scalability!

For example, if I could create a custom object of “Managers” that has fields like First Name, Last Name, Job Title. And a custom object of “Job Titles” that has a field of Title. Then in the Managers object we set the value for the field “Job Title” to reference the values in the Job Title custom object.

In the reader node we would then want to reference the field Job Title of the “Managers” custom object and have it return First Name and Last Name of the Manager it finds. This is not currently something that it can do.

Not a great example but I hopefully get the idea across. 

@zachary.king I am doing something similar currently but only in Service Request:

first CO:

Second CO:

Service Item with dependency on the CO:

Only Academy jobs listed

Here select Practice as a filter

Have not tried it with the reader node yet

@zachary.king I just filed at ticket with FreshService on this as one of the main issues is the ability to sort the results or show more than the first 50 objects of the custom object table you are pulling from.  Both sorting and returned results are issues for us.

Select from our job/title custom object (75 entries) only the first 50 show in drop down ordered by entry into Custom objects table.  HR tries to find a title to assign to someone in service catalog item and … hey I can’t find the title …. painful.