security overlay - what am I doing wrong

[Wim Gielis]

Further testing:
• a chore that runs a TI process can write without issue, when the chore runs on a schedule
• a chore that runs a TI process, when the chore is run by a particular user, will run with the security rights of that user

So you can you summarize:
- what do you see in your environment?
- is it equal to what I have documented?
- if needed, challenge IBM with the observations I/you made. When they say that all TIs run regardless of security overlays, that is not true. Remark: I tested in TM1 Architect and server 2.0.9.21 or so.

Best regards,

Wim

[stingo]

Further testing:
• a chore that runs a TI process can write without issue, when the chore runs on a schedule
• a chore that runs a TI process, when the chore is run by a particular user, will run with the security rights of that user

So you can you summarize:
- what do you see in your environment?
- is it equal to what I have documented?
- if needed, challenge IBM with the observations I/you made. When they say that all TIs run regardless of security overlays, that is not true. Remark: I tested in TM1 Architect and server 2.0.9.21 or so.

Best regards,

Wim

I have a process that writes a cell that is "overlayed".
we know the behaviour if we run manually that process.

Now if we put that process in a chore and schedule it, the process will run as an admin.

so the only benefit of the overlay is to prevent random users to run a process on a closed month.

I tested it just like that. I created a cellPut in a process
scheduled it for 5 mins later.
checked the result.

[Wim Gielis]

Correct. Chores should run from static cube values. They will not be stopped in case someone puts in a wrong value. That’s a responsibility for users. At least the manual runs are protected. If you want to have chores protected than take out the time to add validation code in the Prolog tabs.