Laddawn.com : Open-closed issue archive (5/20-5/22, 9 am)

Create a WEB.SPECAS.VALIDATE program that will pass this info to back to site via RESET.FLDS/RESET.VALS.

Also check VCI Blue validations to make sure it is also defaulting the color/opacity.

Spaces in the name are underscores in the first instance and missing in the second instances.

Please align the parenthetical statement as indicated by red vertical line.

Made on Demand text wraps below the "Made on Demand" header. Put a line break at the start of the 2nd sentence and center both lines vertically.

SP: In addition, there should not be a hyphen between the category and the product type (Layflat-bags).

Please make enabled "All" text in widget black (#000). Right now it uses #666 gray and looks disabled.
These are choices for Sizes and Gauge. 

Please keep gray/disabled version of "All" text for disabled entry fields.

Did not do exhaustive testing, but we are not getting marketplace results when we should be (according to Judy). Dimensions showing in widget should produce an exact MOD match.

Saved Item/Tagging layer has text issues.

1. "Tag and number your item" header is too small. Should be 18px bold. Currently 16px. Please left align it with subheads.
2. Link colors are incorrect ("Cancel" and "Create New". They should use our standard blue link color of #0f57c2.
3. Sub head text size is too large. All 3 (Tag by use, tag by location and Add items...) should be 14 px
4. Entry field "Search all locations" text is too light. Should be #666666.
5. Entry field text is too close to the left border. Please move over by 10px.
6. "Add" button should be 16px Scala Sans Offc Bold. It is currently Arial.
7. Make same change from #6 to the "Save" button as well.

Label colors in results for Item, Available, Freight and Total are using the color #5a6d7a.

It should use the #666 gray color. This goes for the expanded labels as well (Materials Additives, Color, construction, Printing, venting)

Current header on staging server.

Correct header from design.

Try entering a FURN bag - 60x48x1.6.  Packaging defaults to 'Rolls'.  The FIND shows the first MOD result as 'Rolls' instead of 'Rolls, Boxed'.  This affects the MOD price, which won't include the boxing upcharge (so Boxed and Cradlepacked results have same price again).

*** John may have already fixed this.  He asks that you try it on your machine, and if the problem has gone away, then the next deploy should take care of it.  If you still see an issue on your machine, please investigate further.

Cannot add saved MOD to cart.

Ed: Issue corrected and will be deployed Mon - 5/19, afternoon.

SP, 5/21 - Now am unable to add either a fresh or saved MOD to cart. Can still add stock to cart.

Typo in Material & additives menu

Ed: Issue corrected and will be deployed Mon - 5/19, afternoon.

SP, 5/21 - fixed.

Shows when UVI/UVA expanded - should be 'agricultural'

View alternatives not displaying when selected from the bundle.

Janice 5/21:  delimiter has been corrected, closing

Standard Braks are all 0.00. This was working a couple days ago.

Fresh MOD availability link date does not match what's in pop-up

Sal 5/15/14 17:28 - Per Jim :

Guys – let’s not do any more work on the Availability Popup bugs at this time.   We need to regroup and get straight on what we really need to happen.

Date of 5/29 in pop-up does not match link date of 5/22. I did not change anything with the result quantity or anything else before opening pop-up.

Same thing with saved/numbered MOD a few moments later:

Stock availability date/link not updating with change in quantity

Sal 5/15/14 17:28 - Per Jim :

Guys – let’s not do any more work on the Availability Popup bugs at this time.   We need to regroup and get straight on what we really need to happen.

I increased stock quantity to trigger an availability pop-up with split shipment options and noticed that the availability date itself is not matching the plus-72 hr. date in the popup.

Funky things happening with mismatched zip pop-up.

Chuck: I was able to reproduce Example 1. The issue is occurring when the user triggers a dialog pop-up that has Yes/No buttons first and then triggering a dialog pop-up that does not use the same Yes/No buttons. To reproduces, do to a shopping cart and delete an item. This will cause the 'Delete Cart Item' dialog to appear with the Yes/No buttons. Then go back to the Shop Tab, select a category and then search with a different Ship To zip code. This will trigger the 'New Cart?' dialog and the Yes/No buttons will linger.

SP, 5/21 - fixed, closed.

Example 1 - Too many buttons!?
May be hard to recreate; I couldn't recreate it a few steps later. I don't have screenshot or notes on what I did to get this. If I come across it again I will update this.

Example 2
Now getting correct pop-up (attempting to recreate example 1) I clicked OK with delete current/start new selected. Nothing seemed to happen - pop-up did not close. So I X'd out. Got spinner. Waited 2 minutes. Closed out of browser window, reopened. Clicked cart tab; cart was empty.

Example 3
Getting error message I should not get. Note - this red msg is fleeting, so I didn't grab it the first time I got it. The first time, I swear to the verbiage different - it said something like "Cart 2916 is already saved you can't save another cart under that name" - but this was not "another" cart. I got this error with the first choice selected, after clicking OK.

Checkout Shipping Bundles always displaying shipping from Sterling even when shipping from an alternate warehouse (Sterling is hardcoded).

Janice: 5/15 10:16 After discussing with Ed, we determined that the warehouse name is returned; updated RPC$SHIPMENTBUNDLING_GETBYFILTER (& Judy's copy) to return WHS.NAME

Ed: 5/15 - Corrected issue.

Janice: 5/21/14:  this has been working, closing out

Bundles incorrect when more than one item in cart & each completely available from different alternate warehouses 

Janice 5/21:  bundles display correctly

If there are two items in the cart & neither one is available from the primary warehouse but are fully available from the alternate warehouse but each is available from a different alternate warehouse, it only creates a bundle for the last item (ie, item 3200 for qty 10 is completely available from whs 02 & item 3175 for qty 5 is completely available from whs 06).

New cart button, 'proceed to new cart'  button not doing anything.

Ed: This issue has been resolved and will be deployed 5/19 evening.

SP, 5/21 - tested, closed.

I should be able to clear current cart and start fresh if I click this button. But when I do, nothing changes; cart contents still there.

Sales Order Creation records missing data 

Wayne - 5/19/14 :  On WEB orders, the hold code (SOHDR<76>) automatically gets set to "1".  Also, related to this, available to pick quantity (SODET<33>) will get set to null.

Sales order creation from web is missing information or contradicts data on the following sales order files (vs. what is created thru Avante) - see Avante order 109172A & web order 109171A:

SOHDR is missing the following information:  city, state, zip (<7>), domestic cost of sales (<11>), customer PO date (<13>), ship via code (<29>), term code (<51>), fob code (<52>), acknowledgement contact (<57>), current cost of sales (<127>).  Hold code (<76>) differs between Avante & web

SOHDR.USR:  credit card date (<8>) has / as value on web, c/s request packslip hold (<71>) set on web, c/s request lock (<73>) filled in on web

SODET is missing the following information:  domestic cost (<6>), description (<12>), domestic extension cost (<22>), pick quantity (33), current cost (<63>), current extension cost (<64>).  UOM (<2>) differs between Avante & web

Janice 5/20/2014: order header & detail still have incorrect tax information (seems to be related to when bill-to customer is a different state (GA) than ship-to customer (MA) - see WEB order 109227A); order header missing contact <8>, customer PO date <13>, & fob code <52>; header user has invalid code for label source (1); detail sales posting code <49> differs

Web discount in cart

5/12 (Judy) - UI s/b calling RPC$UTILITY_GETSESSIONINFO when contact logs in.  This has not been scheduled for programming yet.  Should be done soon.

Not showing 1% web discount.

Search - I got nothin

Sal 5/12/14 12:02 - This issue seems to be fixed, I couldn't reproduce. Please re-test.

SP, 5/13/14 - (~3:25pm?) I was able to repeat with the same parameters on the right (category, zip, dimensions, color.
SP. 5/15/14 - To further investigate the original issue, I went through configurator on live prod site and I am able to quote with these parameters - however, I must provide complete dimensions; I used  50 x 44 x 57 4 mil, and was able to quote as pink tinted gusseted bag on rolls.

Stock issue resolved (data issue -sp, 5/15). Also - based on a sample of 5 stock searches (entering stock number in banner, clicking "go") 3 searches (6360, 4094, 4096) produced the same issue  - scrunched up widget with blank results area; 2 (5800, 2525) produced legit results.

For the 3 stock searches that produced no results, the back widget did populate with stock item parameters correctly.

SP, 5/15/14 - Judy determined screenshot below is correct behavior; it has to do with draw-length validation - crossing this portion of the list. 
SP: Update a little while later (5/13/14, 3:45 pm):

While testing another issue (I needed to produce a fresh MOD for 161) , I got no results - but I noticed the Godzilla line appeared briefly in the white space and then disappeared (over the span of 1-2 seconds). Happened too fast to capture it. Trust me.

Sal 5/15/14 9:21 - John will discuss with Judy.

SP, 5/15/14 9:31 - Thanks. It continues to happen -this time with gusseted 11 or 13' W/all-D/all-L, 4 guage - I get nothin g.

  And with 11W/all-D/all-L, 2 gauge, I get this: I get no MOD exact match. Just YMAC stock:

Crossout correction - duh - I should not get an exact MOD Match with incomplete dimensions; but I should be getting someting like this, right? (Taken from specs so of course search details don't match):

Should validation error have prevented me from getting this far - or should search have yielded something else like "we can make that, enter complete dimensions"?

Please see edits below.

Please see edits below.

Additives validation error showing late.

Sal 5/12/14 12:56 - Per John (email):

"I will discuss it with Judy about improving the validation programs."

Choose Layflat -> Materials -> Check Metallocene -> Choose Anti Static -> AmineFree Pink

Metallocene gets disabled but its still checked and didn't get any validation errors and we should get a validation error here. If we click on UVI/UVA we now get the validation error but it's too late.

product name missing from MOD YMACs

Sal 5/12/14 14:52 - Judy will be taking care of this. "these have to be setup in CATALOG.CD.USR".

Judy 5/13/14 - Will speak with Owen to see how he wants MOD generic name codes assigned.  Stock generic names are not as detailed as the category.  For example, if entering a 'Gusseted' bag (category 102), the exact stock match would show BAGS as the description, not GUSSETED BAGS. 

 "Bags" missing after comma in the 2 ymac results. Is this an Owen/Cliff/Tom issue?

404 error on availability date

SP, 5/21 - seems to have resolved itself. Closing.

While testing fix on issue 101 (availability popup), clicked avail link for item that was already in cart - see box below. Got 404 error. Had to add another "fresh" item to cart in order to test issue 101 . (Logged in as sparker.)

Validation issues in Comments Maintenance (SYS9012)

Janice 5/2/14 9:25am: changes have been made & ready for testing

Judy 5/12/14 - 1-5 tested and look good.  Added #6 and re-opened.

1. Only prompt/require Input Format1 if Screen Prompt1 # "".
   1. 1. 1. 1. Only prompt/require Input Format2if Screen Prompt2 # "".
2. F5-Web Info: Validate that Range Max, if entered, is >= Range Min
3. F5-Web Info: LTL Upcharge should be optional
4. F5-Web Info: Validate revenue charge code, if entered, in CHGCODE File
5. added 5/12: If revenue charge code is entered, validate that CHGCODE<4> (type) matches SYSCON CONFIG.SETTINGS.LAD<15> (strip off comment first).  Change F3 to only show the rev charge codes with F4 = CONFIG.SETTINGS.LAD<15>.

MADE ON DEMAND Box needs fine tuning.

Sal 4/29/2014 18:34 - This banner will show or hide based on whether we got something on the message back from the database. Will work with John to get this message to return the correct text.

Sal 5/1/14 11:07 - UI part is done. Wording needs to be changed in database accordingly. Please reassign to a DB programmer.

Sal 5/2/14 12:41 - Additional info: "RPC$MODITEM_OPTIONAL" needs to be changed to accommodate requested message.

Janice 5/214 14:53 - message changed as requested

jbm - 5/15/14

1) The "made on demand" text should be placed to the right of the "box" and centered vetically.

2) The Godzilla message should be BOLDED and the "Show Me" link shuold be the same blue as "save" and "share" links.

1.) The Box shows up when the Status is "2" which means we cannot make it.    Also the Box and Message should show up when the Status is "1".  The message format needs to be changed as follows:

"We can make CATEGORY on demand.   Enter complete dimensions for pricing and availability." or

"We can make Gusseted Bags on demand.   Enter complete dimensions for pricing and availability."

jbm - 5/15/14

Some quotes have no operator in QUHDR<82>

Joe 4/22/14: Fixed OPERATOR and USR.ID fields on LDLIB RPC$MODITEM_CREATE and BP WEB.CREATE.QUOTE.

QUHDR<82> should contain either the c/e rep's SB User Id (if OPERATOR # "") OR should contain "WEB" (if OPERATOR='').  Not all quotes have this info filled in.

I emailed you a snapshot of the code ... I think you are overriding the named param OPERATOR to "WEB".  OPERATOR should never be changed and should never be "WEB".  The UI side is carrying this around only if ce is logged in on behalf of a customer.  Please change the variable in your program so you don't destroy the contents of this named param.

Test

Going into saved cart with unsaved active cart never gets you into the saved cart

ED: Judy, please retest, can't seem to recreate.

sp, 5/21/14 - closing issue, not happening for me either.

Extra tooltips (same as issue 93).

SP, 5/6/14- I am still seeing all of the tooltips.

SP, 5/7/14 - while testing another issue today (101), I happened to noticed that the tooltips are all "delete cart item."

And moments later, they were empty:

Please test after next deployment

SP, 5/13/14 - reopening. This is fixed for all tooltips noted except the last "Delete item from cart ( X )"

SP, 5/21 - fixed, closed

Please eliminate the tooltips that appear when you hover over:

• Availability
• Price breaks
• Save
• Share
• Delete item from cart ( X )

Please KEEP the tooltips for the 3 buttons in the top corner (share/new/delete) - for example:

Can no longer add a MOD item to the cart from results

SP,  4/22/14 -  this issue appears to be resolved.

Regardless of whether it is a new MOD result or an existing MOD Item but a new Quote, the following error appears when you click 'add to cart' button "Has already been added to cart "Thursay".

"Non-standard" product details should show in results and are not.

4/24 - Shop widget has details of the extended description.  We need to review with you what is needed. Susan will provide an example.

Sal 5/8/14 08:46 - Should be all set, please test after next deployment.

SP, 5/13/14 - All "non-standard" details should show, not just full gauge. In this retest, fulll gauge showing, but not color detail . (Also see my 5/13 testing notes on issue 79.) Reopened.

Sal 5/14/14 16:31 - Should be all set, please test after next deployment.

SP, 5/16/14 - This is a big improvement; however, see issue 30. We're still not showing special packaging choices (slit gusseted/bags folded in half). Also, some small inconsistencies in use of punctuation. Let's discuss next week. Reopening.

Details like full gauge and color should show in description (along with anything else that's non-standard). This is related to issue 79.

Should be able to undo-anti stat, other pct.

Sal 5/8/14 15:57 - Fixed when Chuck was working on bug #43.

SP, 5/13/14 -  Reopening.   I can change material back to standard only if I backspace over my erroneous antistat %. That's an improvement, but don't think that is as intuitive as it should be. Even if my intention is to revert to standard (or some other material where this error is irrelevant), I still either have to backspace, or change the % to something between 1-10 as though I were still interested in antistat.  Clicking in standard radio button or even clicking reset still give me this error. If possible, I think the user should be able to click reset or click to another material that renders the error irrelevant. If this is a major programming effort to address, we can learn to live with it for release 1, but we should log it as a future fix.

After getting the validation error for entering antistat % outside of allowed ranges and clicking either X or OK to get out, the only way to get the error to stop reappearing is to enter a % between 1 and 10. That's fine if I am determined to get this antistat, but I cannot select the default "standard" to undo my anti-stat selection. I am barred from doing this, even after clearing the field with the erroneous %. I can only go back to standard material by entering a number in antistat % field between 1 and 10.

Sal

Chuck

Fix to issue 68 caused problem with abbreviated product names

Sal 5/2/14 14:41 - Need to apply formatting rules to "Mills" or "Mics" only.

"C&A" is now "C&a"; "LD" is now "Ld" - acronyms/initial cap abbreviations should remain all caps.

Please re-work the logic for the Wooden Slat comment in create orders.  You are using SHOP.PKG, which is a shop widget variable that isn't available during checkout:

1. As you are going through the bundles, identify whether this is a MOD bundle that has export pallets selected.  If so, read the packaging info from MOD.ITMMST.USR<43> using the MOD Item# in the shopping cart.  For that bundle/order, you can use the boxed or cradlepacked comment (you may find either 'Boxed' or 'Cradlepacked' in MOD.ITMMST.USR
2. For a stock bundle, you can assume that you are using the 'cases' comment# (because we don't cradlepack stock items).  So if export pallets was selected for this bundle, use the 'cases' comment# on the stock order.

Stock price breaks

4/24 - In results area no quantity break pricing is done. It is done in the cart so all items can be considered.

SP, 4/25

I understand your logic (and in hindsight, our specs are not very detailed on this point). However, we think quantity price breaking does need to happen in the results area. Specifically, using the 3/25 example:

• In situations where there are 0 stock items in the active cart, if user increases quantity to 5, the unit price should  change from $60.30 to $54.81 (and the total cost = to 5 times that).
• In situations where there are items in the cart, those quantities should be taken into account; so if there were 5 items in the cart, the price should go to $52.20 (and total cost to = 5* that).

If nothing happens, the user will not be "rewarded" for choosing a larger quantity; they may even hesitate to add the item to the cart (to see the hidden reward of lower pricing).  Again, we get your logic. Either way, there's some potential confusion about pricing, but we believe this approach is the least confusing, and the most conducive to getting the sale.

5/5 - Meeting with Cathy, John, Judy and Sal.  This is not a bug.  It was programmed as designed.  John will come up with hours to make the change and add to the timeline.  It will have to be determined if it will be done in phase one or two.

SP, 5/13 (see also email from 5/7)

There is no need to come up with hours etc.
After discussing with Owen, we decided on simpler approach - lets tack some text on to the last sentence:

"Discounts will be shown in the cart."

This extra text should only part of the pop-up when it is accessed from a result, not from the Cart. If this is not possible or requires a lot of effort, we’ll just live with it as it is and consider for phase 2.

The fake customer we are testing with has stock price breaks...

... but when I change the quantity from 1 to 5 for this item, the total reflects the original unit price x 5, and the unit price on the far right does not change.

Tried this with a few stock items, results were consistent.

Full gauge in description

Sal 5/8/14 08:46 - Should be all set, please test after next deployment.

SP, 5/13/14 - Almost, not quite ...

Font for "Gauge" should be gray like "Item" and "Available" - I am sorry, it is confusing. The specs were missing this piece. Image from 3/25 test is correct on color; image from spec below is correct in showing line for "Gauge: Full", but was outdated with respect to font color. Reopened.

Steve provided an up to date spec a couple of weeks back, but it was not shared widely. Here it is:

Sal 5/15/14 13:28:31 - Should be all set, please test after next deployment.

sp, 5/21/14

This is a search for a furniture bag; at 1 mil, validations forced me to set gauge to full. Result should include a line for full gauge indicator.

Image from test:

Image from specs:

No exact stock match, but there is exact MOD match

Sal 5/1/14 11:25 - Fixed please test.

SP, 5/7/14 - tested, reopening. The exact match is now appearing above "You might also consider" (good); however, there are still a couple of things wrong with this picture...

The MOD exact match should look exactly like a stock exact match - no yellow warning message, and please add back "Results" header - here's a mockup:

Sal 5/8/14 08:46 - Should be all set, please test after next deployment.

SP, 5/13/14 - So close! However, something happened to the YMAC heading; it's now black, should go back to being orange.

Sal 5/15/14 13:28 - Great catch! Should be fixed after next deployment.

sp, 5/21/14 - fixed, closed.

We have not spec’d a “no stock items found” message.

Here, 12x23 2 mil layflat bags in cases are appearing under the YMAC heading. They should not.

In scenarios where there are no exact stock matches, but there is an exact MOD match the MOD option should be displayed as an exact match. (Yes, even though when there is an exact stock match, that MOD exact match is demoted down to the YMACs.)

(The cradlepacked result is where it belongs under YMAC heading, with its own subhead.)

Results under the Shop Widget by 1/4 of an inch or so.  Move them down to match visual design 

Sal 3/28/14 13:03 - Fixed, please test.

Customer Numbers as Location Tags 

Joe 3/20/14: This has been tested and should be complete.

DB

There is code in RPC$MODITEM_CREATE  that is causing the setting of the MTO flag to be set to 1 ALL THE TIME. There is a comment that says the issue was related to the repricing. This needs to be brought back in, and fixed so it's not  a problem any longer. 

SHOPPINGCART.USR isn't being updated when CONTINUE from any screen 

ED: These steps are being updated one by one, Shipping Address is now persisting it's data to the shopping cart.

4/15/14 (Judy) - Data isn't being updated to SHOPPINGCART.USR until a screen later.  ie, I click 'save' on the address screen and no shipto customer/address is in the cart record.  When I save the bundling screen, I see the shipto customer/address in the cart record, but not the bundling info.  When I save the payment info, I see the bundling info and the payment info saved.  The label info is written as soon as I save the label screen. Please check why some screens update immediately and some there's a 1 screen lag between save and actual update.

MOD Item Exact Match in Results gets new MOD# when added to cart 

ECD: Janice completed the back end work, I completed the UI side and tested. This is now resolved.

I entered a 12x24x2mil layflat bag for Butler, which is MOD Item MOD1153.  MOD1153 showed correctly in results, but when I clicked 'add to cart', it created new MOD item 1155.  If PART.NBR is already assigned with a real MOD Item#, it s/b calling the create order using STATUS 2 (Existing MOD Item/New Quote), not a STATUS 1 (New MOD Item/New Quote). 

2/27/14 (judy) - Per John: If PART.NBR="MOD" then set ISSAVED = False.  This is only for MOD items.

3/11/14 (judy) - Ed will make sure that PART.NBR is sent back to the database when STATUS=2.  Janice will change RPC$MODITEM_CREATE to get the most recent quote# from MOD.ITMMST.USR<7> instead of from CONTACT.ITEM.XRF.USR when QUOTE.NBR = ''. Test plan PMI.CREATE.RP2 does not have a saved item, which is causing the problem with getting the last quote# to determine config.rev#.

In results, an exact match was found with a MOD item (MOD1140) that had a favorite flag (CONTACT.ITEM.XRF.USR<6>) of 0.  The MODxxxx item# appeared in results (even though you don't see it in saved items list).  When I 'saved' it from results, it assigned a new MOD Item# (MOD1153) to it insead of using the original MOD Item#.  How should MOD items not flagged as a favorite be handled? Should it have been assigned as an exact match, and if so, should it have set the active flag on the record when it was 'saved' from results?

2/27/14 (judy) - Research required:  Find everywhere that we are updating the CONTACT.ITEM.XREF.USR record (creating/modifying).  Note whether we are setting the 'favorite flag' in field 6 or not, and how it determines how to set that flag. John and I will let you know where to go from there.

3/10/14 (judy) - John and I have determined that Favorite Flag is no longer needed. It will be removed from dictionary and RPC$CONTACTITEM-GETBYFILTER, RPC$CONTACTITEM_SAVE, RPC$MODITEM_CREATE, and RPC$ITEMTAG_GETBYFILTER2. -Joe: done 3/10/14.

Changing quantity in widget results area for a MOD item returns an invalid Available Date

Do a search for 12x0x24x2mil Layflat Bag from the widget.  Returns a date of 2/24.  Change the quantity in results.  The avail date will change to 12:00:00AM.

02/21/14-I just noticed that new stock selection for Amber Ziptops - all stock items in this search have 12:00:00AM for an avail date.  Select 'Reclosables' and 'Amber' then FIND.  All 8 stock items are showing this weird date.

04/28/14 (Judy) - I tested and both look fine. 

05/13/14 (Janice) - need to verify that the available date in results area matches available date in cart as well as checkout shipping & packaging (bundle)

Re-Open

ProductModItem_GetByFilter / GetById need to return IsSaved value, currently item gets created everytime we open the Save Item popup since IsSaved is always False coming back from the Saved Items tab..

3/13/14 - JJP - Decided to go with changing the MODITEM_CREATE program, to check for the exact MOD item before creating a new item.  IF STATUS = 1 and an exact item is found change the STATUS from 1 to 2, set the PART.NBR to the found item, and continue processing.

3/14/14 - Joe: logic added, testplan MIC.EXACT confirms working as expected.

Return Custom Price Breaks for MOD items 

1/27/14 Joe: Quote# was not passed; Ed fixed and confirms now working.

SP, 5/15/14 - TESTING ON BEHALF OF JOHN. Customer-entered price breaks are not being preserved.  Steps to repeat: Customer contact 17279/cust # 2916. Return saved MOD1301 item to widget. Click price breaks. In pop-up change breaks to 15, 20, 25, click save, get success mgs; open popup again, see the new price breaks on right (good). Click share; share shows old price breaks, not new (in both internal/external views). Go back to results, new price breaks there. Click save, and save button in pop-up, success. Go back to saved items, re-return item to widget. Click price breaks link. New price breaks gone from pop-up. Would test from Cart but cannot at the moment. (Can't add MODs to cart.)

Printing Direction forcing Vertical when it shouldn't 

5/5 - Judy is reviewing.

When choosing the Static Bags category, there are some defaults happening on the database side that are appearing in the group description but can't be viewed when going into the Materials drop down.  I think we should work together on this one. 

5/5/14 (Judy) - I tested this again and same issue.  Once Defaults are done (right after category selection) you aren't able to see what was defaulted when you go into the Materials Menu.  You should see (and be able to change) all Anti Static sub-fields.  Same issue if you choose Layflat Bags, then go into materials and choose Anti-Static and answer sub-fields.  Once you leave that panel and go back in, you can't get into the sub-fields anymore.

SHOP.LFGUS null for Sheeting/Tubing

Sal 3/27/14 15:21 - This value will be obtained and used internally in Avante to avoid littering our objects. Please reassign to a DB programmer.

RPC$SHOPPINGCARTITEM_GETBYFILTER;  Items that are of type StockProduct are coming back with their FREIGHT property populated as “Included”, these should be coming back as “Free at $500”.

Sheeting Slit/Folded 

4/24 - This goes with bug 102.

Sal 5/8/14 08:46 - Should be all set, please test after next deployment.

Sp, 5/19/14 - issue 102 seems to be addressed, but not this issue; these special packaging details not showing in results. Reopened.

When I choose either sheeting slit (gusseted sheeting) or 'Folded Bags' from the packaging menu, neither show as part of the MOD item description when I click on the item in results.  Should they?

Zip Code Validation

Sal 5/2/14 10:48 - This seems to be fixed, please test.

This is only an IE8 and IE9 error.  Firefox works.

I entered a width and an invalid zip code format, then selected FIND.  I received zip code error message and fixed the zip code.  When I tried FIND a second time, I received an 'out of range' error message for the Length field.  I s/b able to leave this as 'All'.  This validation should not have triggered when the field is blank or All.  I had to enter a length before I was able to click FIND again. 
This occurs on every field.  You see error message before you get to the field to enter.

Can't 'reset' to start over once error box displayed.  'x' out of error box allows you to continue with invalid data.

Sal 3/26/14 21:21 - Reset now overrides validation. x out now re-positions focus on calling text box. Please test.

Judy 5/9/14 - The 'reset' now works if choose OK on validation error box then click on 'reset'.  But if I click on "X" on error box instead of OK, it still leaves bad data and lets me continue.

• Layflat Bags
• Width 10, Length 20
• Gauge 9
• Get error message that gauge out of range. I click OK.  Then I click Reset.  Won't let me out ... keeps giving me gauge error box.  I just want to RESET and start over.
• Also noticed if 'x' out of error box instead of 'ok', it allows you to continue with bad data in field.

Widget - Hovers Design

1. Change stroke to hover (and repeat for all hovers) to be (#DF7A1C). Decided on 1 consistent stroke color (3/2414)
2. Remove heavy drop shadow. Use drop shadow from #3 - Rolls cradle packed hover.

3. Make all hover text 13px Arial regular. Please double-check, it looks bold on my laptop.

Sal 3/24/14 - Fixed, please test.

Steve 05/19/2014 - initially it works but when you start adding Level 3 options, the shadow gets progressively darker.

05/19/2014 screenshot

Widget - make disable entry fields stroke (#CCCCCC), they are currently set to (#999999).

Please test after next deployment

SB (5/19/2014) - The stroke around entry field is still #999999 gray when disabled.
I tested this on FF and Chrome. 

Shop