Using source control as the basis for creating a migration package is the best way to ensure you have all appropriate changes included in your package. Pulse tracks each change as it occurs so you can easily identify changes by date range and by person.

By default Pulse only stores the name of a dimension and the types of attributes in source control. This default setting is great for dimensions that are updated from external systems but for dimensions that are manually maintained through TM1 or xdi sheets it is recommended that you include the whole dimension in the Pulse…

Defining the pulse security scheme

Pulse can be integrated with TM1 Web to allow the usage of web sheets and cube views to be logged to TM1. To enable this integration you need to follow the steps below.

The following article will show the Administrator of Pulse to set the validation of users’s credentials with CAM Security

The following Document will guide the Pulse Administrator to configure Pulse to work with CAM security. The reader of this document should be familiar with the IBM Cognos TM1,  IBM Cognos BI terminology and should understand the technical implications and settings to achieve CAM security enabled in her/his environment.

The following article describes the steps to set up Excel logging to Pulse with Extend. If you are trying to set up Excel logging to Pulse with the new Excel Add-ins Excel Logger, you need to go to this article:

Pro-active Alerts can be configured in Pulse based on multiple scenarios and triggers. Allowing you to rectify problems BEFORE they become an issue.

Pulse for TM1 enables you to create alerts so you can proactively manage your TM1 server. To create alerts go to Administration –> Alerts, below is a full list of all the alert types that are available: