<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/dm/admin/ad000496" xml:lang="en">
   <Header>
      <Title>Rules and Attributes</Title>
      <Keyword type="header" order="d1e273820">
         <Level1>Rules and attributes</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>Rules and attributes deal with defining rules for the instances
		of an object. The rule triggers the events for the set of entities that have
		been retrieved from the rule. Each of the events that are triggered can, in
		turn, trigger other dependent events.</Paragraph>
      <Paragraph>This concept was developed to provide the user with a one-point
		provision to trigger dependent events.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Basic concepts of rules and attributes</SectionTitle>
      <Paragraph>Some of the basic concepts of rules and attributes are as
		follows:</Paragraph>
      <Paragraph>Object Data Management facilitates the creation of data in terms
		of objects and the object’ s relation to the other objects.</Paragraph>
      <Paragraph>Some of the entities, such as document revisions, change
		requests, folders, and so on, undergo a lifecycle change.</Paragraph>
      <Paragraph>During the life-cycle change, you cannot trigger the lifecycle
		change of other dependent entities.</Paragraph>
      <Paragraph>You can use rules as one-point provisions to trigger these types
		of dependent events.</Paragraph>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>If a folder is undergoing a lifecycle, change from In-design
		  to Approved. If documents were linked to the folder, which are in In-design
		  status, enabling the user to change the status of the linked documents from In
		  Design to Approved would be useful. Therefore, these documents are also in line
		  with the status of the folder. In these types of scenarios, you can use rules,
		  which, on definition, not only trigger the lifecycle of the calling object, but
		  also the lifecycle events of other dependent entities that are retrieved by the
		  processing of the rule.</Paragraph>
      </ExampleSection>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>Attributes and queries contribute to classifying of objects
		  that must be retrieved by a rule.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Attribute usage to define a rule</SectionTitle>
      <Keyword type="section" order="d1e273854">
         <Level1>Rules and attributes</Level1>
         <Level2>attribute usage</Level2>
      </Keyword>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The rule is to submit only the specified documents created by
		  a role called Manager. In addition, the documents attached as child documents
		  must also be submitted to a predefined vault area.</Paragraph>
         <Paragraph>Create the documents Doc-1, Doc-2, and Doc-3. The role defined
		  in the documents is Manager. Attach the child document revisions to the
		  revisions of these defined documents. <GUIRef href="" role="manual"/> The condition cannot be
		  specified for this rule, because the user wants to submit only Doc-1 and Doc-2.
		  Therefore, the instance of the owner must be defined in an attribute. If
		  multiple instances exist for Owner, you must define these attributes in
		  multiple attributes. Define the instance of Doc-1 and Doc-2 in the attributes.
		  Whenever Doc-1 or Doc-2 is submitted, the child document revisions attached to
		  the document are submitted to the vault area to check the rule associated with
		  these documents.</Paragraph>
         <Paragraph>This case demonstrates the condition that exists for source
		  event only in a rule. The target object and target event do not
		  exist.</Paragraph>
         <Paragraph>The rule defined is to submit all the documents created on a
		  specific date. To realize this, you must define a query, which retrieves
		  documents created on a specific date. Specify the source object as Docs and the
		  source event as Submit .</Paragraph>
         <Paragraph>Define a query for which the query condition is Documents
		  created on 04.08.2002 . All the documents created on the specified date will be
		  retrieved. Now, the rule is executed and submits all the retrieved documents by
		  query.</Paragraph>
      </ExampleSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Authorizations for rules and attributes</SectionTitle>
      <Keyword type="section" order="d1e273877">
         <Level1>Rules and attributes</Level1>
         <Level2>authorizations</Level2>
      </Keyword>
      <Paragraph>The standard ODM authorization mechanism is used to determine
		the actions to be performed by individual users on various rules and attributes
		entities.</Paragraph>
      <TABLE width="100%" border="1" borderstyle="default"
             space-and-orientation="indented-estimated">
         <TBODY noTR="7">
            <TR no="1" isLast="false">
               <TH rowspan="1" colspan="1">Action</TH>
               <TH rowspan="1" colspan="1">Object</TH>
               <TH rowspan="1" colspan="1">Description</TH>
               <TH rowspan="1" colspan="1">Outcome</TH>
            </TR>
            <TR no="2" isLast="false">
               <TD rowspan="1" colspan="1">CREATE_RULE</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Create a business rule</TD>
               <TD rowspan="1" colspan="1">Create a rule, based on query condition or attribute.</TD>
            </TR>
            <TR no="3" isLast="false">
               <TD rowspan="1" colspan="1">DELETE_LOG</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Delete a log for a business rule</TD>
               <TD rowspan="1" colspan="1"/>
            </TR>
            <TR no="4" isLast="false">
               <TD rowspan="1" colspan="1">DELETE_RULE</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Delete a business rule</TD>
               <TD rowspan="1" colspan="1"/>
            </TR>
            <TR no="5" isLast="false">
               <TD rowspan="1" colspan="1">EXECUTE_RULE</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Execute a rule</TD>
               <TD rowspan="1" colspan="1"/>
            </TR>
            <TR no="6" isLast="false">
               <TD rowspan="1" colspan="1">GLOB-RULE</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Action group for rule</TD>
               <TD rowspan="1" colspan="1"/>
            </TR>
            <TR no="7" isLast="true">
               <TD rowspan="1" colspan="1">MODIFY_RULE</TD>
               <TD rowspan="1" colspan="1">RULE</TD>
               <TD rowspan="1" colspan="1">Modify a business rule</TD>
               <TD rowspan="1" colspan="1"/>
            </TR>
         </TBODY>
      </TABLE>
      <Paragraph>The system administrator assigns roles to ERP Enterprise users in
		the <GUIRef href="" role="session">Roles by Employee</GUIRef> session. User roles are
		assigned permissions to perform different operations on different objects,
		using the ODM authorization mechanism. Conditions can be associated with
		permissions to specify that a user role can only perform a specific action on
		an object if a particular condition is fulfilled.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="380" width="646"
                   SRC="images/tr_screen_ad000496_1.png"
                   alt="[...]"/>
      </Figure>
   </GeneralSection>
</ManualTopic>