Enhancements:

• Improvement to Picking List code to make customization easier
• The picking list form on the sales order object has been refactored (to improve the extensibility). This will make any customizations of the form in other orgs easier, as we no longer have to bring the whole code from the Ascent Managed Package when doing so.  The size of the serial numbers field on allocation lines has been increased to allow a large quantity of serial numbers to be allocated.
• The allocation line serial number field was changed from the text area to long text area to provide flexibility to allocate large numbers of serial numbers.  
• Improved alternate vendor functionality on purchase orders
• If the vendor on a PO line is the item alternate vendor, then the price on the PO line will come from the alternate vendor’s price.
• If you change the vendor on a PO by clicking the custom link Choose Vendor, a list of alternate vendors will appear, and after selecting one, the price on a PO line that has that vendor as an alternate vendor will change.  
• Quarantine Lot Movement Enhancement
• A new custom setting called “Move inv. From/To Quarantine Lot” was added. When this custom setting is turned on, the user can move inventory From/To a quarantine lot.  In addition, the user can also move inventory From/To Not Counted in Inventory locations.
• Reverse a Received PO line
• When a user receives a PO line in multiple activities, it will create multiple Received PO Lines records. Now, the user can reverse a received PO line by changing the type of the Received PO line record from “Receive” to “Credit”.
• Sales Order Lines View now correctly allows wild card search
• Filter Item Selection search criteria is now updated to use wild card type search, which will provide more efficient search results to the user. 
• Sales Order allocation working with “From Location”
• When the From location contains a value and “Force Pack from Location” custom setting is turned on, it will allocate the quantity exclusively from this location. And if this location does not contain the required quantity, it will create a backorder line to allocate it later when the inventory is available. If the From Location contains a value and “Force Pack from Location” custom setting is turned off then it will first allocate the available quantity from “from location” and then will allocate remaining qty from other available inventories. 
• New custom setting “Don’t allow mod BomComp Qty Complete PWO”. 
• Once the custom setting is turned on, it will not allow users to change the quantity on the Complete PWO page for components, if there are no split lines; when the split lines are created, the sum of all split lines of a component has to be the same as the required Qty. 
• New button to remove allocation lines for a sales order.
• The new button “Remove Allocation Lines” was added to this new release. It will open up a new page, where it shows all allocation lines for the sales order that are not packed yet, so the user can select which allocation lines to delete. There is a “Select All” option too.
• Reverse Work Order Line.
• We added a new button on the Complete Work Order page, it will allow users to reverse lines already completed. 
• Filter out inactive BOM versions
• When BOM versioning was turned on, and someone added a BOM type item to a sales order line, it would show all BOM versions, including inactive versions. We fixed it by making the sales order line BOM version field to only show the active BOM versions. 
• New custom setting “Disable CaseActions Trigger”
• When the custom setting is turned on, it will entirely disable the execution of the CaseActions trigger. Recommend for orgs that are not using the Ascent Return object.
• The CaseActions Ascent trigger does not perform any update on the Case status that triggered it. It is exclusively an “after update“ trigger (not executed on case insert, or before case update), and the only purpose of the actions are on any Returns (Ascent Return__c) related to the Case. If an org is not using Ascent Returns, the trigger was doing nothing other than performing a useless query on the Return object. That’s why we added this custom setting to stop this query. If an org is using Returns and the query finds any Returns associated with the Case, it will try to update Ascent Return status, based on the updated Case Status accordingly. 
• Delete all Historical Inventory with a button on the Historical Inventory page.
• We added a new button “Delete All” on the Historical Inventory page, so the user can use that to delete all existing historical inventory records for the selected date; or it will delete all existing historical inventory records when the “Date” field is blank. 

Bugs fixed:

• Allocated quantity on the item locator was not being updated properly from the Production Work Order (PWO).
• Bug in Ascent Main where allocated quantity on item locator was not updated if the location on the BOM depletion line was updated after the BOM depletion line was created. This bug is fixed in this release and allocated qty on the item locator will update and the location will be updated on BOM depletion line too after the line is created.
• Picking List not sensitive to lot/admin settings for sort order
• There was a bug where the picking list is not respecting the Ascent Admin Setting while showing the available inventory locations/lots. This is now fixed in this release. Picklist will now use the Lot settings from admin settings to sort lots. For example: If the user has FIFO selected in admin settings, lots will be shown in FIFO order. Same for the other options available in that setting. 
• Bulk Move-Item visualforce page is not working properly with serial numbers, and not respecting the entities when entities are turned on 
• This bug is now fixed in this package. Now the page will ask the user to enter the serial numbers if the item is serialized and also will consider the entity setup when moving the items, which means the user cannot move the items to entities for which they don’t have access. 
• PWO Build for > 200 BOM Components causing lot average cost issues as well as Null Pointer exception
• There was a trigger problem when building a BOM with more than 200 components as it tried to update the lot average cost twice for all component lots and ended up with a “Null Pointer” error. We updated the codes in the PWO completion trigger, so when there is a large PWO (more than 200 components), it will execute a batch class to complete it. 
• Qty On Order on item master being null causing Master Planner error
• It showed “Argument cannot be null” error on the master planner when trying to create PWO and if that PWO required to create purchase orders for the components. It is now fixed.
• Credit Memo description and price fields not showing properly
• While creating a credit memo from the sales invoice and if the items on the sales invoice contained a long description, the description was not wrapped properly. This issue is now fixed.
• “Allow multiple items with the same name” custom setting is not working properly
• This is fixed in the package. Now, it provides flexibility for the user to create a new item with the same name as it already exists in the system when this custom setting is turned on. 
• Item Family substitution error when first substitute item has partial quantity on hand
• “Run Substitution” button on the production work order didn’t substitute the quantities properly from the available items. The issue is now resolved. 
• Lightning interface issue - when the user edits the sales order line and saves the line, it is showing the blank screen. 
• The issue is fixed and it is now redirecting it to the sales order header page.
• Date format not respecting user locale:
• Date format in the ATP Calculator visualforce page was not respecting the user locale. It is fixed now.
• Date format for two fields “Requested Date” and “Delivery Date” in the lower section of the Sales Purchase Planner page were not respecting the user locale. It is fixed now. 
• Too many SOQL Queries On Processing RMA
• It happened when there were too many RMA lines. The code has been improved to get rid of the error.
• Exporting “View BOM with Costs” to Excel with data mismatching columns. 
• It only happened when the custom setting “Use Cost(4 dec) on Item Master” was turned on. Some data were mismatched to their columns. It is now fixed.
• Available to Promise field on item master not being updated properly after some PO’s were canceled. 
• It happened with the custom setting “Use ATP by Location” turned on.  “Available to Promise” = QOH - Allocated Qty + Quantity on Order, where “Quantity on Order” should only count open or partially completed PO’s, not the canceled ones. 

Known Issues:

• When custom setting “Use Return” is on, and “Use Returns And Cases for RMA” is on, and after the Return is completed, the case will be completed too, but the case status still shows “New”. The workaround is to manually change the status of the case to “Escalated” or “Closed”. We will fix it in our future release. 
• There is a minor issue with our new feature of Reverse Work Order Lines. After all work order lines are reversed, WO header status still shows “Complete”. The workaround is to change it to “Open” manually. We will fix it in our future release.
• In Lightning mode, adding new sales order lines or new opportunity lines by using the “Add Lines by Group” button, after saving the line, it will not jump back to the sales order page or opportunity page. A workaround will be switching to Classic mode if you need to add lines by item group. We will fix it in our future release.