How to check (in a Rule) if a Scheduler job is running?

[Jaymer]

If I have a rule that says "Don't do this if LIRU.AccessLevel='Janitor' "
How do I also exclude that rule when being run by a timed schedule process.

There is no concept of LIRU in that case, yet I need to add some condition to keep a rule from firing.

[PointsWell]

This is not an answer but may send you in the direction of one.

When you use PROTECT and READ PROTECT you are able to exclude or include SYSTEM as an option, is there a way to identify that SYSTEM is invoking the rule?

[rocketman]

I have several scheduled email reminders that go out overnight and have set up some SystemSettings yes/no attributes that an admin can switch on or off at will

So the scheduled event starts with IF SystemSettings.SomeAttribute= 'Yes' AND [all the date/time parameters hold true] THEN

[BobK]

If I have a rule that says "Don't do this if LIRU.AccessLevel='Janitor' "
How do I also exclude that rule when being run by a timed schedule process.

There is no concept of LIRU in that case, yet I need to add some condition to keep a rule from firing.

There is a LIRU for the system. It might be limited, but you can do the following:
if LoggedInRegularUser.AccessLevel='System'

[Jaymer]

There is a LIRU for the system. It might be limited, but you can do the following:
if LoggedInRegularUser.AccessLevel='System'

BobK - perfect !!!!!
thats exactly what I was needing.

Added that to many rules to keep them from running when not needed. Thanks so much!

[gernotlg]

BTW... you should use ...

Code: Select all

LoggedInSystemUser.AccessLevel = 'System'

Because if you have other userBO's (for eg. ClientUser) then LoggedInRegularUser wont work if you have a LoggedInClientUser

[BobK]

BTW... you should use ...

Code: Select all

LoggedInSystemUser.AccessLevel = 'System'

Because if you have other userBO's (for eg. ClientUser) then LoggedInRegularUser wont work if you have a LoggedInClientUser

You can certainly use LoggedInSystemUser.AccessLevel and that might even be the better option. But, I would guess that a process running from the scheduler would use the default user (RegularUser) instead of some other BO the system admin added to the SystemUser group.