11 Creating Rules and Rulesets

This chapter describes how to create rules and rulesets using the Rules tab of the Policy Designer interface to Oracle Communications Service Broker Policy Controller (Policy Controller).

The rules engine used by Policy Controller is built on the rules engine for Oracle Business Rules, an Oracle Fusion Middleware product. For general information about Oracle Business Rules and details on the operands and facts you use to build them, see Oracle Fusion Middleware User's Guide for Oracle Business Rules 11g Release 1 (11.1.1.5.0 Feature Pack) at:

http://www.oracle.com/technetwork/middleware/soasuite/documentation/11gr1ps4featurepackdoc-462677.html

There is one significant difference between Oracle Business Rules and Policy Designer. Policy Designer uses the term Lists of Values instead of the term “Buckesets” used by Oracle Business Rules.

About Rules and Rulesets

Policy Controller applies PCC profiles to subscribers that specify service flow limits. The PCC profiles themselves are selected by the rules that you create and deploy in dictionaries. You can create collections of rules to work with one another in a single deployment. This chapter explains how to create these rules and deploy them in rulesets.

You create rules by using the Rules tab of the Policy Controller Policy Designer interface. A knowledge of programming with a third-generation programming language is very helpful for understanding the Rules tools and creating rules.

Each rule has two parts: an IF section and a THEN section. The IF section contains a condition test based on evaluation of data from various sources. The THEN section contains actions that can be performed if the test passes. If the condition in the IF section evaluates to true, the rule performs the actions in the THEN section. The actions usually involve dynamically applying a PCC profile to a subscriber or removing a PCC profile from a subscriber, but they may involve other actions as well.

Your rules and rulesets can be as simple or as complex as your deployment requires. You can set up the rules to select a single PCC profile for the entire service flow, or implement any number of PCC profiles. Policy Controller also enables you to reinterpret your rules dynamically as the service flow continues and the input data, such as the approach of a resource limit, changes. You can specify rules that change the PCC profile, for example, if a subscriber reaches a service limit or credit limit.

Rules can be added, modified, and deleted whenever required and can also be activated and deactivated individually.

You manage the following components, which are related to rules, using the Rules tab:

Rulesets: A ruleset provides a unit of execution for a collection of rules. You can prioritize the rules within a ruleset.
Rule: Rules are individual test for conditions that determine which profiles your subscribers are entitled to.
Lists of Values: A list of values defines a set of values for a particular fact or a property of a fact.
Complex Lists: See "Using Grouped AVPs in the Rules" for details.

Working with Rules

Each rule takes the form of an IF-THEN statement or collection of IF-THEN statements. The IF section of the rule defines a boolean condition, which may be composed of multiple conditions called tests, associated with each other by logical operators. The THEN section describes one or more actions. If the IF condition evaluates to true, the actions in the THEN section of the rule are performed.

See "Using the Advanced Menu Features for All Rulesets" for details on using the advanced feature of the Rules tab.

Figure 11-1 shows the IF statement components. In this example, the IF statement is testing whether the subscriber's account state is Active and whether the account type is Top_tier. If both statements are true then the THEN statement action (shown in Figure 11-3) is performed.

Figure 11-1 Policy Designer Rule IF Statement Components

Surrounding text describes Figure 11-1 .

Tip:

If you must create multiple rules that use the same IF statement, it is considerably more efficient to create a local fact out of the IF statement using a LocalFact operator and then reference the local fact in your rules.

Figure 11-2 shows the left condition browser with Sy and System Variables expanded. The left condition browser displays all the conditions available for you to create rules. Once you pick a condition in the left condition browser, the conditions displayed in the right condition browser are automatically filtered, and only offer the appropriate available conditions.

Figure 11-2 Policy Designer Rule Condition Browser

Surrounding text describes Figure 11-2 .

Figure 11-3 shows the THEN statement components. THEN statements are the objects of IF statements. They serve as the rule action.

