This example creates, builds, and publishes business objects for all user-defined tables set up in iMIS Customer Management. It edits one of the business objects, changing display set and prompt entries, and tests the new business object in IQA.
1. From Customers, select > Set up module > General and click Additional Windows.
The Customer Setup window appears.
2. Verify that the Defined Tables list contains the Name_Demo table. This table (included in the demo database) is used in this example.
3. Close the Customer Setup window.
4. From Tools, select User defined tables.
The User defined tables window appears.
5. Click Build All and wait for iMIS to generate business objects.
Eventually the Results field will display a log of the business objects that were built, compiled, and published.
6. Ensure that CsName_Demo is listed in the Results field.
7. From Tools, select Business object designer.
The Document System appears, displaying a list of available business objects.
8. Select the CsName_Demo object and click the Edit icon in the toolbar.
The CsName_Demo object appears.
9. On the Properties tab, in the Properties area, ensure that a Property Name value exists for was added for each column in the Name_Demo table.
10. Add the ID, Spouse, and School_Attended properties to the object's display set, and change the displayed caption for School_Attended property.
□ Click the Display sub-tab, which shows the display set values for each Property Name.
□ In the Property Name area, select the row containing the ID property.
The values shown in the Display sub-tab change to the defined display set values for the ID property.
□ In the Display sub-tab, select both the Automatically Include in Queries? checkbox and the Default Display Property? checkbox.
□ Repeat this process for the Spouse and School_Attended properties.
□ For the School_Attended property only, change the Prompt for Field value from School Attended to Alma Mater.
11. Click Save and wait a moment for your changes to be saved to the business object.
12. Click Compile.
A results window appears, listing any messages and errors for the compile operation.
13. Ensure that the business object compiled without errors and click Close Dialog.
14. Click Publish.
A results window appears, listing any messages and errors for the publish operation.
15. Ensure that the business object published without errors and click Close Dialog.
Note: If you were to go back to Tools > User Defined tables and run Build All again, your changes will be overwritten and lost. The business objects for user defined tables are always completely re-created by that operation.
16. From Tools, select Intelligent query architect and create a new query that uses the CsName_Demo business object as the Query Source.
17. Save the query, then Run it.
The result set for the query appears. Notice that the three columns shown in the query result set match the three properties that you defined for the business object's display set.
18. Modify the query to return only those records that contain non-null values for either Alma Mater or Spouse. Creating an OR evaluation like this requires you to define two separate filter sets.
□ In the IQA window, select Define.
□ On the Filters tab, from the Mode drop-down list, select Advanced.
□ From the Property drop-down list (beneath the Property column header), select Spouse.
□ From the Comparison drop-down list, select Not Empty.
□ Click the Add Line icon.
The filter is added to the filter set.
□ Click Add Filter.
A new filter set is added below the first filter set.
□ From the drop down list at the top of the new filter set (immediately above the Property column header), select Or.
□ In the new filter set, use the same process to add the Alma Mater property, specify a Not Empty comparison value, and click the Add Line icon.
19. Save the query and Run it again.
Notice that the result set for the query now contains only those records that contain values for Alma Mater or Spouse.
Copyright © Advanced Solutions International, Inc. All rights reserved.
Because of licensing, security, and configuration choices, your implementation may differ from what you see described in the documentation.