It's all about the answers!

Ask a question

HTTP based filtered value providers, allowing only valid parent/child choices and clearing on modification

Fred Bickford (281131) | asked Jun 19 '15, 10:51 a.m.
edited Jun 19 '15, 12:06 p.m.
RTC 5.0.2 iFix006


I have successfully implement 3 fields that I am driving with values externally via HTTP filtered value sets.
I have also set up that those fields has a dependency on the previous one to create a parent child relationship, this works fine

Yet I am seeing (maybe somie basic RTC that I am missing) that the Workitem will allow for a child field to be selected previous to its parents, and also even if not in the parents list,....

so it works if I select 1st field... then 2nd and 3rd....only

also if I change the 1st field to a different value the 2nd and 3rd values seem to perist,,,,

Donald Nong commented Jun 22 '15, 3:00 a.m.

Have you implemented any validation mechanism? If you follow that blog exactly, the attributes are of "small string" type and I doubt that RTC will by default enforce any validation on them.

One answer

permanent link
Ralph Schoon (61.1k33643) | answered Jun 22 '15, 3:55 a.m.
edited Jun 22 '15, 3:58 a.m.
 There is no notion of parent/child attributes in RTC. All attributes are completely independent of each other.
What you can do as Donald hints, is creating validators for a filed that validate its content and prevent saving if the validation fails. The attributes would have a dependency to their "parent fields" to be triggered if the values change. I don't think validators can access the http filtered value provider to be able to load data. You can check if you can use the same scripting in a validator based on JavaScript, but I don't have high hopes.

You could try to do the validators in Java as described in Maybe you have more capabilities there.

Your answer

Register or to post your answer.