Sep 2, 2016

Documentation a necessary evil

Documentation is a long and costly task that is often ignored for more “interesting” tasks by developers and administrators alike. Pulse for TM1 automates much of this process by doing all of the tedious tasks for you. 


Documentation is often large with lots of pages, it’s a pain to find the information you’re looking for.

With Pulse you look only to what you precisely want to understand. For example if you want to understand how the General Ledger cube is updated, just ask Pulse and it will generate the data flow diagram for you:

Quickly find non-valid rules:

When saving the rule, TM1 checks for errors. If a cube used in a DB function is deleted after saving the rule, you won’t get any errors from TM1 but the rule will not be valid.

Pulse can help you to find all the cubes which have been deleted but are still in rules or processes. In the example below, the Flow Diagram shows us that the Wholesale cube is still in the General Ledger rule whereas it does not exist anymore:

The Flow Diagram shows in yellow all objects which don’t exist anymore but are still used in rules or processes.

Documentation in pulse is dynamic:

Pulse does the documentation for you, the beauty of it, is that it is dynamic. Pulse keeps track of the changes, when you ask Pulse, it shows you how your application really is and not how it was when the documentation was created.

Pulse gives you the confidence to improve your model

Having current documentation and the ability to view a TM1 model visually via relationship diagrams also means your team can feel confident changing the system knowing all possible impacts. On boarding also becomes a much easier process, no longer will you have a single point of dependency with all of the knowledge in one person’s head.

Related content

Loading related content