Release Date: July 28, 2016

New Features

System

NS-1075: Updated NorthScope to a concurrent licensing model

In order to move NorthScope to a concurrent licensing model, the following updates were made:

• NS-1076: Updated the NorthScope database to store the license contents

Customer licenses were moved to be stored in the database instead of the file system in order to allow easier access to reading and validating the contents of each license from within NorthScope.

• NS-1077: Updated NorthScope to authenticate users from the database instead of the file system

As of NS-1076, license contents are stored in the database instead of the file system. Therefore, NorthScope was updated to validate the license from the database instead of the file system. In addition, NorthScope now authenticates users on login by tracking sessions in the system and verifying there are less user sessions than there are licensed sessions.

• NS-1078: Updated the NS System License Page to read the license from the database

Because NorthScope now stores licenses in the database instead of the file system, the System module’s License page was updated to work in conjunction with these updates. The License page now pulls the license information from the database, the Reload License button was removed since the license now lives in the database, and the Used concept was removed from this page as we now track user sessions.

• NS-1084: Designed the User Session delete window

The User Session delete window was created to allow users to delete other user sessions upon login when the number of licensed sessions has been reached, therefore preventing the user from logging in. This window was created to include the error message detailing how many licensed sessions exist, the current users with an open session, and each user’s last activity date/time.

• NS-1085: Implemented the User Session delete window

The User Session delete window was implemented so that if a user attempts to login to NorthScope when there are already the maximum number of licensed sessions in progress, the User Session delete window will open, allowing the user attempting to login to delete a user session. Once the user deletes a user session, that user can login.

• NS-1086: Removed the License Count validation on user creation/edit

Previously, when a user was created or edited in NorthScope, there was a process that checked to see if there were enough licenses to create an additional user. However, with the new concurrent licensing model this check is handled so it does not need to happen at the creation or edit of a user so this process was removed.

• NS-1087: Updated NorthScope to store User Session deletion history

With the added ability to log users out of NorthScope when the license limit is reached, NorthScope was updated to store each instance that a user session is deleted. This history records when a user logs out manually and when a user is logged out by another user.

• NS-1117: Added a System Preference for preventing login by non-administrative users

A system preference was added to prevent logging into NorthScope by users that do not belong to the Administrators security group. This system preference is installed for all companies but changing the system preference in any single company will affect all companies.

NS-1163: Created the Ticket Adjustment Summary report

The Ticket Adjustment Summary report was created to show all voids, corrections, and reprices of Delivery Tickets. This report allows the user to select the following parameters to create the report: From date, To date, Fisherman Account(s), Gear(s), Specie(s), Version Type(s), Display By, Consolidated, and Group Product By. The Display By options include Fisherman and Gear and the Consolidated options include Consolidated or Unconsolidated. Consolidated means that in order for a ticket to be considered an Adjustment, the GL date and the Landed date must be in different GL periods while unconsolidated means that in order for a ticket to be considered an Adjustment, the ticket must be greater than version 1.

Purchasing

NS-1061: Added the ability to print a Tender Resale Invoice

The ability to print an Invoice from a Tender Resale transaction was added by creating the Tender Resale Invoice report and adding the ability for NorthScope to determine whether the user is printing from a Tender Resale or Fisherman Sale when the user selects a Fisherman Invoice to print.

NS-1114: Added tax information to Purchasing list views

Tax information was added to various Purchasing list views via the items below.

• NS-1067: Updated the Fisherman Sale List View

The Fisherman Sale List view was updated to help audit sales tax. These updates included adding a Tax Class column to display the Tax Class assigned to the transaction, a Sub Total column to display the sum of the transaction line items without the tax, and a Tax column to display the total tax applied to the transaction. In addition, the Amount column was renamed Total Amount to clarify that the value displayed is the transaction total including taxes.

• NS-1068: Updated the Fisherman Sale & Tender Resale Inquiry

The Fisherman Sale & Tender Resale inquiry was updated to help audit sales tax. These updates included adding a Tax Class column to display the Tax Class assigned to the transaction, a Sub Total column to display the sum of the transaction line items without the tax, and a Tax column to display the total tax applied to the transaction. In addition, the Amount column was renamed Total Amount to clarify that the value displayed is the transaction total including taxes.

• NS-1069: Updated the Sales List View

