#Plantuml online sequence diagram code

Start transaction SAT -> Evaluate -> Double Click on a measurement on the next screen press F8 (Display measurement as UML sequence diagram).Ī sequence diagram will be displayed if the JNet OCX component is installed (e.g.Since SAP Netweaver 7.02, an UML sequence diagram can be generated if the measurement was recorded without aggregation. Measurements can be imported from other SAP systems using either download/upload or RFC. Transaction SAT profiles an ABAP program execution and provides analysis tools for performance, program flow and memory consumption. The link is not accessible and I believe a blog is a stable location for this document. This content was first published 2014 as a SAP wiki.

#Plantuml online sequence diagram code

Code is available at github: Create UML Class and Sequence Diagrams from ABAP Code.Local installation of PlantUML is recommended but not mandatory as a web service is available. the sequence diagram output in PlantUML Format is editable plain text.loop compaction produces smaller diagrams.a custom filter displays calls from standard to custom code.a secondary internal table index speeds up parsing.But for me this would be important: to be able to re-activate lifelines at higher levels without loosing the stacked view.Some shortcomings of the SAP standard sequence diagram generation from ABAP run-time measurements are addressed: For me, this looks like a bug, although I guess there are not many people trying something like this. I would like to be able to create lifelines visibly stacked as seen in (1) even when I create three 'activations' in subsequent text rows. It can be seen, that all lifelines are displayed even more on the right of the middle line and all directly above each other. The 3rd marker (3) now shows the same as seen before, just with three subsequent 'activate actor1' text rows. The 2nd marker (2) shows that when returning from actor5 back to actor1 the double 'activate actor1' from the text sequence results in only one visible lifeline, placed right of the middle line. The 1st marker (1) shows how it was intended to look like: the first lifeline is created below action1 and then overlayed by another, short lifeline, which is then deactivated and re-activated again. Looking at the diagram above, you see three markers.

'actor 1' -> 'actor 1': actor1 following image shows the result: 'actor 1' -> 'actor 1': actor1 sub-activity4 'actor 1' -> 'actor 1': actor1 sub-sub-activity1 'actor1_func1()' -> 'actor1_func1()': actor1 func1 activity1 actor1 func1 activity2 'actor 1' -> 'actor 1': actor1 sub-summary1 'actor 5' -> 'actor 5': general func sub-activity1 'actor 5' -> 'actor 5': general func activity1 general func activity2 'actor 1' -> 'actor 1': actor1 sub-activity2 actor1 sub-activit圓 'actor 1' -> 'actor 1': actor1 activity2 actor1 summary1 'actor 1' -> 'actor 1': actor1 sub-activity1 The principle is shown by the following PlantUML sequence: 1 Now, when I jump between actors, I want to activate, deactivate and re-activate lifelines within the respective actors.

And even show a representation of 'indentation levels' according to the inner code structure where the activity / message stems from. Within my sequence diagram I try to represent active calculations within actors by drawing lifelines. PlantUML's sequence diagrams provide a mechanism to stack these lifelines for each actor and even colorize them. In order to show ongoing operations of 'activities' or 'messages' within actors, lifelines can be used.