Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System and Method for Replaying the Authoring Process of a Business Intelligence Report

IP.com Disclosure Number: IPCOM000237595D
Publication Date: 2014-Jun-26
Document File: 6 page(s) / 96K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention provides a method to replay the process of authoring a BI report. This invention purposes a way to modeling the report spec, with our modeling method and system the report spec can be replayed and it also support to differ and merge.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 6

System and Method for Replaying the Authoring Process of a Business Intelligence Report

In BI reporting product, user is able to author a report layout in report studio, and save the authored report as report spec which is an XML file. BI reporting product can parse this report spec to generate report in different formats.

The authored layout spec can be complex, in that scenario, users have no idea about how that report authored, especially in the step to create that layout spec. And when different users edited the same layout spec, it also cannot be differed and merged.

Problem definition

The processes/steps of authoring report cannot be replayed. If the processes can be replayed, it could be very useful in some cases, such as users can learn how this report authored

This invention purposed a way to modeling the report spec, with our modeling method and system the report spec can be replayed and it also support to differ and merge.

This invention uses the UML as atom operation modeling method, and when users interact with UI to author the spec, system regard this report creation as a sequence operation against the layout objects, then put all the atom operations into a queue. And when replaying it, the operation in queue can be popped, by parsing that operation and displaying the changes in UI. When merging different version of spec, it just compare with the object operation in queue and do that merge.

Currently report specs formed as XML/JSon file, when user authoring it, it is actually editing the XML/JSon spec. This XML/JSon format benefits us a lot: it provides us a simple way to construct the tree structure, and it is easy to read and parse. BUTthere is a drawback for this format: it loses information, such as user operation sequences.

1



Pa...