The Behavior tab functionality applies to add-on and swap transactions on existing services submitted through the web, POS, and the Advanced Change Features wizards.
The Advanced Change Features wizards are available via the Advanced Wizards button on the Service and Features tabs.
This functionality does not impact new services, nor does it impact add-on orders submitted by right-clicking on a service and selecting New > Change Features.
Selections on the Behavior tab take precedence over permissions in the Admin Console.
The options under "When Contract Sold" take precedence over all of the above if the contract is part of the order.
If a contract is not part of the order, these options are ignored. These options operate as follows:
When the Force Add On/Swap Effective Date to Contract Start date is selected, the effective date will be set to the contract start date regardless of permissions AND Add On/Swap Effective options.
The Behavior tab on the New or Edit Product window contains these fields.
Related Items Folder | The name of a folder containing related items (optional). |
Is Restricted | If checked this catalog item is restricted so that only authorized users can add the item to a POS order via the Find Catalog Items tool. See Restricting the Sale of Catalog Items. |
Exclusive Group | An Exclusive Group ensures that redundant features do not get assigned to a service. |
Hide on Sales and Returns | If checked this item is not displayed as a line item on a POS Sale, a Return transaction, or the associated quote and/or receipt.
|
Add On Effective Option | Here you can select an effective date option for the add on product (if the Choose Effective permissions are set in Admin Console). Here you can select an effective date option for the product being swapped (if the Choose Effective permissions are set in Admin Console). See below for more. |
Swap Effective Option | Here you can select an effective date option for the product being swapped (if the Choose Effective permissions are set in Admin Console). See below for more. |
Is Protected | When a SKU is marked as Is Protected, users will not be permitted to perform disconnect/reconnect actions on the SKU independent of the parent Service or Package. Protected SKUs can only be disconnected or reconnected when the action is applied at the Service (or parent) level. Through user permission profiles you can grant certain users the ability to override this setting and perform disconnect/reconnect actions directly on protected SKUs. |
When Contract is Sold | |
Force Add on Effective Date to Contract Start Date | If this is checked, then during an Add On, the product catalog item's start date is set to the contract start date regardless of the Add On Effective option selected or any value selected on the Effective Date window (if shown). This check box is not available for the "contract" exclusive group. |
Force Swap Effective Date to Contract Start Date | If this is checked, then during a swap, the product catalog item's start date is set to the contract start date regardless of the Swap Effective option selected or any value selected on the Effective Date window (if shown). This check box is not available for the "contract" exclusive group or if the exclusive group is empty. |
Effective Date Options for Web Transactions
Web add/swap item transactions observe the related Product Catalog settings for Effective Date and When Contract is Sold. This applies to Contracts, Discounts, Dynamic Charges, Packages, Pricing Plans, Products, and AdvancePay Products.
Also, Orders Field Configuration lets you set Effective Date rules and restrict user groups that can modify the default value for add/swap transactions. Order Field configuration will apply when the item’s Effective Date is set to Default.
Note: This functionality only applies to existing services. It does not apply to a new service being added in a transaction.
These options will apply for:
Adding an item to an existing service - When the selected option does not cause the removal of an existing item on that service due to exclusivity.
Swapping an item on an existing service – When the selected option causes an existing item on that service to be removed due to exclusivity.
The Add On Effective Option and Swap On Effective Option selectors provide the same options:
Default | This sets the Effective Date according to the Order Field configuration. A selector is provided during transaction assembly to change the Effective Date as shown below.
|
Today | The Effective Date is automatically set to the current date and cannot be changed during transaction assembly. |
Back Date | The Effective Date is automatically set to the start of the current billing period and cannot be changed during transaction assembly. |
Forward Date | The Effective Date is automatically set to the start of the next billing period and cannot be changed during transaction assembly. |
When Contract Is Sold Settings
When a contract is added to the same service on the same transaction where an item is being added or swapped, you can use these settings to override the above settings and force the item Start Date to match the Contract Start Date. This applies regardless of which is added first, the contract or the item. Note: If more than one contract is added to the same service in the same order, the item will be updated to match the earliest Start Date of the newly added contracts.
The following message will appear in the top-right corner of the page either when a contract is added and one or more items are in the order configured to match contract Start Dates, or when an item is added that is configured to match contract start dates and one or more contracts are in the order.
Workflow Processing Considerations
Depending on workflow configuration, the Start Date set when the order is processed may be different than the time when the order is submitted. For example, if you submitted an order with Start Date = Today selected on August 1st, but the order isn’t processed by workflow until August 10th, the system will calculate Today at the time of processing, on August 10th and set the Start Date accordingly. This also applies when backdating to current bill period and forward-dating to a future bill period. Note: If you set the Start Date by selecting a specific date from the date selector, it will always be set to the selected date (not impacted by when the transaction is processed).
Examples:
Add Transaction, Exclusivity Not a Factor
Item Effective On Add = Back Date
Item Effective on Swap = Forward Date
In this example there is no other item in the same exclusive group as the item being added, so the Start Date is set to the start of the current bill period according to the item’s Effective On Add setting.
Swap Transaction Triggered by Exclusivity
In this example the same item as above is being swapped with an item in the same exclusive group that already exists on the service. In this case, the Start Date is set to the start of the next bill period according to the item’s Effective On Swap setting.
Set Start Date According to Order Field Configuration
In this example the item’s Effective on Add setting is set to Today.
Note: In all three examples above, Start Date cannot be changed, because these values are set in the Product Catalog.
Defaulting to value set by Order Field Configuration
When the item’s Effective On Add setting = Default, the Start Date is preset according to the Default value specified in Order Field Configuration. In this case, the value can be changed if the submitter has no restrictions.
Decision-making Hierarchy of parent-children items
When observing the configurations of items in a parent-child structure, some effective dates might apply differently, based on the scenario.
When an item with children below it is staged (but the children themselves are not manually staged), and the child items have an Add On/Swap Effective Date of Default, the children will inherit the start date value from the parent; if, however, the children are staged, they will look to the Order Field Configuration default value and preset to that, even if they are different from the parent item.
If children are configured with an Add On/Swap Effective Date of Today, Back Date, or Forward Date, they will be calculated separately of the parent item, regardless of if they’re staged or not, since these values cannot be modified.
Order Field Configuration
You can add fields for Feature Effective Date on Add and Feature Effective Date on Swap. Below shows both fields added.
When you edit either field you can set the default to Current Bill Period, Next Bill Period, or Today and restrict by User Group. Users in restricted user groups are not allowed to modify the applied OFC default value
Effective Date Options for Client-based Transactions
When Back Date, Today, or Forward Date are selected, the permissions configured in Admin Console are ignored. The Choose Effective dates window is not displayed during the Make Sales wizard. The IDI platform will use the option selected on the behavior tab.
When Default is selected, the IDI platform looks at the permissions and sets the effective date accordingly.
No Permissions Enabled. In this case the IDI platform automatically sets the effective date to Effective TODAY without operator intervention (Effective Dates window is not displayed in the wizard).
User Has One Permission Enabled. If the user has only one permission enabled, the Choose Effective Dates window will not be presented in the wizard, and the effective date will automatically be set to the date corresponding to the enabled permission.
Multiple Permissions Enabled - System Administrators. For users who have multiple permissions enabled, the POS Make Sale wizrd presents the Choose Effective Dates window that lists the enabled permissions. Here the user can select any one of the enabled options.