Figure 11-3 Policy Designer THEN Statement Components

Surrounding text describes Figure 11-3 .

Figure 11-4 shows the THEN statement actions menu displaying the actions available to use in rules. After selecting action, you then select or enter a fact for the rule. The example in Figure 11-3 uses the “install PCC profile” action, that will install the Gold_Plan PCC profile created for the example. Because the PCC profiles had already been created, the fact menu (not shown) was automatically populated with the profiles to select from.

Figure 11-4 Policy Designer Rule THEN Actions

Surrounding text describes Figure 11-4 .

Implementing Rules

The general workflow for implementing rules is:

Create a ruleset. See "Creating a Ruleset" for details.
Create the rules in the ruleset. See "Creating a Rule" for details.
Create the list of values and decision functions as needed to support the rules. See "Managing Lists of Values" for details.
Validate the ruleset.
Deploy the ruleset and supporting list of values and functions as a deployment. Once deployed, the rules are applied to your Policy Controller subscribers. See "Deploying Rulesets to a Deployment" for details.

You create rules inside a ruleset using the Rules tab of the Policy Designer. You can change the order in which the rules are displayed in the ruleset; see "Changing the Display Order of Rules in a Ruleset". You can page through the rules in a ruleset using the arrows to the right of the ruleset name. The Deployments tab displays individual deployments and shows some of their details.

You can dynamically associate a rule with a profile when an Assert New action asserts the InstallPolicy fact. A rule is dynamically disassociated from a profile when an Assert New action asserts the RemovePolicy fact. See "Asserting a New Action" for more information.

You can also create rules by importing a previously created deployment. See "Working with Deployments" and "Managing Deployments" for information about importing a deployment.

You can create a PCC profile from the PCC Profiles menu of the rule editor, and also from the profile editor. See "Creating a Dynamic PCC Profile" for information on how to do this.

Rule Editor Naming Conventions

A ruleset name must start with a letter and can contain only the letters (a to z and A to Z), numbers (0 to 9), the following characters: “.”, “-”, “_”,”_”,””, “:”, “/”, and single spaces.

A deployment name can contain only letters (a to z and A to Z), numbers (0 to 9), and the underscore (_) character. Special characters are not permitted in a deployment name.

Other names and aliases, used for rules, facts, list of values and so on, must begin with a letter and contain only letters, numbers, “.”, “-”, “_”,”_”,””, “:”, “/”, and single spaces.

A type name defined by the specification as containing a hyphen (-) may need to have its hyphen changed to an underscore (_) to accommodate the Java-based rules engine. For example, the specification defines the IP-CAN_CHANGE event trigger AVP, but this value does not validate and must be changed to IP_CAN_CHANGE when used in a rule. The Expression Builder automatically enters this value as IP_CAN_CHANGE. See "Using the Expression Builder" for information about the Expression Builder.

Viewing and Modifying Deployments

You manage deployments from the Deployments tab. See "Working with Deployments" for details.

Creating and Deleting Rulesets

This section explains the tasks required to create or detect rulesets.

Creating a Ruleset

To create a ruleset:

Start the Policy Designer
Click the Rules tab.
Select Create from the Rulesets menu.

The new ruleset appears in the list of rulesets.
Click the ruleset if it is not already selected
Assign a name to the ruleset by overwriting the default name in the text field.
Select the New Rule (page and plus sign) icon.

The IF-THEN fields appear.
Rename the rule by overwriting the default name in the text field.
If you want to configure advanced settings, toggle the advanced settings icon to the left of the Rule name field. See "About the Advanced Settings for Rulesets, Rules, and Rule Actions" for more information on the advanced settings.