The Sales List View was updated to help audit sales tax. These updates included adding a Tax Class column to display the Tax Class assigned to the transaction, a Sub Total column to display the sum of the transaction line items without the tax, and a Tax column to display the total tax applied to the transaction. In addition, the Amount column was renamed Total Amount to clarify that the value displayed is the transaction total including taxes. In addition, the Transaction Class column was renamed Transaction Type.

• NS-1070: Updated the Sales Inquiry

The Sales Inquiry was updated to help audit sales tax. These updates included adding a Tax Class column to display the Tax Class assigned to the transaction, a Sub Total column to display the sum of the transaction line items without the tax, and a Tax column to display the total tax applied to the transaction. In addition, the Amount column was renamed Total Amount to clarify that the value displayed is the transaction total including taxes. In addition, the Transaction Class column was renamed Transaction Type.

NS-1112: Added the Sales Line inquiry

The Sales Line inquiry was added to merge all Fisherman Sale, Customer Sale, Employee Sale, and Tender Resale lines into one inquiry. This inquiry now shows all line items from the aforementioned transactions as well as any tax details applied to the corresponding transactions, which also display as individual line items.

NS-1171: Added the ability to change the Sold To entity on a Customer or Employee Sale prior to posting

Previously, the Sold To header field on Customer and Employee Sales became disabled upon save. This functionality was improved so that once a Customer or Employee Sale is saved, the Sold To header field is still editable but the options are filtered on the entity type originally saved – i.e. if an employee was originally selected and the transaction was saved, only employees would display in the Sold To drop-down after saving.

NS-1199: Created the Tender Deliveries by Product report

The Tender Deliveries by Product report was created to display species delivered by a tender with a landed date within a specified date range. This report allows the user to select the date range, tender(s), gear(s), specie(s), and disposition(s) to include on the report as well as how the product is grouped and displayed with or without detail.

NS-1202: Created the new Ticket Taxes & Premiums report

The Ticket Taxes & Premiums report was created to display the amounts attributed to each tax and premium from new, adjusted, corrected, and voided delivery tickets. This report groups by program and then displays each ticket the corresponding program exists on with details regarding the ticket’s net weight, the ticket’s extended amount, and the amount of the program on that ticket. The tickets included on the report are determined by the landing dates entered in the date range selection criteria.

Sales Order

NS-1177: Created a preference for “Default Invoice Dates from Ship By Date”

The ‘Default Invoice Dates from Ship By Date’ Sales Order preference was created so that users can choose to have the Doc Date, Deliver On Date, and Actual Ship date default from the Ship By date on Invoices. However, the Actual Ship date on the Shipments tab is still editable. This preference only applies to Invoices.

NS-1178: Created a preference for “Manage Invoice Dates from Doc Date”

The ‘Manage Invoice Dates from Doc Date’ Sales Order preference was created so that users can choose to manage their invoice dates by simply editing the Doc Date on the Home tab. This preference only works when the preference for ‘Default Invoice Dates from Ship By Date’ is also set to Yes. When these preferences are enabled and the order is first saved the Doc Date, Deliver On Date, and Actual Ship Date on the Invoice default from the Ship By date and all date fields other than the Doc Date become disabled. Then, when an existing invoice is saved, the Deliver On Date, Ship By Date and Actual Ship Date will default from the Doc Date. However, the Actual Ship date on the Shipments tab is still editable. This preference only applies to Invoices.

NS-1179: Created a preference for “Create SO Shipments in Shipped status”

The ‘Create SO Shipments in Shipped status’ Sales Order preference was created so that users can choose to have Sales Order shipments be built in a status of ‘Shipped’. When this preference is set to Yes, once a shipment is built, it will be built in the status of ‘Shipped’ and will pull its Actual Ship date based on the preference settings for managing invoice dates. This preference only applies to Invoices.

Sales Programs

NS-1165: Created the Freight Rates by Item and Freight Rates by Item Set inquiries

The Freight Rates by Item and Freight Rates by Item Set inquiries were created to give the user visibility to all combinations of sales program, item set, rate assigned to the item set, and address assigned to the program. The Freight Rates by Item inquiry displays this data to the detail of each item on each item set whereas the Freight Rates by Item Set inquiry displays this data to item set detail and does not display each item on the item set.

Improvements

Integration

NS-1207: Improved the integration of base units of measure for items created in GP

