Flow based visualization of business rule processing traces

• US 9,489,642 B2
• Filed: 06/19/2012
• Issued: 11/08/2016
• Est. Priority Date: 06/19/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Paul, Joydeep, Ziegler, Carsten
• Primary Examiner(s): Chad, Aniss
• Assistant Examiner(s): COOK, BRIAN S
• Application Number:
  US13/527,313
• Publication Number:
  US 20130338980A1
• Time in Patent Office: 1,603 Days
• Field of Search: 703/1, 703/2, 703/6, 703/4, 706/52, 717/101, 717/104, 717/106, 717/120, 717/126, 717/135, 171/101, 171/104, 171/106, 171/120, 171/126, 171/135
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

Embodiments relate to systems and methods for visualizing processing traces as a flow diagram. Certain embodiments allow conversion of a text based processing trace, into an intermediate state which can then be projected using a flow diagram. A model transformation engine receives as an input, a trace log and also a pointer to the trace metadata. The model transformation engine uses the metadata information to convert the trace into a format from which a flow diagram can be built. Such an intermediate state could be, for instance, an XML document or a JSON object. Output of the model transformation engine is then fed to renderer, which reads the XML document or JSON object and displays it onto the screen. Embodiments may be particularly suited for visualizing processing traces of business rules in an enterprise system.

Claims

1. A computer-implemented method comprising:

causing a model transformation engine to receive as inputs, a raw processing trace persisted in an encoded format and metadata information from application specific persistence, the metadata information comprising a trace log, an object relationship, and information related to an intermediate result value, and a pointer to metadata;

causing the model transformation engine to use the metadata information to convert the raw trace into an intermediate state output comprising a hierarchical format;

on demand, causing the model transformation engine to provide the intermediate state output to a rendering engine to generate a flow diagram comprising a plurality of nodes enclosing a number indicating a numerical node position in a hierarchy of the object relationship;

causing the flow diagram to be displayed on a screen; and

causing a processing trace text format to be displayed, the processing trace text format organized with indentation depth according to a multi-tier hierarchical structure and including an icon indicating a type of entity in the raw processing trace.

2. A method as in claim 1 wherein the intermediate state output comprises an XML document.

3. A method as in claim 1 wherein the intermediate state output comprises a JavaScript Object Notation (JSON) object.

4. A method as in claim 1 further comprising persisting the intermediate state output to serve as a store for the raw trace.

5. A method as in claim 1 further comprising:

communicating a user input to the model transformation engine; and

in response to the user input, causing the flow transformation engine to generate a revised intermediate state output to the rendering engine to generate a different flow diagram.

6. A method as in claim 5 wherein the different flow diagram comprises a subset of the flow diagram, a more detailed flow diagram, or a less detailed flow diagram.

7. A method as in claim 1 further comprising not persisting the intermediate state output.

8. A method as in claim 1 wherein the processing trace text format is displayed by toggling.

9. A method as in claim 1 wherein the flow diagram is integrated onto the screen as a side panel.

10. A method as in claim 1 wherein the type of entity comprises a function, a ruleset, a rule, a data object, a database lookup, or a loop.

11. A non-transitory computer readable storage medium embodying a computer program for performing a method, said method comprising:

causing a model transformation engine to receive as inputs, a raw processing trace and metadata information from application specific persistence, the metadata information comprising a trace log, an object relationship, and information related to an intermediate result value, and a pointer to metadata;

causing the model transformation engine to use the metadata information to convert the raw trace into an intermediate state output comprising a hierarchical format;

persisting the raw processing trace in an encoded format;

on demand, causing the model transformation engine to provide the intermediate state output to a rendering engine to generate a flow diagram comprising a plurality of nodes enclosing a number indicating a numerical node position in a hierarchy of the object relationship;

causing the flow diagram to be displayed on a screen; and

causing a processing trace text format to be displayed, the processing trace text format organized with indentation depth according to a multi-tier hierarchical structure and including an icon indicating a type of entity in the raw processing trace.

12. A non-transitory computer readable storage medium as in claim 11 wherein the intermediate state output comprises an XML document.

13. A non-transitory computer readable storage medium as in claim 11 wherein the intermediate state output comprises a JavaScript Object Notation (JSON) object.

14. A non-transitory computer readable storage medium as in claim 11 wherein the method further comprises persisting the intermediate state output to serve as a store for the raw trace.

15. A non-transitory computer readable storage medium as in claim 11 wherein the method further comprises:

communicating a user input to the model transformation engine; and

in response to the user input, causing the flow transformation engine to generate a revised intermediate state output to the rendering engine to generate a different flow diagram.

16. A non-transitory computer readable storage medium as in claim 15 wherein the different flow diagram comprises a subset of the flow diagram, a more detailed flow diagram, or a less detailed flow diagram.

17. A non-transitory computer readable storage medium as in claim 11 wherein the method further comprises not persisting the intermediate state output.

18. A non-transitory computer readable storage medium as in claim 11 wherein the processing trace text format is displayed by toggling.

19. A non-transitory computer readable storage medium as in claim 11 wherein the flow diagram is integrated onto the screen as a side panel.

20. A non-transitory computer readable storage medium as in claim 11 wherein the type of entity comprises a function, a ruleset, a rule, a data object, a database lookup, or a loop.