The advanced settings fields appear. Configuration of these fields is optional.
1. In the Description field, you can enter an option textual description of the ruleset. [Advanced Setting]
2. From the Effective Date menu, select a configuration for the effective date of the ruleset. See "Setting the Effective Date for a Rule or Ruleset" for details. The default is Always. [Advanced Setting]
3. Confirm that the Active check box is checked. To deactivate the ruleset, check this box. [Advanced Setting]
Add rules to your ruleset. See "Creating and Deleting Rules" for details.
Click Validate to confirm that your new rule has a valid syntax.

You can export an invalid ruleset to a file to work on later, but it must validate successfully before you can deploy it.
To save your work you have these options:
- Deploy the ruleset to a deployment. See "Deploying Rulesets to a Deployment" for details. All rules must validate successfully before you can deploy them.
- Save the ruleset to a file. See "Working with Deployments" for details. Use this option to save incomplete rules and rulesets to work on later. They do not need to pass validation to be saved to a file.
WARNING:

If you do not export or deploy the ruleset, your work is not saved.
Your ruleset now appears in the Rulesets section on the left side of the Rules tab

Deleting a Ruleset

To delete a ruleset:

From the Rulesets list, select the ruleset that you want to delete.
Select Delete from the Rulesets menu.

The selected ruleset is deleted.

Deleting a ruleset does not affect a deployment that has already been exported or deployed. To make the deletion permanent, you must export or re-deploy the deployment.

Setting the Effective Date for a Rule or Ruleset

The Effective Date menu is displayed only when advanced settings are shown. See "About the Advanced Settings for Rulesets, Rules, and Rule Actions" for details on the advanced settings.

To set the effective date of a rule or ruleset:

From the Effective Date menu, select one of the options described in Table 11-1:

Table 11-1 Effective Date Settings

Value	Description
Always	The rule or ruleset is always in effect.
Range	The rule or ruleset is in effect from the specified start date to the specified end date.
From	The rule or ruleset is in effect from the specified start date with no end date.
To	The rule or ruleset is in effect from the deployment of the ruleset to the specified end date.

If you specified a value other than Always, select from the date-time menu whether you want to specify a date, a time or both a date and a time for the start date and end date values. This setting applies to both the start and end dates. You cannot assign different configurations to the start and end dates.
If you are specifying a start date, click the date-time icon to the right of the Start Date field.

An editable calendar appears.
In the calendar, set the date and / or the time and time zone, depending on whether you are setting a date, a time or both.
Click OK.
If you are specifying a range or an end date, click the date-time icon next to the End Date field and repeat steps 4 and 5.

Managing Rulesets

You can activate/deactivate rulesets or change the order in which they are applied by using the Manage Rulesets item from the Advanced menu. See "About the Advanced Settings for Rulesets, Rules, and Rule Actions" for more information on the advanced settings.

To activate/deactivate or change the execution order of rulesets:

Start the Policy Designer
Navigate to the Rules tab.
On the left side of the Rule tab select Manage Rulesets from the Advanced Menu.

The Manage Rulesets screen appears, containing entries for all of your rulesets.
To deactivate a ruleset, use the single left arrow button to move it from the Active list to the Inactive list. The double arrow moves all the rulesets.

Note:
You can also activate a ruleset using the Active check box on the Rules tab. If you set a ruleset as inactive using one of these tools, it remains inactive, regardless of the other setting.
To activate a ruleset, use the single right arrow button to move it from the Inactive list to the Active list. The double arrow moves all the rulesets.
To change the order in which ruleset are applied, select the ruleset to reorder.
Do one of the following:

Click this icon to move the ruleset one position up:

Description of the illustration sbpms_df_up.gif

or

Click this icon to move the ruleset one position down:

Description of the illustration sbpms_df_down.gif

or

Click this icon to move the ruleset to the top of the list:

Description of the illustration sbpms_df_top.gif

or

Click this icon to move the ruleset to the bottom of the list:

Description of the illustration sbpms_df_bottom.gif
Navigate away from the Manage Rulesets window once you have made your changes.

Creating and Deleting Rules

This section explains the procedures for creating and deleting rulesets.

