More visibility into TI processes

[JamiseBondi]

We have some TI processes (submissions out of TM1 into SAP) that can take some time to complete (up to around 30 minutes) and while this is running, the user has no idea of the progress of the process that is running. My question is - whats the best tool to present to the end user so that they can monitor what processes are running and so be able to decide on 'clicking on that button' again which would re-run the whole process again.... (because they can't see what's happening behind the scenes... they don't have a TM1top.exe or operations console view)?

Some of these users are in different time zones so the main admin team aren't always available to tell the user what process is running. We use the web (no architect or perspectives for users) - so...

Is the operations console the best tool to publish to the user community?

The other question is: the operations console doesn't tell you which process is running, it's very generic "ProcessExecuteEx" function on State "Run:R(}ElementAttributes_DIMENSIONNAME)-(Cube). This doesn't tell me which process is running so I can look through it and debug it.

Lastly, can I choose to assign certain TI processes to be run as certain users? So TI process A runs as userA, process B runs as userB.... this would help me identify which process is running by seeing which user it's using to run it.

thanks.

[AmbPin]

Hello,
One way you could achieve this is to have a simple cube which you update as your TI processes start, progress and end. You could have a TM1 web sheet pointed at this cube to enable users to see a snapshot of what processes are running and they are progressing.

[Wim Gielis]

Hello,
One way you could achieve this is to have a simple cube which you update as your TI processes start, progress and end. You could have a TM1 web sheet pointed at this cube to enable users to see a snapshot of what processes are running and they are progressing.

Will the users be able to refresh the websheet whilst processes are running ?

[AmbPin]

Will the users be able to refresh the websheet whilst processes are running ?

I see no reason why users who did not start the process would be able to. The user who did start the process may also be able to view from another tab or browser window.

[lotsaram]

Will the users be able to refresh the websheet whilst processes are running ?

I see no reason why users who did not start the process would be able to. The user who did start the process may also be able to view from another tab or browser window.

A TI logging cube is fine for information after processes have completed but not for updates while processes are still running. I think what Wim was getting at is that changes to the base model are only made on the commit for each transaction. So where the transaction wrapper is a TI process then other users will only see the new values in the TI logging/reporting cube when the process completes. The only way around this while keeping the logging in a cube would be to use RunTI and shell out for updates, either using an external scheduler or spawn a new RunTI every couple of thousand records for updates. ASCIIOutput would be no good for a similar reason (unless likewise handled via independent RunTI threads) as the files will be locked until the TI completes. Another solution might be to insert into a relational table and read process status from there.

[AmbPin]

Ah yes I see.
Even having a chore with an about to start and about to finish task at each end wont help because as you say the chore in that case is the transaction wrapper.