CLRT-60305: Parameterized Lookup values do not appear on the List View when the Lookup definition contains an embedded UNION statement

Transcription

1 CLRT-60305: Parameterized Lookup values do not appear on the List View when the Lookup definition contains an embedded UNION statement Document Revision #1 restarting services or flushing caches shows the real outcome of using the UNION statement This example uses Object Instances. The customer wants to be able to add an attribute to an Investment Object this example will use the Application Object for selecting an Activity. Once the Activity value is selected, a second attribute (that is the parameterized lookup) will be filtered based on the selected Activity value to show only the appropriate Phase for that activity. Typically, the parameterized lookup example will have a one parent to- many children relationship. For example, you could have a list of Phases and for each specific Phase, you have many Activities. So, typically the first attribute will allow the user to select the Phase and then the second attribute, a parameterized lookup, will show a filtered list of Activity values related to the value selected on the first attribute. This example reverses the fields, because the desired behavior is that the end-user should select an Activity first and then the second attribute, for the parameterized lookup will return the appropriate Phase value. The parameterized lookup definition for the Phase shall have an embedded UNION statement so that there is built-in logic to cover the following scenarios: 1. Activity value is selected and the Phase value on the Activity record matches existing Phases 2. Activity value is NOT selected ; offer the end-user the option to select None for the Phase 3. Activity value is selected, but the Phase value on the Activity record is not filled in but we want to offer the enduser the option to select Unknown Phase value. SETUP & TEST #1 Lookup Query using Union Statement with Alias Values 1. Login as a Clarity Administrator 2. Admin Tool > Objects: Create an Object named Phase / Object id = myphase 3. A new table will be created for this object named ODF_CA_MYPHASE

2 4. Use the default attributes for name and code (and optionally add a Description field) 5. Main Application > see link in navigation menu for Phase List 6. Enter instance data 7. Admin Tool > Objects: Create an Object named Activity / Object id = myactivity 8. A new table will be created for this object named ODF_CA_MYACTIVITY

3 9. Use the default attributes for the name and code

4 10. On this object, create a new attribute > Activity Object > Views a. Attribute Name = Phase b. Attribute id = phase_lookup c. Data Type = Lookup type d. Lookup = Phase Instances (this lookup is automatically created when the Phase Object was created) 11. On this object, add the new Phase lookup attribute : Activity Object > Views > Properties: [Layout:Edit]

5 12. On this object, add the new Phase attribute to the List view too: Acitivity List *Layout+ 13. Main Application > see link in navigation menu for Activity List 14. Enter instance data be sure to add a few Activity records with NO Phase indicated

6 15. Create the Parameterized Lookup for the Phase based on what is selected from the Activity

7 16. Enter the following Query #1 in this parameterized lookup definition: Both the Activity and the Phase IDs can be found in the Activity table. The parameter that we want to pass is the hidden key from the Activity Instances Lookup (this will be the code field). This NSQL Lookup Statement is constructed with a UNION statement so that we can ensure all 3 scenarios are covered based on the selections by the end-user. This statement uses alias values to cover missing values. FROM ( SELECT activity.code ACTIVITY_CODE, 'no_phase' CODE, 'No Phase' NAME FROM ODF_CA_MYACTIVITY activity WHERE activity.phase_lookup IS NULL = activity.code UNION SELECT activity.code ACTIVITY_CODE, phase.code CODE, phase.name NAME FROM ODF_CA_MYPHASE phase, ODF_CA_MYACTIVITY activity WHERE activity.phase_lookup IS NOT NULL AND activity.phase_lookup = phase.code = activity.code UNION SELECT NULL, 'no_activity' CODE, 'No Activity' NAME FROM DUAL IS NULL ) phase 17. FLUSH THE CACHES OR RESTART SERVICES FOR THE MODIFIED QUERY TO TAKE EFFECT 18. Admin Tool > Objects: Application Object > Attributes --- add an attribute for the Activity. This is the APPLICATION attribute where instance data is stored for the activity selected on the investment. Note: This configuration can be used for any investment type; I am using Application Object for this use-case.

