StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10208564
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-18T11:38:45.620
FavoriteCount
0
LastActivityDate
2012-04-18T11:38:45.620
LastEditDate
LastEditorUserId
0
OwnerUserId
1213763
ParentId
9695354
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Automatic variables are there for you to access the working memory object directly via the verbalization. It based on the usage you want to use :) there is no better way than an other. if you want to populate the working memory and let the engine deal with the manipulation then you can use automatic variables If you want to control everything then use rule variable (pre conditions - starting with "definitions") It can depend on how business users want to create/author rules, as well The doc says: Because objects in the working memory cannot be named or verbalized, you must bind them to rule variables or automatic variables by defining a pattern in the definitions of the rule artifact to manipulate them – At run time the rule engine cycles through all the objects in working memory to find objects that match the definition of the rule variable – The rule engine creates a separate rule instance for every match, which works on the object that caused that particular rule instance to be created • You can also use rule variables simply to enhance the way your rules are written – For example to reduce the length of your conditions or your actions when you author rules, or to define a constant used in the rule I have been using JRules for years and it all depends on the design you want to implement. As a JRules instructor, I would say: Pick up what you prefer but personnally I don't use them. Except quick POCs. Hope it helps
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POwhat would be the purpose of Automatic Variable in ILOG Jrules?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDamien
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.