Hi all,
I am working on a basic service desk application for another department in our organisation which is set to use a custom priority matrix table. I have set up the priority table extending from the dl_matcher table, and the fields on the form. I have also set up source table/matcher tables in a data lookup definition within the app, eg. dept service desk = source, dept priority table = matcher.
When I go to add matcher or setter field definitions, the source table is always empty and not able to be manually edited.
My dev environment is patched to Helsinki latest as of today. I did run in to the issues where the setter field definitions could not be set because the business rule "hide matcher and source fields" issue previously reported and claimed to be fixed in Helsinki. I addressed this and was able to work around it when doing some testing directly in SNOW on Geneva, but since I have moved to the studio, I have this new issue. I had this issue prior to patching from Geneva to Helsinki (upgrade went through over the weekend).
I have attached a screenshot of my Data lookup definition which shows the source and matcher tables (both custom, both within the scope of the application). Second screenshot shows the fault, ie. the missing field.
For noting, if I change the source table to the priority table as well, I do get the source table field populated, so it doesn't seem to be a problem with fields being visible, just the field in the new table I've created.
If anyone has any ideas I would be grateful. I'm pretty sure I'm screwing up something to do with app scopes. Let me know if you want more info. ; )
Cheers,
Grant
Okay, have managed to "solve" this by changing the Data Lookup Definition source table to the same as the matcher table. Field definitions now populate, and since the fields are named the same (u_impact, u_urgency and u_priority respectively), I can create valid definitions. I then went back to the Data lookup definition and changed the source table back to the original table. The rules remained valid and my create new incident form started correctly calculating...
eg. You can see the lower field definitions are correctly matching the service desk table to the priority table. That was done by changing the upper source selection to priority, and then the form started to correctly populate...
Talk about weird... Anyway, that's one way to work around, but this seems to be a bug or an undocumented problem. Is there some easy way to forward this to SNOW for review?
Okay, have managed to "solve" this by changing the Data Lookup Definition source table to the same as the matcher table. Field definitions now populate, and since the fields are named the same (u_impact, u_urgency and u_priority respectively), I can create valid definitions. I then went back to the Data lookup definition and changed the source table back to the original table. The rules remained valid and my create new incident form started correctly calculating...
eg. You can see the lower field definitions are correctly matching the service desk table to the priority table. That was done by changing the upper source selection to priority, and then the form started to correctly populate...
Talk about weird... Anyway, that's one way to work around, but this seems to be a bug or an undocumented problem. Is there some easy way to forward this to SNOW for review?