Previously, the logic behind integrating the base unit of measure on items created in GP to NorthScope caused an error when UOM schedules were changed for a base unit of measure that was attempting to be integrated on an item. This logic was improved so that the base UOM is integrated directly on items without the additional logic that caused potential problems.

Inventory

NS-1123: Added a validation for UOM on all Inventory transactions

Previously, there was no validation that required a unit of measure on any Inventory transactions. A validation was added on Save that required a UOM to be selected for all line items on the transaction so that the inventory balance and lot balance(s) of the item can be accurately updated according to the UOM selected.

NS-1204: Updated the Inventory transactions to only calculate conversions once

The logic behind the calculations of units and weight on inventory transaction line items was improved to calculate conversions only once instead of an infinite number of times. This improvement was made so that when two units of measures have unbalanced or inverse conversions, they will not convert back and forth until finding an exact match but will round instead.

NS-1205: Updated the Items list view

The Items list view was updated to improve its functionality. This update included changing the Exception Record column to display Yes and blank instead of 1 and 0 and changing the InvTracked column to only display a ‘Yes’ where appropriate and to not display ‘No’.

Purchasing

NS-1022: Added support for dual permits on delivery tickets

Because ADFG requires that the second permit be identified when dual permit is selected, a new field was added to the delivery ticket for ‘Dual Permit ID’. This field allows the user to select the second permit when Dual Permit is set to ‘Yes’. The only permits that display in the dual permit ID drop-down are those that belong to the same transaction class, gear, and CFEC fishery as the fisherman’s permit on the ticket.

NS-1131: Made changes to the Ticket Inquiry List View

The Ticket Inquiry list view was updated to display its data more efficiently and clearly. These updates include appending a ‘V#’ to the end of each ticket number to signify the version number of the ticket clearly, sorting the list view by landed date and ticket number, including the ‘V#’, and rearranging the columns after Units to display as follows: Ext. Amount, Premiums, Gross Amount, Taxes, then Net Amount.

NS-1138: Changed the validation for Crew Size on salmon tickets

Previously, Crew Size was required on salmon and troll tickets in NorthScope. However, because crew size is not used on salmon landings, this requirement was updated so that Crew Size is no longer required on Salmon and Troll tickets in NorthScope but it remains required on all other ticket types.

NS-1159: Updated the Fisherman Sale Lines list view to show Tax Details

The Fisherman Sale Lines list view was updated to include Tax Details as line items in order to allow for easier auditing of sales tax. To accomplish this, the Tax Class column was added, Tax Details now display as line items under the transaction items on the transaction to which the tax detail(s) correspond, the Receivable Account was renamed Debit Account and moved after the Extended column, the Receivable Account description column was renamed Debit Account Description and moved after Debit Account, the Purchase Account column was renamed Credit Account and moved after Debit Account Description, and the Purchase Account Description column was renamed Credit Account Description and was moved after Credit Account.

NS-1160: Updated the Sale Lines list view to show Tax Details

The Sale Lines list view was updated to include Tax Details as line items in order to allow for easier auditing of sales tax. To accomplish this, the Tax Class column was added, Tax Details now display as line items under the transaction items on the transaction to which the tax detail(s) correspond, the Receivable Account was renamed Debit Account and moved after the Extended column, the Receivable Account description column was renamed Debit Account Description and moved after Debit Account, the Purchase Account column was renamed Credit Account and moved after Debit Account Description, and the Purchase Account Description column was renamed Credit Account Description and was moved after Credit Account. In addition, the Payroll Deduction column was removed and the Line Type column was added to accurately display whether each line is a sale line or tax line.

NS-1161: Removed the Fisherman Sale & Tender Resale Lines inquiry

Because the Sales Lines inquiry was created to show all sale lines from Fisherman Sales, Tender Resales, Customer Sales, and Employee Sales, the Fisherman Sale & Tender Resale Lines inquiry was removed as the data exists on the new report.

NS-1162: Removed the Sale Lines inquiry

Because the Sales Lines inquiry was created to show all sale lines from Fisherman Sales, Tender Resales, Customer Sales, and Employee Sales, the Sale Lines inquiry was removed as the data exists on the new report.

NS-1221: Improved the logic for assigning default Sold Conditions