Creating a Rule

To create a rule:

Start the Policy Designer interface.
Select the Rules tab.
Select a ruleset.
Click the new rule icon.

Description of the illustration sbpms_newrule_icon.gif

The rule is created.
Overwrite the default rule name with the name of your choice in the rule name field.
If you want to configure advanced settings, toggle the advanced settings icon to the left of the rule name field to display the advanced settings fields.

Description of the illustration sbpms_adv_icon.gif

The advanced settings fields appear. See "About the Advanced Settings for Rulesets, Rules, and Rule Actions" for more information on the advanced settings.

Configuration of the advanced settings fields is optional.
1. In the Description field, you can enter an option textual description of the rule. [Advanced Setting]
2. From the Effective Date menu, select a configuration for the effective date of the rule. See "Setting the Effective Date for a Rule or Ruleset" for details. The default is Always. [Advanced Setting]
3. Select a priority level from the Priority menu relative to the priority of the other rules in the ruleset. The options are: highest, higher, high, medium (the default), now, lower, and lowest. [Advanced Setting] Higher priority rules are interpreted before lower priority rules. The default priority is medium.
4. Check the Rule Active check box to activate the rule or clear the check box to deactivate it. The default is Rule Active. [Advanced Setting]
5. To enable advanced mode, check the Advanced Mode check box. Advanced mode allows additional pattern-matching options for creating conditions and actions. Advanced mode also enables you to test the rule with specific data values. See the discussion of advanced mode rules in Oracle Fusion Middleware User's Guide for Oracle Business Rules for information about advanced mode. [Advanced Setting]
6. To enable tree mode, check the Tree Mode check box. Tree mode is used for master detail rule hierarchies. See the discussion of tree mode rules in Oracle Fusion Middleware User's Guide for Oracle Business Rules for information about tree mode. [Advanced Setting]
In the IF section of the rule editor, define the rule's condition. See "Defining the Condition of a Rule" for details.

Note:
By default the grouped AVPs are not displayed. See "Using Grouped AVPs in the Rules" for details on displaying grouped AVPs.
In the THEN section of the rule editor, define the rule's actions. See "Defining the Actions of a Rule" for details.
To save your work you have these options:
- Deploy the ruleset to a deployment. See "Deploying Rulesets to a Deployment" for details.
- Save the ruleset to a file. See "Working with Deployments" for details.

Deleting a Rule

To delete a rule:

Click the delete icon next to the rule that you want to delete.

Description of the illustration sbpms_delrule_icon.gif

Defining the Condition of a Rule

A condition is composed of one or more tests, connected by and or or logical operators. Each test evaluates to true or false. A single row of fields in the IF section of the rule editor represents a single test. If the entire condition defined in the IF section of the rule evaluates to true, the actions defined in the THEN section of the rule are performed. If the condition does not evaluate to true, none of the actions are performed.

Defining the condition of a rule involves constructing one or more tests and combining them with the correct logical operators to create the condition.

You create a test by editing a row of fields in the editor in the IF section of the rule editor. A test consists of three components:

Left operand
Comparison operator
Right operand

See the "Example Rules" section to examine sample rules that you can use as models for your own rules.

Note:

For ease of use Policy Controller enables you to enter UTF-8 values for the AVPs that the 3GPP specifications specify in octet format, such as GxUser-Equipment-Info-Value.

Creating a Test

To create a test:

Do one of the following:
- If a blank test row is displayed in the IF section of the rule, continue to step 2.
or
- To add a new test row, in the IF section of the rule click the insert test button to the right of the existing test row.
  
  Description of the illustration sbpms_addtest_button.gif
  
  You may have to scroll horizontally to see the end of the row.
  
  A new test row appears.
Define the left operand of the test by doing one of the following:
1. Click the search icon to the right of the left operand field.
  
  The Condition Browser appears.
