You have defined a new reportable object, attributes of that object, and how you can connect this object with other objects. You are now ready to use it in the report wizard.
Let’s say that you want to configure the wizard so that when the user reports on “Entities” and focuses on “Archived Assessments,” they can use the newly-created reportable object. Assuming that only these customizations are in the ReportWizardOptions.xml, the file content would look like this:
<?xml version="1.0" encoding="utf-8"?>
<ReportWizardOptions>
<ReportOnMappings>
<Mapping name="Entity" displayname="Entities (Any type)"/>
</ReportOnMappings>
<ReportFocusMappings>
<Mapping name="ArchivedAssessments" displayname="Archived Assessment"/>
</ReportFocusMappings>
<ReportOptions on="Entity" focus="ArchivedAssessments">
<AttributeGroup name="Entity"/>
<AttributeGroup name="ArchivedAssessments"/>
</ReportOptions>
</ReportWizardOptions>
From the above example, you can see that you have defined a report on "Entity" and report focus "ArchivedAssessments" (notice that the display names shown in the user interface are different). For a combination of "report on" and "report focus," you have defined the report attributes from groups "Entity" (available by default) and "ArchivedAssessment" (defined by ), based on the newly-created reportable object. Users can choose attributes from either group. Since you have defined the join condition between agl_entity and aglv_archived_assessments, the server can use that information to create an SQL query joining the two tables and return columns from both the tables.
The report on "Entity" is already defined in the default ReportWizardOptions.xml, so it does not need to be defined here. The content of the custom ReportWizardOptions.xml could be:
<?xml version="1.0" encoding="utf-8"?>
<ReportWizardOptions>
<ReportFocusMappings>
<Mapping name="ArchivedAssessments" displayname="Archived Assessment"/>
</ReportFocusMappings>
<ReportOptions on="Entity" focus="ArchivedAssessments">
<AttributeGroup name="Entity"/>
<AttributeGroup name="ArchivedAssessments"/>
</ReportOptions>
</ReportWizardOptions>
Note that ReportOnMapping has been removed.
The new options will show up in the chart wizard after you have put this together, deploy the files in the %AGILIANCE_HOME%\config directory, and restart the server.
In the available attributes area, you can see the attributes defined under the Archived Assessment section. You can also see a lot of other attributes. This is because you included the Entity group in the Report Options section of ReportWizardOptions.xml.
While building the ad-hoc filters in the advanced settings step, you can use all of these columns to build the filters.