Previously, when eLandings tickets were integrated without a Sold Condition, the Sold Condition on those tickets was being assigned by NorthScope but the Sold Condition assigned was not pulled from the preference for the default Item Sold Condition. This logic was improved so that when eLandings tickets are integrated without Sold Conditions, the Sold Condition that gets assigned is the Sold Condition selected for the preference ‘Item Sold Condition’ in the Purchasing module.

Sales Order

NS-1170: Updated the load builder process to include orders that have only non-inventory items

Previously, shipments were only created for inventory items on Sales Order transactions. This logic was improved so that shipments are built for non-inventory items as well so as to allow the approving and posting of Sales Order transactions with only non-inventory items, as before this was not possible. This is only applicable to transactions not managed by logistics.

System

NS-1088: Renovated Security for Security Groups, Forms and Controls

Security Groups were updated to better improve management of security within NorthScope. These updates include the items below.

• NS-1089: Added enumerations for Security Group Category

In order to better display each form available to security, enumerations for assigning a category to each form were created. These categories include Transaction, Master File, Setup, Configuration, Reports & Inquiry, and Other.

• NS-1090: Added fields to the Form table

In order to support the addition of security group categories, the column for security group categories was added to the database table that stores form data in NorthScope so that each form can be assigned a category that will display in the Security Group record view. In addition, a column was added to store the online help URL for the form so that if a help page exists for the form, the form name will display as a hyperlink that will bring the user to corresponding help page.

• NS-1091: Designed the Security Group List View

The Security Group List View was designed to display all security groups in the system with their Security Group name, Company, License Type, and the number of users assigned to the group. This list view also enforces that the Administrators security group cannot be edited or deleted.

• NS-1092: Designed the Security Group Copy Window

The Security Group Copy window allows the user to copy the security assigned to the selected security group and copy it to a new security group that will be created. The name of the security group being created defaults from the selected security group with ‘(Copy)’ appended to the end. In addition, the user can select the company to which the new security group will be assigned from the copy window. Once copied, the new security group can be edited.

• NS-1093: Designed the Security Group Record View

The Security Group Record View was designed to allow the user to create, edit, and delete security groups other than the Administrators security group. This record view displays each module’s forms that are available to set security with a drop-down to assign the security mode – Full Rights, Read Only, or No Rights. In addition, this record view validates that a form’s control cannot have higher security than its parent form and if it does, the record view corrects the security mode on save.

• NS-1094: Added the Security Group Mass Update

Mass Update was added to the Security Group record view so that the user can update the security mode of multiple forms and controls at once.

NS-1189: Updated the Module, Module Form, and Module Form Control tables and all corresponding scripts to improve the ease of use for assigning security

The Module, Module Form, and Module Control tables along with all corresponding scripts were updated to improve the user experience when setting up security groups. To improve the ease of use for assigning security, the following updates were made:

• NS-1190: Updated the Module table

The Module table sort was updated so that the System module appears first then the Company module and then all other modules sort alphabetically. This new sort is reflected in the order the modules appear on the navigation menu and the order modules are sorted in the Security Group record view.

• NS-1191: Removed unnecessary Forms from the Module Form table

Previously, there were old forms that existed in the module form table that were subject to security that had been replaced within NorthScope but the corresponding form entry had not been removed. Therefore, these unnecessary forms were removed. In addition, certain forms were removed in favor of becoming controls. This was done primarily for forms that exist in multiple places within NorthScope, such as Mass Update and Journal Details.

• NS-1192: Updated the Module Form table

The Module Form table was updated to include new columns, updated values, and more. The SecurityGroupCategoryEN column was added to categorize each form as either a Transaction, Master File, Setup, Configuration, Reports & Inquiry, or Other and the Online Help URL column was added so that any form that has a corresponding help page will display as a hyperlink that, when clicked, will open the corresponding help link. In addition, descriptions were updated to more accurately describe the form that is represented. The sort was also updated so that the items subject to security with sort first by module, then by their category, then forms will display in alphabetical order with their corresponding controls below.

• NS-1193: Updated the Parent Form Security when there is no navigate URL

The security for parent forms that do not have a navigate URL, i.e. they do not open anything, such as Setup under the Purchasing module, was updated so that if any of the children forms are granted access, then the user also has access to the parent form. Otherwise, if the user does not have access to any of the children forms, the user will also not have access to the parent form.

• NS-1194: Added missing forms to the Module Form table

Previously, there were forms in the Module Form table that were not subject to security so they were missing from the security group record view.  These forms were edited so that they now are subject to security.

