vb.net 128 barcode generator BUSINESS RULES FRAMEWORK in C#

Creation PDF 417 in C# BUSINESS RULES FRAMEWORK

Figure 7 7. New vocabulary based on an XML Document Element Age d. 5. In the Select Operation section, select the Perform Get Operation radio button.

Add a reference to the Role node in the NewHire XML document. Following the same procedure as defined in step 4, use these substeps:

Select the XML Document Element or Attribute option, and click Next. Enter ApplicantRole for the Definition Name field. Give a description of the role of the applicant, which will be set to INVALID APPLICANT. Click the Browse button, and find the NewHire XSD schema. Once you have selected the schema, a new dialog box appears where you can select the Role node. Select this node, and click OK. In the Select Operation section, select the Perform Set Operation radio button. See Figure 7 8.

Figure 7 8. New vocabulary based on an XML Document Element Role e. Click Next. On the final screen of the wizard, two steps are shown. For the first step, click the Edit button and set INVALID APPLICANT as the constant value. For the second step, keep the default values. Click Finish when this is complete. See Figure 7 9.

Figure 7 9. Setting the values on the final page of the wizard 6. Now, publish the vocabulary by right-clicking the newly created AgeValidation folder and selecting Publish. This allows the vocabulary to be used by a policy, which is where you define an actual business rule.

The steps up to this point have been putting into place the components needed to create a business rule. A rule (or set of rules) is defined within a policy and references preexisting functions, predicates, and any custom-defined constants (such as what you defined in the previous steps). The following steps show how to create the actual business rule and policy and use the vocabulary created previously: 1. 2. 3. In the Policy Explorer, right-click the Policies folder, and select Add New Policy. Enter SamplePolicy for the policy name. A version appears. Right-click this version, and select Add New Rule. Enter SampleRule for the rule name. Select the rule you created in the previous step. You will see an empty condition in the right pane. Take the following steps to create the rule (see Figure 7 10 for a full picture of the completed steps).

In the Facts Explorer, expand the Predicates folder, and select the Less Than predicate. Drag and drop this on the rule condition. On the argument1 entry in the IF section of the rule composition window, drag and drop the custom vocabulary parameter ApplicantAge you created in an earlier step. On the argument2 entry in the IF section, drag and drop the custom vocabulary parameter MinimumAge you created earlier. In the THEN section of the rule composition window, drop the ApplicantRole parameter (created earlier).

Figure 7 10. Creating the rule The rule is complete at this point. Save the rule (right-click Version, and select Save). You can now test the rule (and policy). Use these steps to validate and test the rule: 1. 2. Right-click the Version folder of the rule you just created, and select Test Policy. In the Select Facts dialog box that appears, click the schema name. The option to add an instance of the NewHireList XML will be available. You saw an example of this earlier in this recipe (refer to Listing 7 2). Click Add Instance, and browse to an instance of this XML document. Once you have declared an instance, click the Test button. This causes the XML instance to be passed to the rule. A full trace appears in an Output window where you can verify whether the rule executed as expected (the value of the XML node should change). Right-click the policy version, and select Publish. Right-click the policy version, and select Deploy.

4. 5.

You can now call the rule and policy from an orchestration. To call the rule and policy from an orchestration, perform the following steps: