Hello,
i am a beginner with AwareIM and was exploring the basic concept of AwareIm. I miss the possibility of assigning user defined variables (Strings, integer, etc...) for using them within processes during the execution of rules.
Didn't i only find it? or is there a workaround.
What concept exist for such a request
Regards
Peter
UserDefined Variables
Peter,
You can store variables in the attributes of either RegularUser or SystemSettings and they will always be in context and able to be used in processes.
RegularUser would be used for variables that are user specific while SystemSettings would be used for variables that apply to all users.
To refer to a RegularUser atttribute in a process rule, the format is: LoggedInRegularUser.AttributeName.
Tom
You can store variables in the attributes of either RegularUser or SystemSettings and they will always be in context and able to be used in processes.
RegularUser would be used for variables that are user specific while SystemSettings would be used for variables that apply to all users.
To refer to a RegularUser atttribute in a process rule, the format is: LoggedInRegularUser.AttributeName.
Tom
Tom - V8.8 build 3137 - MySql / PostGres
Hi Tom,
I need the same feature and tried your solution. So in a process I do the following:
LoggedInRegularUser.CurrentObject=Nieuwsbrieven.ID
When I run this I get the following error message:
-Unable to find business objects to modify attribute RegularUser.CurrentObject
From your previous post I understood that the RegularUser object is always in context. Am I missing something?
I need the same feature and tried your solution. So in a process I do the following:
LoggedInRegularUser.CurrentObject=Nieuwsbrieven.ID
When I run this I get the following error message:
-Unable to find business objects to modify attribute RegularUser.CurrentObject
From your previous post I understood that the RegularUser object is always in context. Am I missing something?
Gert (running V8.0 build 2378 on Windows Server 2008)
Hi Tom,
With pleasure. I need to send newsletters to two different BO's, one is Members, the other Friends. On the newsletter form I created a button that calls a procedure SendNewsletters.
This procedure does the following:
LoggedInRegularUser.CurrentObject=Newsletter.ID
(whereby CurrentObject is a numeric field in RegularUser)
SendNewsletterToMember
SendNewsletterToFriend
(The latter are two procedures that handle the sending of the Newsletter to the two different BO's. They have been tested and work)
Just running this gives me the error -Unable to find business objects to modify attribute RegularUser.CurrentObject the moment the procedure starts. It looks to me that this means that LoggedInRegularUser is therefor not in the context.
With pleasure. I need to send newsletters to two different BO's, one is Members, the other Friends. On the newsletter form I created a button that calls a procedure SendNewsletters.
This procedure does the following:
LoggedInRegularUser.CurrentObject=Newsletter.ID
(whereby CurrentObject is a numeric field in RegularUser)
SendNewsletterToMember
SendNewsletterToFriend
(The latter are two procedures that handle the sending of the Newsletter to the two different BO's. They have been tested and work)
Just running this gives me the error -Unable to find business objects to modify attribute RegularUser.CurrentObject the moment the procedure starts. It looks to me that this means that LoggedInRegularUser is therefor not in the context.
Gert (running V8.0 build 2378 on Windows Server 2008)
Hi Tom,
With pleasure. I need to send newsletters to two different BO's, one is Members, the other Friends. On the newsletter form I created a button that calls a procedure SendNewsletters.
This procedure does the following:
LoggedInRegularUser.CurrentObject=Newsletter.ID
(whereby CurrentObject is a numeric field in RegularUser)
SendNewsletterToMember
SendNewsletterToFriend
(The latter are two procedures that handle the sending of the Newsletter to the two different BO's. They have been tested and work)
Just running this gives me the error -Unable to find business objects to modify attribute RegularUser.CurrentObject the moment the procedure starts. It looks to me that this means that LoggedInRegularUser is therefor not in the context.
With pleasure. I need to send newsletters to two different BO's, one is Members, the other Friends. On the newsletter form I created a button that calls a procedure SendNewsletters.
This procedure does the following:
LoggedInRegularUser.CurrentObject=Newsletter.ID
(whereby CurrentObject is a numeric field in RegularUser)
SendNewsletterToMember
SendNewsletterToFriend
(The latter are two procedures that handle the sending of the Newsletter to the two different BO's. They have been tested and work)
Just running this gives me the error -Unable to find business objects to modify attribute RegularUser.CurrentObject the moment the procedure starts. It looks to me that this means that LoggedInRegularUser is therefor not in the context.
Gert (running V8.0 build 2378 on Windows Server 2008)
Bob, Tom and others suffering with this,
I found out the following:
My business object group SystemUser had to BO's underneath: RegularUser and Members.
I got the error when I logged in as a member, however when I logged in as admin it worked. If you do the following it works in all cases.
Define a field say ChosenNewsletter in Members and when you save it, make sure AwareIm updates the other BO's in the group as well. Now, in my case,I needed to save the Newsletter I was working on, so I defined the following rule:
LoggedInSystemUser.ChosenNewsletter=Newsletter.ID
This will work for both admin and a member that is logged in.
Credits go to Tom, without whom I would not have been able to figure this out.
I found out the following:
My business object group SystemUser had to BO's underneath: RegularUser and Members.
I got the error when I logged in as a member, however when I logged in as admin it worked. If you do the following it works in all cases.
Define a field say ChosenNewsletter in Members and when you save it, make sure AwareIm updates the other BO's in the group as well. Now, in my case,I needed to save the Newsletter I was working on, so I defined the following rule:
LoggedInSystemUser.ChosenNewsletter=Newsletter.ID
This will work for both admin and a member that is logged in.
Credits go to Tom, without whom I would not have been able to figure this out.
Gert (running V8.0 build 2378 on Windows Server 2008)