Discount on Add item to OE order
Currently the discount % is not exposed on the OEAddLineToOrder transaction in form studio. Form Studio now exposes the Agility Object Transactions that allow you to call captured objects. The Discount percent is exposed on the OE Order Line Create Agility Object Transaction.
AWE-Add ability to full expand /collapse setting on Group by
NEW: AWE - New grid toolbar options have been added that will allow you to fully expand and collapse Group By Rows, and remove Group By columns from a grid application. Highlight and select the "Group By" icon on the top menu. Here you can select to "Expand All" or "Collapse All"
NEW: Document Type Print function in Agility Designer
Enhancement: New Document Print method. Agility Designer > Transaction Definition > Button definition - a right click for transaction abilities will now show new option "Add Document Type Print" On buttons for printing. List of Document Manager Print Document Setup will display and allow user to select the document category/Name/Type. Updated print functions for PO Master Order List - Release\Print OE Invoice - Using "Add Document Type Print OE Invoice - OEINV" OE Billing- Using "Add Document Type Print OE Invoice - OEINV"
doesn’t seem to update the OEORDHDR_SQL table with zero for frt_amt
Symptoms: Agility Billing object update on frt amount and misc amount will not update if there is a value there and the user wants to reset to 0 and enters 0. The billing proceeds and it appears it works, but the frt amt and/or misc amount is not updated to 0. Wisys.OETrx.PostBillingUpdates now includes two properties ClearFreightAmount and ClearMiscAmount. When billing you can set these properties to True to clear the Freight and/or Misc amounts on the order header.
Ship stagging qty remaining does not change as processing order
Symptoms: Ship Staging form does not reduce the "Remaining" qty. The "Staging" transaction object for the inventory transfer is not writing the doc_ord_no or the line_no to allow the transfer to be associated to the order number and line that it was processed for and reduce the remaining Solution: New Validation added for Staging to look at what has been staged vs shipped - StageValidateOrderItem. Standard Ship Staging application has been updated t use this new validation.
Activity Transactions with Include Quantity with Backflush Labor
Symptoms: When entering a SF Activity Transactions with backflush labor on an M or Y Count Point and the "Include Quantity with Backflush Labor" is checked in SF Setup, the trx quantity is being included in the labor transactions of M and Y Count Point Activity Operations. It should only be included in non count point operations that contain backflush labor
PO - AP Voucher Create Error - Calculate Discount Amt Percent
Symptoms: While processing a PO Receiver To Create AP Voucher if the Amount is 0, the following error is returned; "Failed: CalculateDiscountAmountPercent: Nullable object must have a value. Solution: Warning message stating "Failed: Insert: Invoice Amount must be greater than 0" will be returned.
PS.PalletBuilderValidateItem Validation should exclude wspkglin records that are confirm shipped
The PS.PalletBuilderValidateItem does not excludes the pallets that have been shipped confirmed (Status 'S' or 'C') when calculating the QtyUnpacked value that is returned from the validation. If the pallets that where shipped are not excluded it uses the pallet line qty in the calculation which results in a negative qty.
Progression Item Master insert throws error when setting the user_dt
Symptom: Progression Item Master insert throws the following error when setting the user_dt - cImitmidx:Insert:ProcessSQL :Failed to convert parameter value from a DateTime to a Int32. The date should be formatted as integer for Progression databases Solution: The date insert into a Progression database not formats the date correctly
Handheld Default MFG Stage Bin lookup not pulling from both SF and POP Stage Bins defined in Agility Options
Symptoms: The Default MFG Stage Bin lookup on the handheld is pulling only bins set up as POP Stage Bins in Agility Options. The lookup should also pull bins defined as Shop Floor Stage bins. Solution: Include SF Stage Bins in lookup
Error:AddNewForm:Culture is not supported
Symptoms: Trying to Open OE Pick Management Findings: Language Code is set to '0' on existing users, changing to valid language code ('en_US') resolved this issue. Resolution: Need to add something to update to update existing user records with a valid language code. Adding new user the value is correct.
Shop Floor Work Center reporting the Shop Order information does not fit in the field making it hard to read the description.
[Ronald Cortes 02/09/2018 06:42 (GMT -05:00)] When using Tablet mode for Shop Floor Work Center reporting the Shop Order information does not fit in the field making it hard to read the description.
AWE - Layout editor for List view - unable to get out and back to main view
Issue: AWE - Layout editor for List view - unable to get out and back to main view. Only way to get out is to close the web interface or select bookmark to reopen of web browser Solution: Able to exit column editor and returns to main list screen
PO Receiver to Create AP Voucher doesn't validate entered Terms code.
To duplicate this Use the PO Receiver to Create AP Voucher grid. Select A PO to voucher. Notice when the Voucher screen comes up that you can enter anything you would like into the Term field and it will be accepted. Basically allowing a non-existent terms code.
SF Material Issue error when items have an apostrophe
Symptom: A Macola ES Material Issue / Material Return with an apostrophe in the item number creates a malformed sql statement during the insert to the MCDISFIL. Class will be updated to correctly use a parameterized insert statement. Solution: MCDISFIL insert was not using a parameterized query. This issue is specific to Macola ES. Progression used a parameterized insert. Code update.
Default Order Header Profit Center and Dept
Symptom: the OE Order Header Create Object was not placing the profit_center and dept fields in oeordhdr_sql, in a Macola setup where the System/Package Settings/Distributions/Order Entry/Profit Center Usage O=Ord Pft Ctr Solution: [Bryce Lester 01/08/2019 15:03 (GMT -05:00)] Profit Center and Dept will now default from the artypfil based on the customer type when the Profit Center Usage is set to O. Validate in both ES and progression. Code updated in 568 3.0d Wisys.oe.v4.1.dll [Randy Peabody 02/28/2019 14:33 (GMT -06:00)] Tested and verified that in this Macola oe setup scenario, we now properly place the profit_center and Dept in oeordhdr_sql
Changing settings in Agility explorer for the SQL timeout is not working.
[Ronald Cortes 11/28/2018 16:29 (GMT -05:00)] Changing settings in Agility explorer for the SQL timeout is not working. Transaction will time out at 30 seconds even if setting is changed to greater than 30 sec.
values not showing as decimals on passed variable to a user enter field
[Angela Wilson 12/12/2018 12:32 (GMT -05:00)] I am creating an Agility grid for Olympic Forest Products and have ran into a couple of issues. A button on the grid calls a SQL script to capture some data in a table. To capture this data, some of the parameters for the query are set to “User entered”. I have a validator for input for the @new_loc parameter, but it doesn’t seem to be working properly. The value in my screen-shot below is valid, yet the validator does not accept the value. As well, I have added some form fields to show the old values from the view, however the values for Price and Cost are being shown as integers but should be decimal. Attached is the Agility project and a SQL script to create a supporting table. Run the “Credit-Rebill” grid, select an invoice from order history. Then, select one of the line items from the detail grid and click the “Edit Item” button just above the detail grid to bring up the “Edit Item” grid.
Can't use the sRtnOrderCreated variable on email subject or email body
[Angela Wilson 12/12/2018 10:26 (GMT -05:00)] When using Crystal report transaction for a Purchase Order creation in Agility Designer and selecting email as the print method, the user is able to use the “sRtnOrderCreated” variable for the PO# report parameter. But when referencing that same variable in the @EmailSubject or @EmailBody, it shows as [@@@sRtnOrderCreated] instead of the actual PO#.
Agility Web Role setup - button security - Add all button to select all child buttons
Symptoms: Agility Web Role setup - button security - Add all button to select all child buttons Solution: A "Select All" item highlighted in blue as been added to the top of the "Non-Menu Applications section for the Agility Web > Components that grants security for the buttons attached to applications.
Form doesn't allow additional actions if a Close Action has already been defined on the button
Symptoms: Form studio doesn't allow additional action to be added if last action is close action. Step must be removed and added back in after additional action is added. Additional Actions can now be added if a Close action already exists in the Action sequence. Solution:
FW: Desktop Printers users do not show because a document name has an apostrophe.
Symptom: If a document name in any area of our wsdocuments table has an apostrophe in its name, The Desktop Printers assignment screen shows no users to assign printers, thereby fails to allow Assignment of Desktop Printers. Solution: Code query was changed to account for an apostrophe in the name of the document.
OE Order Line Import defaults all customers to allow backorders
Issue: Using the OE Line Import Agility transaction will always default the customer to allow backorders. The oeordlin_sql.bkord_fg and oeordlin_sql.qty_bkord_fg will default to Y for customers that do not allow backorders. Solution: Updated to properly create BO setting on order line to follow with BO setting on Customer/Item Master files