- Administering Oracle Fusion Field Service
- Add an Activity Bundling Rule to Exchange Information
Add an Activity Bundling Rule to Exchange Information
You can add an activity bundling rule as per defined during configuration, when multiple activities use the same form. The data collected in such a form is available for all activities, or activity segments bundled by the rule, regardless of whether the activities or segments are assigned to different days or shifts.
- Click Configuration > Bundling Rules.
- Click Add Bundling Rule.
-
Complete these fields:
- Label: Enter a label for the activity bundling rule. APIs use this label to identify the bundling rule.
- Active: Select the checkbox to make the activity bundling rule Active. The application calculates activity bundles only for the rules that have a status of Active.
- Name: Enter a name for the activity bundling rule in the English language and other languages that are required by your organization.
-
To add the activity bundling keys, click Add Key.
-
On the Add bundling key dialog box, select the
activity property that you want to identify as the bundling key. Among
the standard fields you can select appt_number, caddress, ccity, czip,
customer_number, and aworktype. Among the custom properties you can
select string, integer, and enum types of properties.
Routing compares the values defined in the activity fields against the specified criterion. Activities are grouped together as a visit, only if the values of all activity bundling keys match the specified criterion. For example, if you select Work Order [appt_number] as the bundling key, Routing bundles all the activities that have this work order.
- Select Take the entire value of short fields to define the maximum limit of characters that's taken from the value of a field or property selected as the bundling key. Deselect this check box to define the maximum length manually.
-
Enter the maximum length of the field or property to be considered as
the bundling key in the Length field.
This number must be between 1 and 64.
-
On the Add bundling key dialog box, select the
activity property that you want to identify as the bundling key. Among
the standard fields you can select appt_number, caddress, ccity, czip,
customer_number, and aworktype. Among the custom properties you can
select string, integer, and enum types of properties.
-
To add the associated forms to the activities, click Add
Forms.
- Add all the forms that you want to associate with the activities that are bundled with the current bundling rule.
-
Click Add.
All new activity bundling rules are created as case-insensitive.If visits exist in the application, and if the bundling keys are changed, then after recalculation, the visits that no longer match the keys are split into individual activities. Not Done status for a visit is defined as follows:
-
All the work orders in the visit have final statuses.
- A 'not done' visit either contains a 'not done' work order or several work orders with 'completed' and 'cancelled/deleted' statuses.
-