The process has recovered from development. This is a concern for auditing since this change is not tracked under 'Change Tracking' section. The documentation is also updated. Could you please help here.
Please let me know if you need further information.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Also, for me it's not very clear what's the issue here:
Is the issue that the deletion of a process was not picked up, or the recovery from development of the process?
Is it affecting a single process or several processes?
Is this a one time issue? Apart from that change, is Change Tracking working?
When instances are in the IBM Cloud, Pulse needs to rely on the TM1 REST API to track the changes, which sometimes doesn't respond in time for Pulse to register the changes. When it's not in the IBM Cloud, it's the Pulse Monitor who tracks the changes, which we can't deploy on the IBM Cloud.
Hastings Direct is the customer and wants the query answered asap. They do not want the process recovered but want to understand why this did not show under the Change Tracking area. I think the call will be a quicker resolution of this issue. I will check with the client if they are available tomorrow during your said timings.
Just one thing, the last logs we have are from 16-12-2024 at 15:00 PM. But I think this issue happened later in the evening, am I correct? Anyway, this might be just because of the local hour in the server where Pulse is installed, but just to be sure we got the correct set of logs.
I had a call with the customer about this issue. So, basically, at some point a TM1 developer of their team just deleted a bunch of TI processes that they did not need anymore and he accidentally deleted three processes that were needed. So they just went to Change Tracking to check on this, and apparently Pulse did not pick any of this TI deletions.
The instance is on PA Cloud and according to the client, this deletion of processes was done in a time frame where nothing was going on (it was out of working hours, around 10PM)
I'm aware that sometimes the TM1 REST API doesn't respond in time to Pulse and Pulse then can't track the changes, but is there something we adjust (a parameter on our side or the TM1 side) to make Change Tracking on PA Cloud more reliable?
Hi Elias, The issue did not happen again but the customer needs a possible reason and how it can be avoided. They need to provide feedback to the leadership for audit purposes.