2015-02 Loki Release Notes

Overview

The Loki release focused on the expansion of carrier costing fields to all traditional product in order to better integrate with third party reconciliation companies. The system will now support applying external Carrier Billing Identifiers to products so they can be reconciled more easily. Any products that currently had costing information already tied to them has now been migrated to the new Carrier Cost Details section of the Traditional product. See below for more details on this new feature within the Traditional Products section as well as other general enhancements and bug fixes.

General TBS
Traditional Products
Integrated Products

General TBS - Enhancements & Bug Fixes

25669 - Add new Estimated Revenue field on Orders Development

A new "Estimated Revenue" field has been added to the Orders Screen. The purpose of this informational field is to track the estimated revenue increase (or decrease) associated with the current order. The data must be in a currency format. This field is informational only, but can be used in reporting if desired.

25960 - Update Location Country to optionally require not require Zip code

TBS launched a United States postal code look-up verification tool on the Locations tool back in 2014. This has been expanded to now also verify if a Country other than the US should require a zip code. A new field (RequirePostalCode) has been added to the Countries table to support countries which do not require a postal code (e.g. the Bahamas). Countries whose RequirePostalCode value is not set are presumed to require a postal code. The value for the Bahamas is being set to 'false' and thus will no longer require a postal code on the location screen.

27001 - Carrier Cost Field Expansion: Permission updates to now use a new Cost Module

A new security module, Cost, has been added to control access to product cost information.

This information is available in both Traditional and Integrated Products. See the table below for a brief overview of the permission changes. Permission to the Cost module has been backfilled by the rights previously used.

Product Type	Previous Security Rights	New Security Rights
Traditional Products	Products Module - Update Accounting Module - Access	Products Module - Update Cost Module - Add/Update
Integrated Products	Products Module - Access ProductsAdmin - Admin	Products Module - Access ProductsAdminModule - Add/Update Cost Module - Add/Update

Here are a few examples of how the permissions have been backfilled at release time. Going forward, please be sure to refer to the table above for information on how access to Cost fields can be set.

Traditional Product Backfill Example:

User A has Update rights on products and Access (but not Update) rights to Accounting. User A will be given Add/Update rights to the new Cost module and have the ability to Update cost information.
User B has Update rights on products but NO rights to Accounting. User B will NOT be given rights to the Cost module and will not have the ability to Update cost information.

Integrated Product Backfill Example

User C has Admin Access rights on ProductsAdmin. User C will be given Add/Update rights to the Cost module and have the ability to Update cost information.
User D has Update rights on ProductsAdmin, but NOT Admin Access. User D will NOT have the ability to Update cost information.

25954 - Metrics now includes data Operation and Transaction Deletes are now included

The Metrics view within TBS will now show the actual Operation of the data being updated / changed. Metrics may show an operation of Add, Update or Delete. This can be useful for identify if items are initially Added or when they are Deleted as previously, these were somewhat cryptic in that they involved the updating of Null values.

Additionally, Transaction Delete activity will now also start being a part of the Metrics view. Transaction Adds will not be present since due to the number of transactions within the TBS system, this could cause performance issues.

Note: These Transaction Deletes in metric only applies to Posted Transactions only. This does not apply to Temporary transactions deleted on the Transaction Posting screen that have yet to post to an account.

25616 - Bug: Flex report export issue w/ Money Fields Development

The Excel export options available from the report grid have changed. One new method has been added and options have been renamed for clarity.

There are different methods of exporting to Excel from the report grid; the best method can vary depending on what the export will then be used for (e.g., calculations, printing, etc.).

With this release, the methods are now:

Excel - This method is new, produces a binary spreadsheet compatible with Office versions since 2013, and is suitable for most purposes.
Excel HTML - This method has not changed.
Excel XML - Prior to this release, this method was known simply as Excel. Other than the name change, this method works as it did prior to this release.

Traditional Products - Enhancements & Bug Fixes

Carrier Cost Field Expansion: Billing Identifiers

TBS supports the ability for Carrier Cost information to be tied to products. This feature has been expanded to now also allow for one or more Carrier Billing Identifiers to be tied to a product along with corresponding cost information to help with third party reconciliation. Customers can now add in appropriate Carrier IDs for products along with Carrier cost information that can then be reported on and used as needed.

