Parameters for IDM document output reports

The component list parameters that you specify for an IDM document output report represent the data that you want to include in your report.

For example, to include the service request number in a service request report, you would select ServiceRequest.ServiceRequestNumber as the component ID.

Collections

To add a collection to your report, browse to the collection property, then drill down to the properties that you want to use under the SearchItem node. For example, to show the comments for each log entry associated with a service request, you would specify ServiceRequest.Logs.SearchItem.Comments.

Asset properties

If you want to use an asset property for a component list parameter, you might find that the property you want is not shown in the list of object properties. This is because the generic IAsset interface is used to access asset properties rather than the specific interface for the asset type, such as IStreetSegment.

For example, the cross streets of a street segment are properties of the StreetSegment object. If you want to include these properties in a work order report, you will not see them in the object property list.

As a workaround, you can add a parameter for one of the available properties and then edit the parameter in the Reports configuration. Follow these steps:

  1. Add a component list parameter for an asset property, such as WorkOrder.Asset.Detail.ID. This is not the actual property that you will use. It serves as a placeholder so you can add the parameter.
  2. Open the Reports configuration in the Configuration Editor and browse to the parameter that you added. The parameter node is a child of the report node.
  3. Change the value of the Component ID attribute to the correct property, such as WorkOrder.Asset.Detail.BeginCrossStreet.ID.

Detail pages

Use the Alternate Business Object column to include properties of detail pages. Normally the component ID is a property of the parent page's business object, but you can specify a different object in the Alternate Business Object column. In that case the component ID will be a property of the specified object. You must also use the Alternate Business Object Parent Bind column to indicate how the alternate business object is linked to the page's object.

For example, suppose you have an agency business object for building applications called BldgDtl in a family called BldgDtls. In that case the alternate business object would be InforClient.BldgDtls.BldgDtl, and the parent bind to a page such as the Application InfoViewer would be BuildingApplication.ApplicationDetails.