Security Access for TI Process

[bradohare]

Hi,

I recently received an error when one of my TI processes tried to update a security cube without the "Security Access" set. This led me to updating the process and the it worked as expected.

One thing I did note, is that upon updating this setting the actual timestamp on the server for the TI process did not update. This would lead me to believe that if I was to migrate this process to another instance/server, the setting would not persist. Though it doesn't make sense to me to have this setting cached somewhere. Is the solution as simple as simply just editing/resaving the process?

Does anyone have any additional knowledge how the internals of TM1 work with regard to this?

thanks
brad

[bagovino]

It looks like it changes the Security Access setting on the Process object loaded into memory on the server and then that change is only made permanent when a Save Data is run. This can be tested by changing the Security Access setting on a Process in Perspectives or Architect and then looking at the data directory for the server on the hard disk. There should be no change to the Process file. If you then run a save data for that server after it finishes executing you should see that the Process file has been updated.

[lotsaram]

To be more precise "run with security admin access" is property 1217. A value of 1 (true) in the .pro file indicates that the process will run with security access.

Normally process properties in the .pro file are updated when a process is saved but the save to disk is not triggered by the right click and needs either a save data, server shutdown or subsequent editing of the process to be saved from memory to disk.