• NS-1195: Fixed Read Only Security

Previously, read only security only worked for certain pages within NorthScope. This functionality was fixed so that it works universally.

• NS-1196: Added security for forms that can be called from multiple places

The forms for Mass Update and Journal Details were removed from being subject to security and the buttons that call each form were added as controls that are subject to security for each instance where they exist. Therefore, instead of assigning security to the form, which would give or revoke access to all instances of Mass Update or Journal Details, the user can now assign security to the Mass Update and Journal Details button for each transaction or list view it exists on.

Bug Fixes

Company

NS-1148: Corrected the module reference for sending message queue emails

Previously, when a message was created in the message queue, NorthScope was incorrectly looking for the emails to send the alert to in the System module’s preferences as the preference for ‘Email Address(es) to notify if inbound integration error occurs’ previously lived in the System module. This reference was fixed to correctly look for the emails to notify in the Company module’s preferences.

NS-1120: Corrected the module reference for the eLandings Management page

Previously, the eLandings Management page referenced the wrong module for the inbound exceptions hyperlink, which was causing an error to display when the user tried to open the inbound exceptions record. This reference was fixed so that the page now correctly references the Company module.

NS-1203: Corrected the Outbound Integration record view

Previously, a bug existed that caused an error when the user tried to open the Outbound Integration record view. This bug was fixed so that the Outbound Integration record view now opens correctly.

NS-1218: Corrected the storage of Reason Codes & Notes

Previously, the reason codes created in CompanyàReason Codes & Notes were not all being stored in the same table for reason codes. This caused an issue because some transactions that had reason code capabilities did not have reason codes to choose from, even though they existed in the database. This issue was fixed so that all reason codes are stored in the same table and all transactions that are eligible for reason codes look to that table for their corresponding reason codes to choose from. 

NS-1229: Corrected the module reference for the Inbound Integration list view

Previously, the Inbound Integration list view pointed to the System module when trying to open the Inbound Integration record view from the corresponding hyperlink. This caused an error since the Inbound Integration record view lives in the Company module. Therefore, this issue was fixed so that the Inbound Integration list view points to the Company module when trying to open the Inbound Integration record view.

Commodity Procurement

NS-1127: Required a Harvest date and a line selection on the New Commodity Ticket window

Previously, a bug existed that caused the Harvest date and a line selection not to be required when creating a new commodity ticket from the New Commodity Ticket window. This was an issue as the Harvest date then defaulted to 1/1/2001 and because a line item selection wasn’t required, the fields that default from the line item were blank and not editable. This bug was fixed so that these fields are now required.

Framework

NS-1122: Corrected the Sales Order Transactions list view Search box to clear reliably

Previously, an inconsistent bug existed that sometimes caused a search value entered in the Sales Order Transactions list view Search box to remain even when NorthScope was reloaded. This bug was fixe so that when NorthScope is reloaded, the value will reliably clear.

Inventory

NS-1142: Updated textbox user-defined attribute fields for items

Previously, a bug existed that caused textbox user-defined attribute fields on Item record views to expect numeric values, thus causing an error when the user tried to save non-numeric data into one of these fields. This bug was fixed so that all textbox user-defined attribute fields allow the user to save both numeric and non-numeric data.

NS-1153: Corrected functionality for duplicate items being saved on Inventory transactions

Previously, a bug existed that caused lots to be incorrectly affected when duplicate items were saved on inventory transactions. This issue was fixed so that upon save, duplicate items are combined into one line item on Production, Adjustment, and Receipt transactions while Transfer transactions do not allow duplicate items to be saved.

Logistics

NS-1235: Fixed issue with saving Notes to Load record views

Previously, a bug existed that caused an error to display when a Note was attempted to be saved for the Load record view grid. This issue was corrected so that notes can be saved without error.

Purchasing

NS-1071: Fixed a bug with eLandings landing date integration

Previously, there was a bug with the integration of landing dates from eLandings as the UTC offset was being factored into the calculation of the date, converting the ticket date to the day after the intended date. This issue was fixed so that the offset value is not included in the calculation of the date.

NS-1129: Updated Delivery Tickets to round all extended amounts to 2 decimals

Previously, a bug existed that caused extended amounts on Delivery Tickets to expand beyond 2 decimal places. This bug was fixed so that extended amounts now correctly round to 2 decimal places since they display prices.

