Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

3. Creating a New Model

  1. Last updated
  2. Save as PDF
Let's create a model to see how it all hangs together.

Create the Model Using the Oracle Bridge

  • Click Add under the Models table.
  • Enter the Name: "People (Oracle)".
  • Click Save.

New_Bridge_Create.png

While the new model is selected in the table, add Attributes

  • Click Add under the Model Attributes table.
  • Enter the Attribute Name: AR Login.
  • Enter the Attribute Name: Email.
  • Enter the Attribute Name: Full Name.
  • Click Save

Add_Attributes_to_New_Model.png

While the new model is selected in the table, add a Qualification

  • Click Add next to the Qualifications table.
  • Enter the Qualification Name: All
  • Make sure the Result Type is Multiple.
  • Click Save.

 

Add_Qualification_to_New_Model.png
 

Switch to the Mappings Tab

For this test, we're going to retrieve every entry in the target table or view, so we won't create a Qualification Parameter. Let's click on the Mappings tab to start building our mapping.

Create a New Mapping

  • In the 'Select a Model' field, pick the new People (Oracle) Model.
  • Click Add under the Model Mappings table. This mapping will link the abstract model name with a concrete data source.
  • (Mapping) Name: People (Oracle)
  • Bridge Name: (select) Database - Local Oracle
  • For "Structure" enter the name of the database table or view. In our case the Remedy form name is the same as the reporting view name in Oracle:  KS_SAMPLE_People
  • Status: (select) Active
  • Click Save.

Create_the_New_Mapping.png

Once we've created (and selected) the new Mapping, the attributes will appear in the Model Attribute Mappings in red. They're red because they aren't mapped to any data elements in the target database.

Model_Attribute_Mappings.png

Modify Model Attribute Mappings

Double-click on the AR Login row

  • In the Attribute Mapping dialog form, enter this Field Mapping value: <%=field["AR_Login]"%> 
    • Note: Spaces become underscores in Remedy database reporting views.
    • You can use the Add Field button to create the mapping string automatically!

Add_Attributes_to_New_Model_01.png

 

  • Click Save.

Double-click on the Email row

  • In the Attribute Mapping dialog form, enter this Field Mapping value: <%=field["Email"]%>
  • Click Save.

Double-click on the Full Name row

  • In the Attribute Mapping dialog form, enter this Field Mapping value: <%=field["Full_Name"]%>
  • Click Save

Modify Qualification Mapping

The Qualification Mapping that we created ("All") will appear in red in the Qualification Mappings table on the Mappings tab. That's because we need to map it to a real-world Query String.

  • Double-click on the mapping named "All."
  • In the Query field on the Qualification Mapping dialog, enter this qualification:  1=1
  • Click Save.

Modify_Qualification_Mapping.png

 

Your new mapping is now ready to use!