2. In the Condition Browser, select the value to use for the left operand.
  
  See "Using the Condition Browser" for information about the Condition Browser.
or
- Enter a literal value by typing the value directly into the left operand field.
Repeat step 2 for the right operand, using the search icon to the right of the right operand field to display the Condition Browser.
From the menu of comparison functions between the two operand fields, select the function to use to compare left and right operands.

The menu is context sensitive, so its items vary depending on the contents of the left and right operands.

Deleting a Test from a Rule

To delete a test from a rule:

Click the delete test button to the right of the test that you want to delete.

Description of the illustration sbpms_deltest_button.gif

Creating a Condition with Multiple Tests

To create a condition that contains multiple tests:

Create a test as described in "Creating a Test".
Click the insert test button on the right side of the test row to add another test.

Description of the illustration sbpms_addtest_button.gif
Toggle the logical operator on the right side of the first test to be and or or depending on the logic of the condition you are creating.
Create another test.
Continue to add tests and connect them with logical operators until you have constructed the entire condition.
If you want to enclose multiple tests in a parentheses to create nested tests, check the check boxes to the left of the rows that you want to enclose and click the add parentheses icon above the condition.

Description of the illustration sbpms_add_parens.gif

The tests being enclosed in a single set of parentheses must be contiguous in the rule editor. If necessary, change the order of the tests before applying the parentheses. See "Changing the Order of Tests" for information on how to do this.

To remove the parentheses:

Check the check boxes to the left of the tests around which you want to remove parentheses.
Click the remove parentheses icon above the condition.

Description of the illustration sbpms_rmv_parens.gif

Changing the Order of Tests

The tests are evaluated in the order in which they appear in the rule.

To change the order in which the tests are evaluated:

Check the check box to the left of the test for which you want to change the position.
Click the up or down arrow at the top of the IF section to change the position of the test in the rule. Every click moves the test up or down one row.

Description of the illustration sbpms_reorder_arrows.gif

Defining the Actions of a Rule

In the THEN section of the rule, you define the actions to be performed if the condition evaluates to true. Each row of fields in the THEN section of a rule defines a single action.

To define an action:

Do one of the following:
- If there are no action rows displayed, click Insert Action.
or
- If action rows are displayed, click the insert action button on the right side of an existing row to create an action row.
  
  Description of the illustration sbpms_insert_action.gif
A new action row appears.
The default rule action is InstallPCCProfile. If you are installing a PCC profile select the Edit Properties box, and from within it select from the PCC profiles available. is automatically populated with actions that you are allowed.

If you are not installing a PCC profile, select another option from the rule action menu. See "Asserting a New Action" for details on the menu items.

Asserting a New Action

You can assert the following actions in the actions (THEN) section of you rules. These actions are all outputs of the rules engine.

If you select one of these actions facts, and then select the Edit Properties (pencilXYZ) icon, the Edit Properties form appears. You can type an entry in the Value field, or select the search icon to choose from a list of all acceptable values. The acceptable values list is automatically populated with just the permissible values for the action you chose.

