Change tracking on Pulse with Planning Analytics Engine (TM1 V12)

Hi,

We are migrating a customer from PA on Cloud to PA SaaS (V12), I know that Pulse does not have access to the TM1 server logs, so some features like the Process History, Change Tracking and the Process Log do not work with V12.

Do you have any updates or a timeline for when these features, particularly Change Tracking, will be available? Our customer uses the Change Tracking functionality for audit purposes, so we’ll need to recommend a workaround until it is supported in Pulse.

Any additional information or suggestions would be appreciated.

Thank you!
Felipe Bittencourt

I’m working on a v12 project and there is no capability for us developers to query server logs in v12 yet. IBM’s roadmap says Q4 2024 for that (critical…) feature. I don’t know if the code team has a way to see them already but that may explain why it’s not available yet.

IBM’s roadmap:

https://bigblue.aha.io/published/30f7b700d5eb7d18cfdd19c793f4a10d?page=4

3 Likes

Thanks @abonnet for sharing that article!

Hi @fbittencourt! No timeline yet. We will update the release of Pulse as soon as we can successfully connect and retrieve the server logs. For now, it is as per what @abonnet has detailed.

Cheers,

Paul

1 Like

V12 allows the server logs to be sent to any valid logging location (I think logstash is the standard). Are you looking for a server rest endpoint instead?

Hi @rdclapp,

Thanks! Yes, we were aware of that route, though we have not had the chance to explore that yet. But once we have successfully connected, we will publish an article on how to with Pulse.

By the way, which rest end point are you using at the moment?

Cheers!

Paul

Hi @Vincent,

IBM has enabled access to the TM1Server.log through the PAW interface in V12.

I’m following up on this post to see if now we can have the Change Tracking and Process History functionalities in Pulse with V12.

Thank you!
Felipe

Hi @fbittencourt,

Thanks! That looks promising! I can see those server log messages as well!

Though when we checked just now, the documented REST API where it used to go to were still returning empty,

We will check what we can find as well from this. In the meanwhile, if you do have further information on the matter, especially the REST API part, that would be great too! I would recommend to create an enhancement request ticket for this.

Thanks!

Paul

1 Like