NS-1166: Updated Delivery Ticket Item Reprice to remember manually entered new prices upon validating

Previously, a bug existed that caused the New Price value to clear on the Item Reprice screen when the user clicked the Validate button. This bug was fixed so that when a user enters a new price for an item and clicks validate, that new price will remain so that the user can process the reprice correctly.

NS-1169: Updated how eLandings import works with existing tickets in NorthScope

Previously, a bug existed that caused issues when importing tickets from eLandings that had duplicate ticket numbers. This bug was fixed so that the following occurs when a duplicate eLandings ticket is imported to NorthScope, based on the NorthScope ticket’s status:

If the NorthScope ticket is…

• New: Update the ticket with all the new data and don’t change the status
• Approved: Update the ticket with all the new data and change the status to new
• Ready to Post: Create a correction for the max version of that ticket number
• Posted: Create a correction for the max version of that ticket number
• Void: Create a correction for the max version of that ticket number
• Deleted: Create a correction for the max version of that ticket number
• Replaced: Create a correction for the max version of that ticket number

NS-1176: Added self-healing to transactions that support sales tax

Previously, a bug existed that prevented the sales tax on transactions to update when a line item was updated to be taxable or not taxable. This bug was fixed so that if an item on a transaction is updated to be taxable or not taxable, the transaction’s tax amount will update upon save to reflect the new tax amount.

NS-1183: Updated extended amounts of line items on Purchasing transactions to round to two decimal places

Previously, a bug existed that caused the extended amounts on purchasing transaction line items to round to two decimal places in the NorthScope interface but to remain unrounded in the database. This caused an integration issue as the unrounded amount would be sent to the host system and the host system would then round the value according to its rounding rules, which may result in a different value displaying to the user when comparing the host system’s transaction to NorthScope’s. This issue was fixed so that the extended amounts are rounding in the database as well so that the value that displays in the NorthScope interface is the same as the value that displays when the transaction is integrated to the host system.

NS-1201: Updated the way grades are assigned when delivery ticket line items are integrated from eLandings without a grade

Previously, a bug existed that automatically defaulted the grade on delivery ticket items imported from eLandings without a grade to ‘00’. This bug was fixed so that the Grade for these lines will default to the Default Grade setup in the user’s Purchasing Preferences.

Reports

NS-1224: Corrected the report install for data entity company

Previously, a bug existed where the report install script had the data entity company column and the display type column switched, causing the report install to always install into company 1 and set the display type for the report to the company’s SK value. This issue was fixed so that the reports get installed to the correct company and the display type is set correctly.

Sales Order

NS-1110: Corrected the Sales Program link on the Customer Address record view

Previously, a bug existed that caused the Sales Program link on the Customer Address record view to open a Sales Order Price List. This bug was fixed so that when the user clicks on a Sales Program link from within the Customer Address record view, the corresponding Sales Program record view will open.

NS-1146: Corrected Linked Price Lists to update linked item prices when the corresponding base price list items are updated

Previously, a bug existed that caused linked price list item prices to not be updated when their corresponding base price list item prices were updated until the linked price list is resaved. This bug was fixed so that when a base price list item is updated with a new price, any of the linked price list items that are linked to the base price list item will have their prices updated while still enforcing any formulas applied to the linked price list items.

NS-1175: Corrected the allocation procedure on Sales Order transactions to handle allocations of unit only and weight only managed items

Previously, a bug existed that caused issues when trying to allocate weight only and units only managed items on sales order transactions. This bug was fixed so that all allocations are properly handled on sales order transactions.

NS-1180: Corrected Linked Price Lists to update linked item date ranges when the corresponding base price list items are updated

Previously, a bug existed that caused linked price list item date ranges to not be updated when their corresponding base price list item date ranges were updated. This bug was fixed so that when a base price list item is updated with a new date range, any of the linked price list items that are linked to the base price list item will have their date ranges updated as well.

System

NS-1241: Updated system preference value lookup to ignore the module the preference lives in

Previously, the lookup for the preference values for enabling Report Data Access and Workflow Data Access only looked for the preference values in the System Module. However, these preferences were previously moved to the Company module, as the preferences are set by company. Therefore, the preference values were not being found and Data Access Groups security was not adhering to the preference settings for whether or not it was enabled. This bug was fixed so that the preference values are found regardless of the module they live in.