Request to pass ShipRush Account number through SDK so end user does not have to manually select in ShipRush Interface
Symptoms: The customer's customer needs the FedEx/UPS tracking number on the label and the return address on the label to belong to the originating UPS/FedEx account number. Currently the only way to accomplish this is to use the Special Shipment flag and then select the correct 'From' account number from the drop down list at the top of the ShipRush screen. The request is to automatically pass the correct FedEx/UPS account number to ShipRush through the SDK so the end user does not have to select it.
Only 1 return label prints in ShipRush - new 1 label per package
Symptoms: ShipRush will only print 1 Return Label per UPS shipment. They need to print 1 label per package We cannot do this because the SDK interface will only print one label per shipment. We are changing this request to be able to do one return label based on individual Customers. The return label option is Global in the shipping settings. We are looking into being able to control this Global setting. If we cannot then we will have to reject this request. [bhollinger 03/09/2015 10:26 (GMT -04:00)]
Assign Order Number to iminvtrx_sql.doc_ord_no when Ship Staging
Symptoms: ship staging form does not write the Order number to the Doc_ord_no field in the iminvtrx table. The Staging object being used has an order no field passed to it but it does not write to the iminvtrx table. This leads to the inability to trace an issue back to an order.
Agility OE Pick Tickets Add properties to hide print message and hide order line status message
Symptoms: Added property HidePrintOKMessage to hide the "Did the pick tickets print correctly" message. Added property HideStatusMessage to hide the Print Status message from displaying.
Add IF NOT EXISTS option to Wisys Utility Script Builder
Symptoms: Add an option to include an IF NOT EXISTS query to the Wisys Utility Script Builder. This can be used by supplying a select statement to the InsertIfNotExistsSQL property. Example Wisys.AllSystem.ScriptBuilder.InsertIfNotExistsSQL = "Select count(1) from TABLENAME where Column1 = @Column1 and Column2 = @Column2"
Menu changes for EM10
Symptoms: When we insert into pwfunc the Option_exp value needs to be null. At the same time we insert into pwfunc we need to make inserts into two tables if not exists (select 1 from pwrole where role_id = 2000) begin set IDENTITY_INSERT pwrole on EXEC sp_executesql N'insert into pwrole([role_id],[role_name],[descr64],[rb_id],[job_group],[visible]) values (2000,''Agility'',''Agility Applications'',0,null,1)' set IDENTITY_INSERT pwrole off end EXEC sp_executesql N'insert into pwrprm(role_id,fnc_id,right_id) values(2000,fnc_id,2)
SF.IssueValidateItem when same component is on shop order more than once
Symptoms: When a SF Item has the same component multiple times in a build the SF Issue and Receipt validations will display a component selection screen. Two additional SF Validations will be added that will allow a component's build sequence number to be passed into the validation to avoid displaying the component selection screen. SF.IssueValidateItemBySeq SF.ReturnValidateItemBySeq
SFWCR error logging two employees in same shop order and same opp
Symptoms: When clocking in multiple employees in Shop Floor workcenter reporting application user receives error message that elapsed time does not belong to table preventing to have more than one employee clocked in to the same order and same operation
Non-Stock / Non-Controlled issue-auto select will double qty shipped
Symptoms: Pick Pack Options "Auto Select Non-Stocked/Non-Controlled Items" selected. If the item is added to the shipment in Pick Pack, when the order is shipped, it will double the non-stocked/non-controlled shipped qty if a shipper selects the non-stocked/non-controlled item to ship, when it is processed, the Ship qty will double on the oeordlin and bill incorrectly. Qty will double the qty to ship in the oeordlin_sql table. Qty does not double on the wspkglin table.
Update ForceFieldStop to overrride default value if alphanumeric key is pressed
Symptoms: The default behavior of the ForceFieldStop property requires you to backspace to clear out any default text. The default behavior will be updated to clear the value if an alphanumeric value is selected.
Shipping Tree requires bin but item is not binned when adding an Item OEORDLIN Bin_fg is null
Symptoms: Shipping Tree requires bin but item is not binned when adding an Item OEORDLIN Bin_fg is null to Duplicate make a non-binned item in the oeordlin_sql table null. You will have to do this through SQL. Macola intermittently does not write this field and it is null. Try to ship the non-binned item by adding to a shipment. Notice that it is requiring a Bin Entry.
ShipRush Stamps.com package weight not passing
Symptoms: ShipRush STAMPS.com - weight is entered in oz for postage and comes in at 0. When the user enters the weight and selects SHIP, they still receive and error "A package weights is required. Please enter a package weight". User must click ok, the shipRush screen opens highlighting weight, and user must enter the weight again. Screen shots attached
ShipRush Stamps.com unable to backout shipment
Symptoms: ShipRush Stamps.com - Unable to backout shipment. Error received: Backout failed:PostTrx:UnConfirmShipShipment:Error unconfirm shipping the shipment:Error trying to make a connection to Shiprush:Account configuration required (wizard dialog) but ShowLogin is disabled. call ShowWizard or set ShowLogin to TRUE
Agility Mobile Label Qty form should default to Quantity field
Symptoms: When printing a label that has the prompt enabled. The screen to enter the amount of copies does not have the qty on focus, instead the "ok" button is highlighted. The system should default to the quantity field with focus so the user can just enter a value.
Agility Mobile should prevent saving blank device name
Symptoms: When logging in to agility mobile the user was always prompted to enter a device name. If this value is left blank, any future logins also prompt for a device name and the system continues to create records in the device license table. The system should not allow you to enter a blank value for the device name.
When using the WiSfActTrx application to report against Shop Floor orders with backflush labor will not set the status to ended
Symptoms: When using the WiSfActTrx application to report against Shop Floor orders. If an operation has backflush labor checked the WiSfActTrx application will NOT set the status of the shop order to Ended after all operations have been completed and marked as completed. It will set the status to ended if no operation has backflush labor checked and all operations are marked as complete.
Progression multi currency issue for R/I item during a PO receipt.
Symptoms:' Loc_avg_cost, loc_std_cost,loc_po_price and adj_po_price are not writing correctly when using currency code on a PO receipt. To duplicate this create a vendor in Canada and set their vendor type to have a Canadian currency code. Create two po’s. One to receive with Macola The other is to receive using our PO Receiving Form. Use an item and note the std and average cost in Macola. use cnd currency code note the conversion conversion Rate(i.e0.751800 ) after doing the receipt notice these fields in the POINSHDR_SQL In The POINSHDR_SQL The Receipt trough Macola will receive with a converted loc_avg_cost , Std_cost and loc_po_price, and it uses home currency for the adj_po_Price. The second record is received through the PO Receiving form. It will use the macola avg and std for the loc_avg and std , but also converted the adj_po_price where Macola did not.
Reporting Negative Qty during POP Reporting calculates an incorrect adjustment to the allocation records.
Symptoms: When using POPReportProduction in FormStudio, and reporting a negative quantity, the allocation records for all components are being set to the exact same value, regardless of different qty_per in IMORDBLD file. To recreate: Create a POP order and report production for more than the original order, causing the allocation records to be deleted. Then, report a negative quantity to reduce the total report quantity to less than the qty ordered. Looking at the allocation records in IMINVTRX, all components have been assigned the same allocation quantity.
PO Currency Multily works but divide does not when doing PO Receiving on Inspection item.
Symptoms: PO Multi Currency Multiply works but divide does not when doing PO Receiving on Inspection item. The fields loc_std_cost, loc_avg_cost and loc_po_price in the POINSHDR_SQL table do not calculate correctly when using multi currency and doing a receipt of an inspection item using the divide factor capability in Progression..
POP Report FG on the guns does not honor Agility Option for Closing POP Orders
Symptoms: The Agility WMS form for POP Report FG does not honor the Agility - File - Options - WMS - POP Reporting - Order Completion Options. Form Studio needs to be modified to return the appropriate value to the variable designated for these values. The Agility Explorer WMS option "Over Production Warning" was set to use the string value in Form Studio and Agility Mobile. It has been updated to use the numeric value that's stored in the DB (0,1,2) vs (None, Soft, Hard). This is because any change in the description text would break setting variable condition.
Order Entry Tax Codes are not being calculated based on the Order Header Tax Code Percent
Symptoms: OE Tax Codes are not being calculated based on the Order Header Tax Code Percent. If the tax code percent is modified on the order the SDK tax calculations continue to use the original tax code percentage.
Agility PO Receipts - Same receiver number being used when passing to a SQL Script in a process grid
Symptoms: to duplicate use the PO Receipt Grid. Create an insert sql script to a table with one field( I create a table called _rec with a field called rec_no) Insert into _rec (rec_no) values (@rec_no) On the PO Receipt button transaction add this SQL script. In the method parameter use the variable ReceiverNoUser from the PO Receipt transaction. Now receive a few lines from the grid. Notice that the insert @rec returns the same receiver number for all the lines.
Getting warning on grids with linked components on update. - "Focus is not on a data row, please select a valid row on the grid."
Symptoms: Seeing the warning message, (Focus is not on a data row, please select a valid row on the grid.) show up every time focus is moved to the filter row of the parent grid with a linked component grid still open.
Agility Mobile add functionality to support negative receipts for serialized items
Symptoms: to Duplicate this, Create a purchase order for a serialized item using our form "Po Receiving" receive a qty of -1 of the item. When the serial lot collection box pops up notice that you should be able to select a serial number but any serial number will respond serial number already in use.
Agility Designer - on the button design properties, the Disable/Enable Rule does not appear to be working unless you are able to use an = or <>. If the criteria is set to contains, begins with, ends with - it is not reading properly
Symptoms: Agility Designer - on the button design properties, the Disable/Enable Rule does not appear to be working unless you are able to use and = or <>. If the criteria is set to contains, begins with, ends with - it is not reading properly and disabling the button.
OE Order Header Totals are zeroed out when an Update method is called against a Status 4 order
Symptoms: When using the SDK to update a status 4 header, the Tot_sls_amt, and other calculated fields becomes zero. This can be duplicated by creating a status 4 order and then using SDK OE Order Header update method.
wsPkgShipment-Backout Shipment resets Truck company to null but leaves Trailer and ProNo intact
Symptoms: When a shipment is backed out, in the wsPkgShipment table, the TruckCompany is set back to Null. The Trailer and Pro_No field remains the same and are not set back to null. Correct so that the TruckCompany does not get set back to Null to match and works the same as the Trailer and Pro_No
POP WIP Return object re-allocates the wrong amount on return
Symptoms: WIP Return of components with varying qty per values result in reallocating an incorrect qty on the second - nth component. The first components qty per value is used for all other components. To duplicate Create a pop order that has components that have different qty's per. Once created look in the iminvtrx table and notice that the components are allocated correctly. Issue the components to the pop order and again notice that the allocations are turned into issues correctly. Using the POP return form, return the issued components. Notice in the iminvtrx_sql that all issues are reversed out correctly but that the new allocations are both for the quantity of the first component. My example had issues of 20 for component 1 and 160 for component 2 upon return the allocations are now for 20 for the first component and 20 for the second component.
SDK Macola ES Customer insert fails when customer numbers exceed 10000
Symptoms: SDK Customer insert fails when customer numbers exceed 10000. A temp table is created during the customer insert process that provides 10000 customer numbers. If all of those customer numbers are used, a new customer cannot be inserted
Workcenter Reporting - Backflushing scrap Negative quantity
Symptoms: [rcortes 08/13/2015 18:18 (GMT -04:00)] When a user has reported scrap against an operation that has back flush materials assigned to it, The material qty for the amount scrapped are backflushed out of inventory. However if the user commited an error and wants to correct the entry by entering a negative number then the qty that was backflushed does not put the material back in to inventory.
IMLSTRX comments were not being retained on multiple confirm ship
Symptoms: To duplicate create an order using a lotted item. I create an order for an item called Lotted_item with a qty_ordered of 15. Print the pick ticket. Modify our Ship form, and on the save button, on the confirmship/serial/Lot Properties tab select any text field on the form to go to comments_1 Using that form Confirm the created order. In the lot section chose a lot but only confirm ship part of the order, I confirm shipped 5 of the first lot. In sql notice that the comments_1 field is populated as expected. Now select the same item to be shipped and chose a second different lot. I select 10 of another lot. In sql notice that the comments_1 field has now reverted back to nulls.
Non stocked items can be included and posted in inventory
Symptoms: Cycle Count allows non-stocked/non-controlled items to entered with an extra tag and posted. IM.CountByItemValidateItem has been updated to throw an error when a non stocked item has been entered. The SDK inventory count and extra tag methods have also been updated to prevent non inventory items from being added
Concurrency record not clearing when logging out of Agility Mobile
Symptoms: the concurrency record does not go away until the PocketESServer.exe form is closed. The concurrency record should remove on logout. To duplicate this use two guns login to one and notice the concurrency record. Login to the other gun and notice the concurrency record. Now try to log in as a different user on one of the guns. Notice that the currency record remains for the previous user. In this customers scenario, this prompt a license exceeded message because they only have two device license.
Pkg Package Add Multiple Pkg With Items Trx not available in Form Studio
Symptoms: The OBJ_TRX object available in the WiSys Object Transactions project called 'Pkg Package Add Multiple Pkg With Items' does not have an equivalent Transaction available in Form Studio. The 'Pkg Package Add Multiple Pkg With Items' object uses the AddMultiPackageWithItems method of the wisys.PkgTrx.PackageAdd class in the Wisys.PkgTrx.v4.1.dll.
Agility Mobile SQLBusinessTransaction times out if using selecting previous updated rows
Symptoms: Agility Mobile SQLBusinessTransaction times out if using locked rows. If the select statement of a SQLBusinessTransaction contains rows that were modified in a previous business transaction the query will time out due to not using the same transaction connection object.
The Selling UOM is no longer calculating correctly when processing a shipment in Pkg Pack and Ship. Worked correctly in 561, error occurs in 564.
Symptoms: When attempting to process a shipment that has an item with a Selling UOM, we receive the following error: "There was a problem with the Confirm Shipping process. Problem confirm shipping 26952 line 1 :CheckRules :60050 - The sum of detail Bin quantities Does not Match Header Trx Qty:Header qty=1000 - Detail qty = 100"
POP Order Create/Release updates
Symptoms: When assigning a customer number to a POP order that has multiple levels it is not being propagated to the dependent orders. Also, the customer was not formatted correctly. The ppordfil_sql.org_multiplier was not being written correctly at the parent level when released and was also different as compared to Macola at the dependent order level. Although the calculations were correct when creating / reporting exclusively in the SDK or Macola when reporting across the different mediums it could cause over/understated inventory transactions at the dependent level.
pick pack 4 issues
Symptoms: to duplicate Set Over Shipping to Hard in File/Options/Pick Pack/Shipping. Create a Macola order for any item for a qty_to_ship of 10 In PP4 create a shipment and add that order/Item to a carton with a quantity of 1. Then notice that you can replicate that Package past the qty_to_ship of 10. in my case I created 11 packages. On the other hand , after deleting all those replicated packages, try just adding one package with a qty of 11. Notice that you receive the Failed: You can only receive 10 message box. Honoring the flag in setup.
UpdateDisplay:Error getting view data:ReturnValues : The connection string property has not been initialized
Symptoms: When open Agility Designer, select Project > Copy Project - Receive error: UpdateDisplay:Error getting view data:ReturnValues : The connection string property has not been initialized
Overshipping at hard shipping kits calculates overshipping incorrectly
Symptoms: To duplicate this add a kit it to an order. Set over shipping to Hard ship the item in for the qty_to_ship PP4. You will get the message box that over shipping is not allowed. Notice that the sum for the line of the order is the sum of all component parts.
Error on any iff condition placed on a detail of a button in design studio
Symptoms: To duplicate If you go into the File Import component training and go to lesson 2. go to the buttons and on the create order button click transaction define. Click the if condition in the detail. You will get an error. HostViewGuid is neither a DataColumn nor a DataRelation for table.
Cannot add multiple items to same carton in PP4 without selecting add item again
Symptoms: When adding an item to a carton using the PKG Pack and Ship grid in Agility, after the first item is added to the carton, the screen closes and it returns you to the shipping tree where you have to choose add item again for that same carton to add a second item. The project was missing the repetitive transaction check box for the add item button. After that was enabled, the following error surfaced: "CommonValidated Failed:Conversion from type 'DBNULL' to type 'DOUBLE' is not valid. Error point 6.5"
Pick Pack 4 repetitive transactions on item add fails
Symptoms: Customer will not move to PP4 until they can repetitively add items from an order. John says this is a switch in the Repetitive transaction checkbox on the Add button in the Pkg PP4 Grid in the Pkg Pack and Ship Project. When this box is checked the clicking of OK button produces the error CommonValidated Failed:Conversion from type 'DBNull' to type 'Double' is not valid Error point:6.5
POP Reporting - not using Printer definations from Agility Explorer
Symptoms: POP Reporting desktop application is using report setup from within the application and not using the Agility Explorer Desktop Printers setting to define which printer to use and print settings. If multiple reports to print, no way to direct them to different prints. Also does not allow passing of printer size definitions.