Copying grid with buttons, if button has form defined the layout is applied to button in original and copied grids
Symptoms: When copying grid with buttons, if the button has a form defined any changes to the layout will be applied to both the original and any copied forms. This is due to the guid id assigned to the button not changing when copying the form and the forms layout being tied to the same button guid. Solution:
Closing a Grid that has a child grid on the detail section causes an error when closing
Closing a Grid that has a child grid on the detail section causes an error when closing: AssignDataSet:Error updating display:Object reference not set to an instance of an object. Error point:61.3
Log for tracking users who export
Symptoms: Requesting that instead of preventing users from exporting, we create a log of the export, logging username, date stamp and the SQL query used to create the data exported. Solution: Now registers in WsTrxLog table with related or selected export method
Request - change "Alert" title on top of grids to "Alert Key"
Request to change verbiage at top of grid when alert legend is shown. Currently reads "Alerts" and users see that and think that there is a problem in the data. Would like it to read "Alert Key" so it is less confusing for users.
Agility design studio enhancements in process grids and transaction designer
In Transaction Designer add a visual indication if a parameter or property has been set,Process grids, when grouping is enabled, add an option that prevents the user from changing the grouping and add an option so that the user can only click on the checkbox in the group header – disable the checkbox in the group’s rows (but still show checked/unchecked). ,For process grids, add option to enable/disable selection of a row’s checkbox
Add option to allow negative receipts, current forms must be modifed to allow negative number in PO Receipt form.
PO Receiving and PO Item Receiving now allow user to enter a negative receipt qty. If Agility is setup to autogenerate Lot/Serial Numbers, the users may have to clear auto generated numbers to enter a negative receipt of a specific Lot or Serial No. On the PO Item Receiving form, autogenerated Lot No must be turned off as clear button clears the whole form. At this time, logic is not being added to the form to allow Clear Stops to be used on the Lot and Bin fields.
Edit Control Type doesn't change after updating filter
This fix will adjust the edit control type to match and changes to a SQL script data type. It will still be necessary to go into the button definition screen to select that desired edit type. The fixes changes the datatype when loading the transaction definition screen. You will need to press the Save button when done.
WisysLauncherSysTray is not passing filter parameters
The WisysLauncherSysTray is not passing filter parameters from Macola Workspace to the Agility View. The Agility Filter Fields need to be supplied in the same order as defined in Design Studio. Filter Parameters need to be prefixed with -AP in the Workspace Action URL. If the Workspace does not supply prefix the value automatically then it needs to supplied when defining the Agility Launch URL For example: Manual 9999999|-AP{1}|-AP{2}
Pop Production Close Button doesn't work unless you add zero quantity
This issue has been fixed in both POP Production Forms. However, the user must enter a quantity and tab/enter through the quantity field AFTER making the checkbox selection. There is a validation that runs on the quantity field that checks the value of the checkbox.
Add Floating Package to Shipment Column 'Ship_To_Contact' does not belong to table
When adding a floating pallet to a shipment, you will receive an error “Shipment:AddFloatingPackageToShipment:CompareShipToAddressesByShipment:ComparShipToAddresses:cWsPKGLIN:ReadAllOrdersByPackage:Column Ship_To_Contact” does not belong to the table. ,Also receiving this error on Shipment Add Floating Inner Pkg
Agility Shipping - International Shipping button DBNull to type String error when opening
Receive error when clicking the International Button in Agility Shipping LoadData: Conversion from type ‘DBNull to type 'String’ is not valid.,UPS International Form will open after that. Upon closing you will receive an Object Reference not set to an instance of an object.
Agility Shipping Options Capture Producer Plugin
Design Studio Wisys.Options Project should be updated to include a new options screen for “Producers” or "International Producers" used when filing an international documents such as USMCA Certificate of Origin, etc.,The user control to be captured is Wisys.Options.v5.0.dll | ucAgilityShippingProducers,New WsOptionDetail record in Create WsOptionDetail.sql (Macola) and Load WsOptionDetail.sql (SAP),insert into wsOptionDetail (OptionsGroupName, ButtonName, ButtonText,SeqNo,Enabled,SecurityLvl,LicenseCode,BeginGroup,ExtraText,ProcessID),values ('AS-OPTIONS','Producers','Producers',71,1,50,null,0,null,'NEW_PROCESS_ID_HERE')
When a Default Carrier is not set in the Agility Shipping Settings an unexpected error occurs
When a Default Carrier is not set in the Agility Shipping Settings an unexpected error: Failed getting starting for EDI package types is thrown. Eliminated the error message by setting the Default Carrier to an empty string if it has not been set.
Agility Designer Format on SQL Script component throws an error that the statement can't be formatted
The format button will no longer throw an error on SQL Scripts that cannot executed/parsed into Schema based queries that are used with Grids/Process Grids. A message will be displayed stating that it cannot be properly parsed, but will allow you to continue.
User gets prompted twice for the number of copies
When selecting the prompt property in Document library, user gets prompted twice for the number of copies. Code to to honor the No of copies passed into the print method when bypassing the new Copies screen that was created for Desktop applications.
Progression LTL Shipments Clear City State Zip fields
A Progression LTL Shipment clears the wsPkgShipment Ship_To_City, Ship_To_State, Ship_To_Zip columns when writing back to the wsPKGShipment table during shipping. This prevents the order from being backed out and reshipped during validations.