If possible, I’d like to get hold of example(s) of prompts using a where clause. I’m pulling data from a clinical data warehouse (Oracle7) and would like to expand my basic BO prompt to include diagnostic CATEGORIES, based on (included in) diagnosis TYPE(S).
I think I need to start with something like :-
@Select (RBH Diagnosis\Diagnosis Category) IN @ Prompt(‘Select the Diagnosis Category (from list of values …)’ , ‘A’, {‘Cardiovascular’, ‘Gastrointestinal’, ‘Neurology’}, MULTI, FREE) @Where(@Select(RBH Diagnosis\Diagnosis Type) = ‘Medical Diagnosis’)) …
If ‘Cardiovascular’, ‘Gastrointestinal’ and ‘Neurology’ (categories) represent ‘Medical Diagnosis’ (type); ‘Cardiovascular Surgery’, ‘Gastrointestinal Surgery’, and ‘Neurosurgery’ (categories) represent ‘Surgical Diagnosis’ (type); and ‘Chest Trauma’, ‘Abdominal Trauma’, and ‘Neurotrauma’ (categories) represent ‘Trauma’ (type) … can I extend my syntax so that users are prompted to select “diagnosis type” and then “diagnosis category” according to the TYPE selected?
I’ve been struggling with this for a while and would really appreciate any advice / examples of advanced BO prompts that could be provided.
Thanks & regards,
Gaye Kiefer
Clinical Data Manager
ICF - Royal Brisbane Hospital
When you are using prompts in a query and want to return a list of values for user selection, any manipulation of the LOV data is best handled at the Universe level. Use an existing object or create a new one if this does not suit.
I got a little confused there in the end though. Do you want to choose a category/s based on a selected type/s? or the other way around?
Assuming the former. Object = Select Category. LOV for Category = Select Category, Where Type = prompt user for type.
Sorry to confuse! You correctly assumed that I want to choose a category/s based on the selected type/s. To be honest, I really need “spoon feeding” with my prompt/ SQL at the Universe/Designer level. I’ve successfully used the pretty basic ones from examples given in the manual but haven’t a clue where to start with this one.
I understand your advice to :-
create a “Select Category” object at Universe/Designer level. - to bring back the LOV for Category based on Type …
Select Category, Where Type = prompt user for type
My understanding of what this will do is once the Type is selected, then the user will only see the LOV appropriate for that type.
I have four different Types and many Categories belonging to each Type. eg. Two of these …
Am I pushing the friendship too much to ask you to actually give an example of the syntax required to bring back the appropriate Category LOVs where there’s say just the first two types given above?
Thanks again for your help.
Gaye
Gaye Kiefer
Clinical Data Manager
ICF - Royal Brisbane Hospital
Gaye,
I think you’re talking about Stacking LOV’s. I was trying to get a list of zip codes based on a County entered by the User. Here is a solution that was given to me:
In the Designer module you can do the following.
Go to the properties tab for the object Zip code 2) Click on Edit button in the Associate a list of values 3) Add the prompt condition in the Conditions box as follows
Zipcode equal to "Which country "
Note : use the Type a new prompt
Click on Run
Next time whenever the user lists the lovs for zipcode and refreshes the list he will be prompted for the country code and only those values for that country code chosen will be displayed in the list