InstallPCCProfile: Associates the rule with the specified PCC profile. The value property contains the PCC profile name.
RemovePCCProfile: Disassociates the rule from the specified PCC profile. The value property contains the PCC profile name to disassociate.
AddEventTrigger: Adds the specified event trigger to the Gx session. The value property contains the event trigger to add. You can specify any event trigger from the Policy and charging control over Gx reference point (3GPP TS 29.212 Release 9) specification. See "About Event Triggers" for more information.
RemoveEventTrigger: Removes the specified event trigger from the Gx session. The value property contains the event trigger to remove. You can specify any event trigger from the Policy and charging control over Gx reference point (3GPP TS 29.212 Release 9) specification. See "About Event Triggers" for more information.
ClearEventTriggers: Removes all existing event triggers from the Gx session set, including all the system-level event triggers and adds the NO_EVENT_TRIGGERS (14) event trigger to the Gx session.
SetAbsoluteRevalidationTime: Sets a deadline, before which the PCEF should re-request an update of the rules. The timer is set to an absolute date/time; for example: 2011-12-30 14-55-30 PST.
SetRelativeRevalidationTime: Sets a deadline, before which the PCEF should re-request an update of the rules. The timer is set as the number of seconds from the time that the rule was invoked; for example: 3600.
Redirect: Redirects all service data flows to a Web address (global session redirection). See "Globally Redirecting All Services in a Session" for details.
RedirectPCCProfile: Redirects a single service inside a session to a Web address (service based redirection), and associates a new PCC profile to the rule. See "Redirecting Individual Services Inside a Session" for details.
SendSMS: Sends and SMS message as part of the rule action. See "Adding SMS details to a Rule" for details.
InstallADCProfile: Associates the rule with the specified ADC profile. The value property contains the PCC profile name.
RemoveADCProfile: Disassociates the rule from the specified ADC profile. The value property contains the ADC profile name to disassociate.
SetAdcAbsoluteRevalidtionTime: Sets a deadline, before which the PCEF should re-request an update of the rules. The timer is set to an absolute date/time; for example: 2011-12-30 14-55-30 PST.
SetAdcARelativeevalidtionTime: Sets a deadline, before which the PCEF should re-request an update of the rules. The timer is set as the number of seconds from the time that the rule was invoked; for example: 3600.
LocalFact: Creates a custom fact. See the discussion of LocalFact in "Using the Condition Browser" for more information.

To define an assert new action:

In the THEN section of the rule editor, select Assert New in the left menu.
Select the fact to assert from the right menu.
Click the pencilXYZ icon.

A properties form appears in which you set the value of the fact.
If the value is a constant, check the Constant check box.
To set the value of the fact do one of the following:
1. Click the search icon to the right of the Value field.
  
  The Condition Browser appears.
2. In the Condition Browser, select the value.
  
  See "Using the Condition Browser" for information.
or
- Enter a literal value by typing the value directly into the Value field.
Click OK.

Changing the Order of Actions

The actions are performed in the order in which they appear in the rule.

To change the order in which the actions are performed:

Check the check box to the left of the action for which you want to change the position.
Click the up or down arrow at the top of the THEN section to change the position of the action in the rule. Every click moves the action up or down one row.

Deleting an Action

To delete an action from a rule:

Click the delete action button to the right of the action that you want to delete.

Description of the illustration sbpms_deltest_button.gif

About Event Triggers

Policy Controller uses event triggers to inform the PCEF that it should trigger a new request for rules when any of the subscribed events, such as an IP-CAN change, occurs at the gateway. You can use the default specified triggers or add your own. See "Using an Event Trigger to Change a PCC Profile" for details.

Using the Condition Browser

The Condition Browser is generally used for creating unusually complex expressions to use in rules. You use it to browse for values to use in the operands of a test in the IF section of a rule, and values used for the properties of facts in the THEN section of a rule. The Condition Browser contains a text field, a hierarchical tree view of the rules metadata, organized by protocol, and an embedded Expression Builder. The Condition Browser is also a mechanism for including any method parameters in rules.

There are three ways to enter a value this browser:

You can select a leaf item from the tree.
You can type values directly in the browser text field.
You can use the Expression Builder embedded in the browser to create an expression. See "Using the Expression Builder" for more information.

After you enter a value into the in the browser's text field by one or a combination of these methods and click OK, the value appears in the operand field that you are editing in the rule editor.

The default nodes displayed in the browser tree reference the data listed in Table 11-2. The Condition Browser tree also includes any facts that you have already used in rules. In general the nodes contain data facts generated outside the rules engine and used as input for the rules engine. The individual nodes can contain child nodes.

Table 11-2 Condition Browser Node Data

