Changes between Version 2 and Version 6 of Ticket #51


Ignore:
Timestamp:
05/08/12 11:29:12 (7 years ago)
Author:
Garth Braithwaite
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #51

    • Property Severity changed from to Moderate Effort
    • Property Summary changed from Add Query Module Configuration(s) to Indicator Profile definition to Integrate/Associate Query Module Configuration(s) with Indicator Profile Reports
    • Property Version changed from 2.0 to Unknown
    • Property Milestone changed from Enhancement Ideas for Version 2 to Unassigned
  • Ticket #51 – Description

    v2 v6  
    1 Optional: Associate an IP with the backend query dataset configuration.  This is especially nice if the admin and IP struct is changed to a more generic dimension/measure structure to match the IBIS-Q XML struct.
     1Now that we have the saved query function IP Views can have a URL to a  saved query definition that a user can click on while on the IP report page.  The IP editor can either run the query or take the user to the query builder interface page. 
    22
    3 related to ticket #104
     3The reverse is also possible where a query module XML element can be added for any given configuration that contains URL(s) to IP reports.
     4
     5Another benefit is for updating IP View Values from a query.  This works well IF the IP struct is changed to a more generic dimension/measure structure to match the IBIS-Q XML struct.
     6
     7related to ticket #104 (saved query).