Previously, any cost information only existed for Dedicated and Internet product types. With this release, carrier cost information is being expanded and will now be available on these product types:

Local
Cable
Internet
Fixed charges
Dedicated
Wireless
Long distance
Toll-free
Travelcard
Calling card
Dedicated long distance
Dedicated toll-free
Voicemail (added in the Odin Release)

This new Carrier Cost information can be accessed via the Product Links menu on each of the product screens listed above. Any cost fields that previously existed on the Dedicated or Internet screens have been removed and all data has been migrated to the new Carrier Cost Details area.

Each Carrier Cost Detail entry supports the following fields:

Field Name	Definition	Notes
Service Description	Required field. Type of Service corresponding to the Cost information at the Carrier level	The options can be maintained by choosing Drop Down Menus from System Administration. Screen Name = [Blank] List Name =TraditionalProductCarrierServiceDescription
Carrier Detail ID	Required Field. The Carrier ID or Unique ID that the Carrier uses to bill and identify this particular product
Activation Cost	The Carrier Activation Cost for the product.
Interval Cost	The Carrier Interval (recurring) cost for the products.
Cost Verification Date	The date the Cost record has been verified.

The following fields are being removed and data migrated to the fields mentioned above:

Dedicated

- CarrierCost
- CarrierCostVerified
- CarrierInstallCost
- CarrierRouterCost

Internet_Master

- CarrierCost
- CarrierCostVerified

25856 - Additional Fields on the Voicemail Development

New "Active Date" and "Disconnect Date" fields have been added to Traditional Product Voicemail screen.

It is important to note and remember that this Voice Mail screen is for "Information Only" and in no way impacts billing the client. Because of this, the Status / Workflow Actions from Customer or Orders does NOT flow down to these VoiceMail screens.

25611 - Field Expansion: Additional Field on Dedicated Screen

A new "Service Type" field has been added to the Dedicated Product screens. The purpose of this informational field is to track the type of service (DIA, Ethernet, Integrated, etc) being carried on the Dedicated Circuit.

25968 - Add Area of Service Options on LD screen Development

Area of Service Options have been added on the Long Distance Product Screen.

These work exactly as the Area of Service Options on the Toll Free Product Screen. Users may set:

Area of Service (US 48, US & Canada, US 50+ Territories, etc)
Enter the Allow/Block Information in a pop up window

Important: This information is for tracking purposes only and will NOT be sent in any Provisioning Batch Files.

26005 - Add Carrier Drop Down to all Traditional Products Development

Carrier and Carrier Account Number fields have been added to the following Traditional Products:

Fixed Charges
Conference Calling - as with Long Distance, both Inter and Intra Carrier information is available
Local
Wireless

These fields previously existed on the following Traditional Products:

Dedicated
Calling Card
LongDistance - On this screen both Inter and Intra Carrier information is available
TollFree

25635 - Bug: Exceptions - Intra rating error Development

A bug on Long Distance Exception Rates has been corrected.

When creating an "IntraLata" rate exception, the system would fill the Exception Location drop down list with States instead of Lata. Now the system correctly fills this drop down list with valid Latas.

27162 - Bug: Apply Filter Option not in the grid when adding Existing Account Codes to an Order Development

Fixed a bug when "Adding Existing Account Codes to Order". Users could build Account Code filtering criteria but the "Apply Filter" option was not being displayed in the grid. This has been corrected.

26205 - Bug: TBS Allows Duplicated Dedicated ProductIDs Development

Bug Fix: An issue that allowed Duplicate Dedicated ProductID (Circuit ID (A)) has been corrected. TBS will now alert the user when a duplicate Circuit ID is entered as it does on other Traditional Products.

Integrated Products - Enhancements & Bug Fixes

Carrier Cost Field Expansion: Billing Identifiers

TBS supports the ability for Carrier Cost information to be tied to product Charges & Plans. This feature has been expanded to now also allow for a Carrier Billing Identifiers to be tied to a charge/plan along with corresponding cost information to help with third party reconciliation. Customers can now add in appropriate Carrier IDs for charges/plans along with Carrier cost information that can then be reported on and used as needed.

If multiple cost records are needed per product, it is advised that users setup distinct charge / plan records that may not have a billing revenue amount, but may contain cost information that can then be rolled up at the product level.