Node	Description
Gx (Enforcement Function)	Attributes in the gx node specify data concerning traffic between your PCEF and Policy Controller. They are defined in the Policy and charging control over Gx reference point 3GPP TS 29.212 (Release 9) specification.
LocalFact	LocalFact is used for custom values that can be used in actions and tests. LocalFact supports integerValue, name, booleanValue, and doubleValue values. You can assert a LocalFact: assert new LocalFact (integerValue:42) then create a test based a LocalFact value: IF LocalFact.integerValue isn't 42 and then modify LocalFact in another action: modify LocalFact (name:"strange value")
Rx (Application Function)	Attributes in the Rx node specify data from the traffic between Policy Controller and your Application Functions. They are defined in defined in the Policy and Charging Control Over Rx reference point 3GPP TS 29.214 v9.8.0 (2011-09)(Release 9) specification.
Sp (Subscriber Profile)	Attributes in the Sp node specify data from the traffic between Policy Controller and the SPR portion of the SPR/OCS that you are using. Policy Controller uses an Sh-like interface for Sp data. For details on Sh, see the Sh Interface based on the Diameter Protocols (3GPP TS 29.329 V10.4 (2011-12) and the discussion of the subscriber store data model in Oracle Communications Service Broker Subscriber Data and Lifecycle User's Guide.
Sy (Spending Limits)	Attributes in the Sy node specify data from the traffic between Policy Controller and the OCS portion of the SPR/OCS that you are using. They are defined in defined in the Sy Interface based on the Diameter Protocol (3GPP TS 29.219 Release V11.2 (2012-09) (Release 11) specification
System Variables	Attributes in this node currently include the currentTime variables, such as amPm, dayOfMonth, and so on.

Using the Expression Builder

You use the Expression Builder to build advanced expressions used in rule tests.

You access the Expression Builder from the Rules tab Condition Browser by clicking the Expression Builder icon:

You can directly type an expression in the Expression text field in the Expression Builder. You can also insert values from the rules metadata using the four tabs: Variables, Functions, Operators, and Constants. Each tab displays the rules metadata in a tree structure.

To build an expression, select an item in the tree and click the Insert Into Expression button to insert the selected item at the cursor position into the Expression text field. You can switch among the tabs for the different items needed to build the expression. You can also type directly in the text field.

After you have created the expression and clicked OK, the expression appears in the text field in the Condition Browser.

Expression Builder provides a variety of functions to simplify rule creation.

The Functions tab of Expression Builder is especially useful for providing functions that can be used in tests. The "Applying a Profile for Part of a Day" example uses the Gx GetCalendarAtHour function to This function requires you to use the Expression Builder Functions tab.

To select the GetCalendarAtHour function, click the search icon in the right side of the rule IF statement. In this example, the left side of the IF statement specifies the Gx MS-TimeZone_3GPP.date object, so the Set Date and Time window appears. Click the Date Expression option and then click the search icon from this window. The Condition Browser appears. Click the Expression Builder icon from the top left and the Expression Builder window appears. Select the Functions tab of the Expression Builder, and select the GetCalendarAtHour function from where it appears under Gx. The GetCalendarAtHour function appears in the right side of the IF statement.

Changing the Display Order of Rules in a Ruleset

To change the order in which the rules are displayed in the rule editor, use the up and down arrows to the right of the rule name field to move the rule. Each click moves the rule one position up or down in the ruleset.

Description of the illustration sbpms_reorder_arrows.gif

The display order of rules in the rule editor has no effect on the order in which the rules are fired.

Deploying Rulesets to a Deployment

To deploy a rules deployment:

Click the Deploy button at the top of the rule editor.

A dialog box appears containing a Note text field.
Optionally add a note about the deployed deployment in the Note text field.

The text that you enter appears near the top of the screen in the Deployments tab of the Policy Designer when the deployment is loaded.
Click Deploy in the dialog box to deploy the deployment.

Future updates to the deployment do not affect a deployed deployment. To include updates in the release, you must re-deploy the deployment.