8 19. Now add the second attribute on the Object for the Phase. This is the object attribute where the instance data is stored for the phase selected on the investment. This attribute will use the parameterized lookup you defined in an earlier step. First, create the attribute, save and the parameterized option will show up for you to select the correct linking attribute. Pick the Activity attribute id you created in the previous step.

9 20. Add the two attributes to the object [Layout:Edit] 21. Add the two attributes to the object List View [Options] layout 22. Now try it out! Main Application > Applications > Edit existing investment > Select an Activity and see the appropriate Phase appear!

10

11 23. Don t select an Activity Value Note that there is a value available for selection on the Phase. Select this value and click Submit button. The value is saved and when you return to this properties page, the value appears. 24. Go to another investment. Select an Activity value that does not have a Phase value (see previous steps Look at Activity IV for example Note that there is a value available for selection on the Phase. Select this value and click button. The value is saved and when you return to this properties page, the value appears.

12 25. Go to the Applications List View. Although you can go into each investment and see the selected, saved value for the Phase on the properties page, the value does NOT show up here. Display is incorrect. Display should show values for all 5 investments. 26. Go into [--Actions--] Edit Mode. The functionality works as expected. The end-user is able to select the same values for the 3 scenarios as what is presented on the investment properties page. The values can be saved, but once the Save button is clicked, the saved value is not displaying in Edit Mode or Display Mode. The screenshot below shows that the correct values can be selected in Edit Mode this screenshot is taken BEFORE clicking the Save button

13 Clicking the Save button, now the values disappeared 27. Going back to each investment properties page, you can see the value is there.

14

15 TEST #2 Modified Lookup Query ; Using Table values ; not alias ; gives same results 1. Go to the Parameterized Lookup Query Definition and copy the following query to replace the existing query defined from step #16 in the first test. FROM ( SELECT activity.code ACTIVITY_CODE, phase.code CODE, phase.name NAME FROM ODF_CA_MYACTIVITY activity, ODF_CA_MYPHASE phase WHERE activity.phase_lookup IS NULL = activity.code AND phase.code = 'unknown_phase' UNION SELECT activity.code ACTIVITY_CODE, phase.code CODE, phase.name NAME FROM ODF_CA_MYPHASE phase, ODF_CA_MYACTIVITY activity WHERE activity.phase_lookup IS NOT NULL AND activity.phase_lookup = phase.code = activity.code UNION SELECT NULL, phase.code CODE, phase.name NAME FROM ODF_CA_MYPHASE phase WHERE phase.code = 'None' IS NULL ) phase 2. Once you have modified this query, go back and perform the same steps outlined in TEST #1 for the 3 different scenarios you will see the outcome is the same. The List View is not displaying the values for 2 of the 3 scenarios. 3. FLUSH THE CACHES OR RESTART SERVICES FOR THE MODIFIED QUERY TO TAKE EFFECT 4. Screenshots for TEST #2

16

17

18 Display is incorrect. Display should show values for all 5 investments.

19 TEST #3 Modified Lookup Query ; Simple SQL Statement (NO UNION) 1. Go to the Parameterized Lookup Query Definition and copy the following query to replace the existing query defined from step #16 in the first test. This query does not have a UNION Statement. FROM ( SELECT activity.code ACTIVITY_CODE, phase.code CODE, phase.name NAME FROM ODF_CA_MYPHASE phase, ODF_CA_MYACTIVITY activity WHERE activity.phase_lookup = phase.code AND (@WHERE:PARAM:USER_DEF:STRING:parm_activity@ = activity.code IS NULL ) ) phase 2. Once you have modified this query, go back and perform the same steps outlined in TEST #1 and TEST #2 for the 3 different scenarios you will see the values will show in the list view. 3. FLUSH THE CACHES OR RESTART SERVICES FOR THE MODIFIED QUERY TO TAKE EFFECT 4. Screenshots for TEST #3 Display is correct. There are no values for investment #4, #5 because of the lookup definition design.