| # Rules (dmcom2170m000) Rules enable you to trigger the dependent events. You can define rules on the combination of source object, source event, target object, and target event. The conditions for source event and the condition for target event is assigned in the Query (dmqry0501m000) session. To process the rule, you must enter a value in at least one field. The field can be Condition on Target Event or Attributes. Processing of Rule if Condition for Target Event is specified: If the Condition for Target Event is provided, the objects to be processed are retrieved from the query condition. The query conditions are defined for the source and target entities of the rule. All the objects retrieved from the query execution undergo a life cycle change. Processing of Rule When an Attribute is specified: If the user provides the attribute, you must provide the default value. If this rule is processed, the system compares the default value with the value specified in Link Attribute Setup. Default Value matches and no records are present in the Link Attributes and Properties session: If the default value specified in Link Attribute Setup and the default value of Rules match and no records are present in the Link Attributes and Properties session, for the specified attribute, in this case, the rule processes all the instances of the target object. Default Value in Link Attribute Setup matches and records are present in the Link Attributes and Properties session: If the default value specified in Link Attribute Setup and the default value of Rules match, the records retrieved from the Link Attributes and Properties session undergo lifecycle change. Default Value in Link Attribute Setup and Rules do not match and records are present in the Link Attributes and Properties session: If the default value specified in the Link Attribute Setup session and the default value specified in the Rules session do not match, a search is carried out in the Link Attributes and Properties session to find the records with the given attribute and default value. The objects that match this criteria are retrieved and undergo lifecycle change. Example: Scenario for Rule Definition: Whenever the revision of the Documents that are created by an employee with a global role are revised, all the child document revisions attached to the main revision must also be revised. You can revise attached child documents if authorizations and the required status are provided to carry out the current action . Define the Owner Object as Doc_Rev and the Owner Event as Revise. The direction is from owner to member. The Member Event is revise and the Member Object is again taken as Doc_Rev. The condition for Owner Event is defined in the respective query object. The query condition for the query is defined as the documents which have global role. Create a Document, Doc-1 and link the document to the child document CDoc-1. The role for these two documents is defined as Global. If you run the run the rule and whenever Doc-1 is revised, the attached child document CDoc-1 is also revised. Related topics Remove Data Locks for Rules (dmcom2280m000) Source Object The source object for which the rules are defined. Source Event The source event for the source object. Condition for Source Event Use the browse arrow to select the condition for the source event. Target Object Use the browse arrow to select the target object. Target Event Use the browse arrow to select the target event. Condition for Target Event Use the browse arrow to select the condition for the target event. Attribute Use the browse arrow to select the attribute. Default Value Displays an option to enter the default value. Note: If the user provides the attribute, the default value must be provided. Execute Rule Executes the rule to carry out the specified action. |