Context Q?

hpl123

Hi all,
I am trying to understand the AIM context feature and was wondering if it is possible to create a BO (instance) that functions in the same way as "SystemSettings" so the instance IS ALWAYS in the context? and thereby always being available to rules etc.? I am trying to create a custom "SystemSettings", a "Settings" BO that all users have their own instance of (containing application settings etc.)

Also, is it the case that one has to always make sure an instance of a BO is in the context (found e.g. though a FIND action) if one wants to use it / an attribute from it in a rule?

hpl123

Another related question. When it comes to the "Process Input" option, is this what i think it is, basically a feature to add a BO to the context before running process actions?

hpl123

hpl123 wrote
Another related question. When it comes to the "Process Input" option, is this what i think it is, basically a feature to add a BO to the context before running process actions?

I tried adding a BO to the "Process Input" option but when i ran the process, if the BO i used in the "Process Input" had more that 1 instance; Aware IM asked me which instance to use??

tford

. . . a "Settings" BO that all users have their own instance of (containing application settings etc.)

You can use LoggedInRegularUser attributes

hpl123

tford wrote
You can use LoggedInRegularUser attributes

I have come across this "code" ("LoggedIn") a couple of times in the "code assistant" when working with rules but don´t fully understand how it works. Is it simple a way to write a rule for/about BO´s etc. of the currently logged in user?
I experimented with "LoggedInSystemUser" followed by the path to a BO/attribute, but had some issues getting it to work..

aware_support

"LoggedIn" is the prefix that identifies currently logged in user. You can use LoggedInSystemUser or LoggedInRegularUser or any other object in the SystemUser group. It is one of the most frequently used prefixes and there are no problems with it.

LoggedIn user is always available in the context.

hpl123

Thanks, got it to work. Hadn´t used it properly before.