Laddawn.com : Open-closed issue archive (as of 5-14)

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).

Customer preference routine returning incorrect preference for  ship-to back order handling preference

Janice: 05/14 14:00 tested, correct preference is returned

Order Confirmation not displaying after place order in checkout summary

ED: Corrected and deployed to staging.

Janice: 5/13/14 16:34 - tested, now displays

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.

Funky MOD result - no min quantity, no price.

5/13/14 (Judy) - problem was in WEB.OPER.TABLEINFO - stripping off .00 of the TO GAUGE when building the sideweld table name.

Availability is showing incorrect for certain items.

Sal 5/13/14 11:09 - The problem was that when the requested item is not in stock anywhere (we had it as negative stock in avante for items 8440 and 500) the availability routine was correctly returning one row, with the closest warehouse, for the full amount, available in 72 hours. So today's date is the 13th, the availability date for that row showed the 16th which is correct. The issue was that we were not displaying that date in the UI, I was assuming that if I had 1 row only, it was supposed to have today's date. That logic is wrong. Modified in the UI to show the date as long as it's a mod item OR the AvailabilityDate is different from Today's date.

Need to propagate Config Groups to Substitutes partial.

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

Checkout Payment Screen won't display

ED: Corrected and deployed to staging.

Checkout process hanging when no customer found for zip code & no null zip code exist for bill-to customer

ED: Fixed and deployed to staging.

Janice: 5/9 15:14 no longer hangs, brings to address screen to enter ship-to address

Results include a numbered MOD YMAC

5/9 (Judy) This may be related to bug#70 which hasn't been tested yet (setting MTO flag by godzilla logic).

5/12 (Judy) Tested with 2 test plans provided by Sal (SALMOD1-regular search and SALMOD3-quick search) and both returned correct info, so we believe the issue is on the UI side when doing a quick search. I have turned this back over to Sal. Update: SALMOD3 was incorrect ... it was reallypassing back PART.NBR = 1785. We are looking into which side is incorrectly handling this for a MOD item.

5/12 (Judy) - I changed backend RPC$MODPRODUCTITEM_GETBYFILTER to always set PART.NBR = '' before including MODPRODUCTITEM.READ.  This took care of the issue.

I don't know if this is user error/memory loss - but I did a search on item # (1785)  and I get an exact stock match, and below it under YMAC is a numbered MOD result - but wouldn't I have had to put this item in my cart or save it for a MOD to appear numbered?Below first screenshot is shot of my saved items; my cart is empty. I have no recollection of saving this, and so far, saved MODs are only showing up as MOD#### (not with custom numbers from Saved process); this one is not following that format. Logged in as Sally Draper ( contact 17279; customer number 2916, PACKAGING SALES, INC).

Cathy John Judy

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.

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: Update a little while later (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.

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 add in the the highlighted sentence. (Sorry - this is a change; the spec did not include this sentence but in hindsight we think it is necessary to include in this scenario.)

Please see edits below.

Please see edits below.

MOD availability pop-up - "FRESH" MOD - Simplified text + unit of measure issue

Please test after next deployment

SP, 5/13/14

Same as issue 160; heading of pop-up is fixed, but please replace current text in white area with the simplified text provided previously.

MOD availability pop-up - SAVED/NUMBERED MOD - Simplified text + unit of measure issue

Please test after next deployment

SP, 5/13/14 - heading for pop-up fixed (thanks) but still need to replace text in white area with the simplifed text on the right (which was a mockup - sorry, I think I forgot to spell this out more clearly in the issue detail column):

Manufacturing lead times fluctuate.

Order now for shipment from Sterling, MA on 5/27/2014.

Checkout from Cart hanging

ED: Fixed. This was an issue with the cart cost summary fields. Retest on staging.

Janice 5/9:  address screen now displays

Substitutes

Sal 5/13/14 12:17 - Fixed please test after next deployment.

SP, 5/13/14 - Tested, fixed, closed

Heading should be "Consider these substitutes," black font

Background color should be light peachy color ( #ffefcf )

Staging:

Specifications:

Please HOLD off on this; there is another variation of this issue (MOD that has not been saved yet) - I need to confer with Owen on some questions. -SP, 5/8/14

Editorial issues with MOD availability pop-up

Logged in as Sally Draper, customer number 2916 (PACKAGING SALES, INC).

Please take a look at unit of measure and other issues highlighted below.

Please add SYSCON and CUSTMST file opens and add WEBINFO.REC.  This program won't compile.  It is used by the EDI Process, so needs to work with CONTACT.READ going forward. Joe 5/9/14: Fixed & complies but not sure how to test EDI?

5/9 (Judy) I have compiled and set to 'done'

Cannot edit zip code

SP, 5/13/14 - no longer seeing this issue. Closed.

Logged in as Sally Draper, customer number 2916 (PACKAGING SALES, INC).

After running a search with one zip code, I can go up to the widget and change things like dimension, but widget is not letting me change the zip code.

Update: Actually, it won't let me edit zip code even after clicking reset. It only clears zip (and makes field editable) if I switch to pick up, then back to ship to (clears field now editable).

Zip prompts not happening

Sal 5/12/14 18:03 - Fixed please test.

SP, 5/13/14 - tested, fixed, closed.

I added one item to cart (via cart quick add? Not sure) with zip set to 01760.  I then went to widget and searched by stock item number and added item to cart with zip code 02030. No prompt regarding conflcting zip code. Item added to cart, looked in cart, zip was 01760. Went back to widget, searched on another stock #, added item to cart under zip code for Reno (as ship to). Same thing - no prompt regarding conflicting zip code. Cart remains at 01760 with all three items.

PS: If I check availabilty with zip 89434, I get Dallas warehouse info. (Am guessing this is correct and item not made in Reno.)

Search by item #

Sal 5/13/14 14:59 - I was unable to reproduce this issue. I spoke to Sue and after several attempts we were also unable to duplicate this behavior, we agreed that this issue has been resolved, closing this bug.

I happened to notice there were items in my cart, but no zip. (Not sure how that happened; the items had zips when I added them from the widget.) So I decided to clear my cart to see what would happen if I used quick add with zip field empty. Each time I entered an item number and moved to quantity field, site froze up before I could enter quantity (no prompt for zip either). I then turned to searching by item # in the widget (zip field empty). After entering legitimate stock #s the widget would back populate, but not produce any results (nor would it prompt me to enter a zip code). When I attempted to enter a zip code, I got validation error concerning antistat (now I can't remember the stock number I used...)

If I reset the widget, enter a zip code, then enter a product number, and click go, I get results.

Customers with full partnership/P-1 pricing should not get any price breaks link or popup with stock results.

Sal 5/9/14 15:22 - Fixed, please test after next deployment.

SP, 5/13/14 - Seems to recognize P-1 pricing with disabled (grayed-back) link; however, would prefer for there to be nothing (no text). Reopening. Please advise if this is a lot of programming effort. Reopening.

Sal 5/13/14 15:33 - Not a lot of work at all. It's all set, Will be deployed within the next hour or so.

SP, 5/14/14 - tested, fixed, closed.

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?

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.)

Checkout Address Screen hangs when only one shipto customer with cart zip code (and no shipto customers with a null zip code)

FIXED: ED, retest on staging

5/6 11:30 JC looks good, returns the one ship-to address

'BILLTO.NBR' missing when add an item thru quick add.

ED: Issue resolved and deployed to staging.

Janice 5/9:  BILLTO.NBR is now present

Choosing Polypropylene enables Color and Packaging and shouldn't.

5/7/14 (Judy) - when Polypropylene category is chosen, all level 3 is now disabled.  When material is set to Polypropylene for another category (ie, layflat), color, printing, venting, and packaging are disabled.  They are enabled again when material is changed to something else.

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>.

DEFAULT.VALUE and OPTIONS widget programs need BILLTO.NBR sent from the UI

Sal 4/29/14 16:46 - Fixed. (OPTIONS was already being passed BILLTO.NBR and is working). Please test.

Janice 4/29/14: Works as expected

Checkout Shipto Customer List includes customers with zip code that doesn't match cart zip

ED: Seems to have resolved itself, could you retest this?

Judy - retested - i can't make it happen again so am closing.

When 'Random Venting' is selected, the last 3 fields in the Spacing Section (Inches from Side, Inches from Bottom, Inches Between Holes) are no longer defaulted.  They are disabled as they should be, but empty.  These fields should be defaulted AFTER Nbr of Holes has been entered.

4/25 (Judy) I determined the problem is that SHOP.HOLETYPE is set to "None" instead of 'Butterfly'.  This causes none of the default programs for venting to work because they think venting isn't selected.  LAD.SHOP.TOP sets SHOP.VENTED based on whether SHOP.HOLETYPE is None or something else.  I also noticed that other SHOP. variable's info is being lost during the loop of default routines in RPC$SEARCHFIELD_GETDEFAULTVALUES.  ie, SHOP.WIDTH has the width until it gets past sort index 120 (which is the width field), then is gone when it goes through default routines after that field.

5/5 (Judy) Sal looked at it.  Looks like it's on the back end where it gets lost withint the defaultvalues RPC.  I will take this one back.

5/7 (Judy) I tracked the problem to the new logic in RPC$SEARCHFIELD_GETDEFAULTVALUES where we were trying to keep track of the previous default values because they are needed for other default.value programs that are executed later in the loop.  The program is updating the named param even if the default value is null.  But even if we stop this, we still don't know that the UI side is actually going to use the default because the field may have been manually changed (in which case the UI ignores the default value).  We don't know this info on the backend so can't duplicate this rule.

5/8 (Judy) decision was made to go back to adding logic to individual DEFAULT.VALUE programs and removing the logic from RPC$SEARCHFIELD_GETDEFAULTVALUES.  This has been done and random venting defaults are working again.

System freezing with availability link on certain broad searches.

Sal 4/30/2014 11:15 - Fixed. Please test after next deployment.

SP, 5/6/14 - Tested, fixed; however see new issues reported in issue 99.

Substitutes link should not be in this popup

Sal 4/29/2014 18:31 - Fixed while working on bug 135. Please test after next deployment.

SP, 5/6/14 - Tested, seems to be fixed.

Any time the stock item is available at requested quantity from the primary warehouse, there should not be a substitutes link; this link should only appear when other warehouse/bundling/backorder options are being presented (when the item is NOT available at requested quantity from primary warehouse).

Also - related to issue 99... please fix typo (change "are" to is" - Updated product availability is...).

Within the Saved Items Tab a small white semi circle and a portion of a purple icon appear on the "Shop" tab.

Sal 4/30/2014 14:26 - Could not reproduce bug, Please test after next deployment.

Steve 5/5/2014 - Whatever you did? Great job. It looks to be fixed.

Firefox only

Tested in IE and Chrome
and bug does not happen 

The category sections show only include the selection for Full Gauge when the operator entered full gauge.

4/25/14 - JBM - this looks complete - also tested Black Conductive Tubing which was another FG category.   Looks like it is already set to Done.

Try Furniture Bags and no dimensions and you will not get any stock items.    We should include all items except when they specifically ask for Full Gauge only.

4/25 (Judy) Modified BP WEB.GET.STOCK.ITEMS to change stock select to only look for stock items with full gauge = Y if the Full Gauge box is selected on the widget.

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

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."

Availability popup for MOD Items should look exactly like the window for stock items that are fully aviable except you need to take the due date to the end of the message "on xx/xx/xx".

• 1) Need better description on title bar of popup. ie "on Case" s/b "in Case".
• 2) Display "Available Substitutes" a little bit further down from the other text.
• 3) Fix first row showing wrong qty available ie: For part number 520 and required qty of 100 we get "At this time, 100 cases of item 520 are available to ship fromSterling, MA" then in the options we get another line saying "52 cases of item 520 can be available to ship from Sterling, MA within 24 hours of placing an order." First line is wrong, second line is accurate.
• 4) Make the legend "Please note that inventories fluctuate. Updated product availability are provided at time of checkout." Show ONLY when we have a Stock Item and also it is not fully in stock, ie: they request 5 but we can only ship 2 at this time from the requested warehouse.

Sal 4/25/14 17:54 -

• 1) This description comes from Description1 from the database (also, currently Description is shown when Description1 is empty). This will have to be fixed in the Database side. Sal 4/29/14 18:09 - I was advised to put for description the same text we show in the results items, and fixed the "in" "on" text. 
• 2) Fixed in UI
• 3) Needs to be fixed in the Database side. Sal 4/29/14 18:09 - This was actually the right information except I was not showing the availability date, it should have read "At this time, 100 cases of item 520 are available to ship fromSterling, MA on 5/1/2014".
• 4) Fixed in UI.

Sal 4/24/14 18:22 - Done, please test after next deployment.

Sal 4/29/14 18:27 - Done, please test after next deployment.

SP - 5/13/14 - please note: some aspects of this superseded by instructions in 160 + 161

When there are no YMAC's the system is still showing the YMAC header information.  Do not show headers

Sal 4/30/14 11:26 - Fixed. Please test after next deployment.

PORT.NUMBER, PORT.MARKER, and OPERATOR are null when creating a MOD Item/New Quote

4/23 (Judy) - Had conversation w/Ed. We confirmed that these 3 are being kept on the site in cookies but are not being passed to back end when creating a MOD Item/Quote or when creating a MOD or Stock Sales Order. New timeline tasks should be created for these tasks.  Once the timeline tasks are created, remove from the QA sheet.  OPERATOR is also needed in shop widget for FCT.PACKING.OPTIONS for cradlepack preference.  We have to know if it's ce or customer who is using widget search.

Sal 5/9/14 10:47 - Fixed, please test after next deployment.

Clicking save second time seems to freeze website.

Sal 5/1/14 15:04 - GetDefaultValues is not pulling the right data for a saved mod item. Need to touch base with Judy as to why.

Sal 5/2/14 15:51 - John fixed this in database side.Please test.

SP, 5/6/14 - 5:06-5:09 Tested - system hanging. Gave up after ~3 minutes (tested by retracing steps, created and saved MOD1292).

Sal 5/7/14 17:48 - Fixed, please test after next deployment.

SP, 5/8/14 - tested, closed.

Certain categories do not have level 3 options but
gray arrows appear within empty container.

Please remove these arrows in following poly bag categories:

Garment, Lit/merch/newspaper, polypropylene,
vacuum pouches, wicketed, sandwich & pre-opened.

 This change should be made for the remaining Level 1 selectors (reclosable bags, tubing & sleeves, etc.)

4/24 - Do not fix or hard code based on category becuase they are added to all the time and therefore would reqire code changes.  Find a way to determine if there is nothing showing as a default and then remove the arrows based on that.

Please test after next deployment

Print function of the Share popup, text cut off on right side about 1/2 inch.

Sal 4/18/14 - This was fixed by setting margins to 0 in Firefox page setup.

Tweaked Modsearch banner as it was slowing down the Find in the shop widget.

Sal 4/23/14 09.54 - Not slowing the Find anymore, but it's now not functional to spec, will have to tweak it a bit more to make it work again the new way.

Saving a contact in Profile screen deletes the SLSCONTACT.USR record

Sal 5/1/14 15:15 - Note: We need to include a $('#SaveButton').off(); // So we don't trigger function(s) attached to this button in other MyAccount partials. Fixed.

Selecting Cradlepacked MOD Item in Results creates a saved item for the Boxed result.

Sal 4/23/14 10.37 - This bug was originated by the change we made in whether the id that represents the results item changes from cpn to part number depending on whether the mod item has already been created or not.
Please test after deployment.

Judy 4/23/14 11:27am - Tested - looks good

Increasing Order and Work Order Characters Allowed and Making them Alpha Numeric

Joe 4/22/14: Tested fine; will move to Live morning of 4/23/14.

I just stumbled across a screen that might cause us some problems when we have an alpha character at the end of our order numbers.

INV9029 when then are printing brandit or sample labels expect to have numeric only.

1

Level 3 content does not show correct section.

I started in "Color" and then clicked "Materials and Additives". The display still shows content for Colors. I've had this issue in both Chrome and IE. This screenshot is from IE.

4/22 (Judy) - I saw this same thing happen in Firefox. Kept showing Printing Menu (which had data selected) no matter which level 3 menu I tried. This happened after the FIND button and I went back into the level 3 menus.  I had to 'reset' and start over to correct.

Sal 4/23/14 15:04 - All set, please test.

Judy 4/23 15:35 - Looks good.  Leaving open so that Steve (who reported it originally) can test.

Level 3 link value is not correct. It says both Metallocene and
high slip selected under additives but they are not checked. 

Please test after next deployment

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

Excess space under Level 3 Packaging area.

Sal 5/1/14 15:59 - Already fixed, please re-test.

Steve 5/5/2014 - Does not look any different in Venting and Packaging. Materials and Additives looks better. I have provided a new screen shot from Firefox.

Sal 5/8/14 10:33 - Did miss this one, all set now. Please test after next deployment.

5/5/2014 sample from Firefox

RPC$PRODUCTITEM_GETBYID & GETBYFILTER don't compile cleanly

JC:  RPC$PRODUCTITEM_GETBYID already opens SYSCON

Please fix following programs (PRODUCTITEM.READ now uses SYSCON and these programs don't open SYSCON):

RPC$PRODUCTITEM_GETBYID

RPC$PRODUCTITEM_GETBYFILTER

Please fix:

Compiling Unibasic: E:\WEB\DEV925A\LDLIB\RPC$SHOPPINGCART_VALIDATECHECKOUTSTEP

Warning: Variable 'FREIGHT.ACCT' never assigned a value

Warning: Variable 'FREIGHT.BILL.ADDR' never assigned a value

Warning: Variable 'STEP.NBR' never assigned a value

Warning: Variable 'TRUCKER.NAME' never assigned a value

compilation finished

'Added to Cart' message gone

ED: This is not a bug, MOD item adding is slow and there has been work in there that somehow is preventing the wait icon from displaying (Sal).

Message does display.

Judy 4/18/14 - It is very slow, but if you wait, you eventually see the 'added to cart' message. 

Button text

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

SP, 5/6/14, tested, fixed.

Although it conforms to the original spec, would like the button text to be "Ok" instead of "Select" (sorry!)

Validation error given when should not be

5/5/14 (Judy) - The site is forcing 'full gauge' under certain conditions (furn < 1.15, Continuous Sheeting or Tubing, Opaque < 2.9mil, Nonslip < 1.1mil).  When forced, the user is not allowed to 'uncheck' the full gauge box.  This is why we are doing it this way.  I have softened the message by adding "Select Yes to accept full gauge".  If they select "Yes" we automatically set full gauge.  If they select "No" they have to re-enter the gauge.  We can't allow them to go any further without knowing which they want.  John also said that the purple 'Validation Error' will be going away, so it won't look like we're yelling at them.

5/7/14 (Judy) - John and I decided that the UI side will only show the validation error box if the user has changed (or looked at in the case of the FG popup) at any of the fields in RESET.VALS.  The UI will always reset the values, regardless of whether the user is shown the error box or not. Re-assigning to Sal.

Sal 5/9/14 12:19 - Fixed, Error now shows only if user went into FullGauge pop-up and altered the checkbox state.

Note: Just by opening the pop-up and closing it doesn't mean we have confirmation of selection for Non-FullGauge. Owen agreed on this behavior, user will have to check and then clear the check box in order to confirm that he/she doesn't want full gauge.

Please test after next deployment.

SP, 5/13/14 - tested, closed.

If I select furniture bags, and do NOT look at full gauge pop-up, then enter gauge below 1.15, I get this error. Should only get this error if I opened the full gauge pop-up and left FG unchecked.

After a user selects a Material & Additive( in this case LLD and selects the sub choice of Std Hexene Blend) and clicks "Find." The user gets a set of results.

Now the user would like to go back and change his LLD sub choices. By clicking on the Material and additives link, the menu only expands partially. It needs to open to show the sub choices the user has made and allow the user to change them.

Please test after next deployment

Delete cart button is not deleting carts or possibly deleting the wrong cart.

ED: This is resolved.

Anti-static choices under level 3 Material & Additives. The user
will not be able to tell this is a stepped process because of
text and design.

Some minor design updates can fix these issues.

1. Add text to indicate a step process.
   "1. Select Anti Static Type"
   "2. Select a Resin Type"
   "3. Select a MIL Spec Type"

2. Add more vertical space between steps.

3. indent and line up text that breaks to 2 lines.

Please test after next deployment

Current Design.

Updated Design

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

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

Stock discount message

ED: Fixed. Deployed to staging for retest.

NOTE: Only the quantity to new break amount is hard coded, waiting on back end for that to be 100%.

SP, 5/8/14, tested, fixed.

The stock message is not changing based on $ value in cart. With stock below $500 (or below stepped volume discounts if applicable), different message should appear.

Staging:

Specs:

PS: I am also seeing the stock message when I only have MOD in the cart.

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 )"

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:

1. Materials & Additives menu heading wrapping to 2 lines
2. It should be "Material" not "Materials"

SP, 5/7/14, tested, fixed.

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.

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

Bundling alternatives should not be presented when the requested quantity is available from the primary warehouse.

4/24 - Ed please check to see if this information is being stubbed in.  It does not appear to be calling the backend availability routine.

Sal 5/1/14 14:06 - This was fixed in Shop, Cart is using the same screen as Shop so it should be resolved in Cart as well. Please test.

Clicked availability for 5 cases of item 1200 shipping to 02030. Shows full quantity available to ship from Sterling, but then goes on to provide all sorts of alternatives. These alternatives should only show when fewer than the requested quantity are available from primary warehouse.

PS: For situations where these choices are offered, please change "can be available" to "are available"...

Warehouse should not be hyperlinked.

Sal 5/1/14 14:06 - This was fixed in Shop, Cart is using the same screen as Shop so it should be resolved in Cart as well. Please test.

SP, 5/13/14 - tested, fixed, closed however, please note subsequent issues noted in 164.

The warehouse items are shipping from his hyperlinked and should not be; it should just be bold/black text.

Apologies, images in specs may have been misleading, but it was not our intent to have warehouse names link to anything.

Typo in availability pop-up

Sal 4/29/2014 18:31 - Fixed while working on bug 135. Please test after next deployment.

SP 5/6/14 - are was replaced with is (thanks), and clicking on a few sample search results, all seems to be well. However, while testing issue 140, on the third result of a total of 3 results, I got a curious availability pop-up. (Because not even one case of this product is available from Sterling?...) The first sentence in 4th paragraph was missing; also missing period at end of 2d sentence (4th para). Missing date from alternative shipping choice. So it should read:

At this time, 1 case of item 6682 is available to ship from Cedar Rapids, IA on 5/7/14.

These other shipment options are available during checkout:

-1 case of item 6682 will be available to ship from Sterling MA within 72 hours of placing your order.

Please note that inventories fluctuate. Updated product availability is provided at time of checkout.

SP, 5/7 - changed status to done; there are numerous editorial issues and inconsistencies with availability pop-ups. Rather than subject you to death by a thousand cuts, I'd like to catalog them all (and I need some direction form Owen on a couple of points). I will log all of these under a separate issue.

Everywhere this string of text appears, please change "are" to "is"; apologies, I think this typo was in the design spec. Thank you.

What is the orange battleship thingy on the Shop tab that appears during transitions?

ED: The images are actually a sprite (all images we use in a single image). The orange "thingy" is actually the trash can. This little "thingy" has been bugging me for over a year, I actually fixed it awhile ago in the image, but didn't replace the current image with the fixed one.
This is now fixed.

I see this while waiting for widget-tabbed pages to load, ie, going from shop to saved items, saved items to cart, etc.

While waiting for the full widget to load, opening homepage for first time:

While going from Shop to Saved items:

Work with Sal to track down why the product use tags are not returning as checked even though they are saved in CONTACT.ITEM.XRF.USR

Joe 4/14/14: Sal confirmed test is working.

Extra tooltips

SP, 5/6/14 - Tooltips have been removed; however, I am seeing what appears to be alt text for save and share.  If there is alt text, it should be for the icons,  not the linked text.

SP, 5/7/14 - they're baaaak. (At least for share and save.) Reopening.

Please test after next deployment

SP, 5/13/14 - tested, fixed, closed.

Please eliminate the tooltips that appear when you hover over:

• Availability
• Price breaks
• Save
• Share

Saving MOD items does not work 

Sal 4/7/2014 20:27 - Save Item Popup is now fully functional. Please test.

Saving a MOD item does not update the database. 

Sal

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

Odd sort behavior, depth sort button with more than one stock match

4/24 - Susan, we have fixed some of this before.  Would you please retest and let us know where you are still having issues.  Thanks

4/24 - Retracing my steps, I think orig issue addressed, changed status to Done, but a couple of new interesting things happened worth pointing out:

1-I am able to do what I originally set out to do, a broad search via widget category, C&A clear - I get a list of results that makes sense.

1a-There is a sort bar. That makes sense. But sorting on depth does not make sense. I clicked it and it reordered the list - not sure what the basis of the sort is. I can  live with that, but not sure if it is an indicator of an issue.

1b-Some of the item descriptions have a length dimension (= foot/roll); some do not; am guessing this is an Owen/Tom/Cliff issue. One, item 4410, has 100 length, but feet per roll is 1.

2-Next I recreated my 4/3 workaround to get some C&A results - typed '4485' in item # search box. Unlike before, this produced one exact stock match (just 4485 and not 4485G). Was that intentional?

2a-There was no sort bar - that makes sense.

2b-If I search on 4485g, I don't get any matches. Have to capitalize G to get a hit. It would be better for search not to be case sensitive.

I tried to do a search for all C&A products via widget. I got no results...

Thinking that might be a known issue incompleteness of data on DEV ( ??? ) I retried the search using a specific C&A stock number in banner (4485); that produced 2 exact stock matches (4485 and 4485G); the widget back populated appropriately with dimensions, etc.. So far so good. The results were sortable on depth and price.  I found it curious that the results were sortable at all - although technically that's probably correct. We probably never spec'd a lower limit.

Sorting on depth definitely didn't make sense though. So I clicked it to see what would happen. It effectively re- ran the search as though I was searching for all C&A products (or all clear C&A product?).  Pretty much what I had set out to do at the beginning. This produced 38 results. This is definitely NOT the expected behavior for a sort button. Also: FWIW, the widget did not back populate to match this "search" (dimensions change to "all" etc.).

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.

Fix 'WEBINFO.REC unassigned variable' in all programs that INCLUDE CONTACT.READ

Joe 4/8/14: Coding and testing complete, please see today's email for more details.

The following programs don't compile cleanly because of an unassigned variable for WEBINFO.REC. This logic was added awhile back to CONTACT.READ but the only program changed to set WEBINFO.REC was RPC$CONTACT_VALIDATE.  Add the call to FIND.AVANTE.WEBINFO when PORT.NUMBER # "" to the following programs.  Refer to RPC$CONTACT_VALIDATE for logic.

RPC$CONTACT_GETBYCUSTID, RPC$CONTACT_GETBYEMAIL, RPC$CONTACT_GETBYFILTER, RPC$CONTACT_GETBYID, RPC$CONTACT_GETBYNAME, RPC$CONTACT_GETBYNAME1

Re-test all programs to make sure that DATAFIELDS in RETURN.VALUE is being set properly.

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.

Cannot delete a MOD Item from a cart

(Judy) - tested 4/16/14 - looks good. May have been an issue with bad data in the shoppingcart record that I was trying to delete from.

Error Box after Gauge is entered

Sal 3/28/14 14:27 - This bug was for IE. Fixed, please test.

Firefox

IE

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.

Centerfold tooltip - appearing for a centerfold category it doesn't apply to

Sal 3/27/14 1:11 - Fixed, please test.

SP 4/3/14, Tested, fixed, closed.

This tooltip is appearing when the category is singlewound sheeting

Centerfold tooltip - missing for a centerfold category

Sal 3/27/14 1:10 - Fixed, please test.

SP 4/3/14, Tested, fixed, closed.

Centerfold tooltip - formatting

Sal 3/27/14 1:09 - Fixed, please test.

SP 4/3/14, Tested, fixed, closed.

Related to issues # 6 and # 69 below.

Font is bold, should be as described in issue 6; pointer is slanted, should be straight as described in issue #69. Please add a period at end of sentence (sorry, this was a mistake in the specs).

Construction of furniture bags

4/24 - this is a furniture bag.  All furniture bags are bottom seal so this is not a problem.

In the same scenario as for issue 79 above, Jay noticed in the expanded description that the construction for this particular item should be sideweld, not bottom seal.

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:

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:

Cradlepack consistency

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

SP, 5/7/14, tested, fixed, closed.

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/14/14 15:35 - Great catch! Should be fixed after next deployment.

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.)

Error in Cart, Saved Carts, Shop Tab when adding a MOD item or with an existing MOD item in a cart.

ECD: Error was caused by MOD item quantities. Qty for a MOD item can be a decimal, property was implemented as an integer. This caused an error in multiple areas. This has now been resolved

Cart allows user to proceed to Checkout without cart zip.

ECD: Resolved.

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.

Write Configuration# to MOD.ITMMST.USR when first creating Mod Item.

Joe 3/19/14: This is complete and update working as expected.

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. 

Gusseted sheeting tooltip

Sal 3/27/14 1:04 - Fixed, please test.

SP, 4/3/14 - Tested, fixed, issue closed.

Design spec:

Staging:

• Font should not be bold (see issue # 6 reported by Steve).
• Please fix 'enteer.'
• Please place period at end of last sentence: '... opens to 48".' (Sorry this was missing in orig design.)
• The bubble's pointer/nubbin thingy should be straight, not angled

Editorial and formatting

Joe 3/28/14: Per JP change all programs that hardcode Gauge UOM from plural to singular: "mils" -> "mil", "mics" -> "mic". Also, add "," after Guage UOM and Change Generic Name to Title Case.

Sal 3/28/14 14:24 - Fixed all issues except Stock Item number preceding zeroes, which will be fixed in database.

Sal 5/1/14 11:00 - Stock Item number preceding zeroes has been fixed in database. Please test.

SP, 5/7/14, tested, fixed. However, noticed a new issue (will log as #150)

(Design on left, staging screen capture on right)

Column heads:

• Price/Unit should just be Price.
• Count/roll, Quantity, Unit, Price, should not be bold.
• Quantity should be spelled out if possible.

Editorial: Mil should be singular; followed by comma, followed by product name in Title Case, i.e.:  "48x30x60 2 mil, Bags" (is this a Tom/Cliff database issue?)

Stock item number should mirror what's in catalog - so remove extra zero, i.e. "Item: 10435" (is this a Tom/Cliff database issue?)

Freight for stock – should be static/black – not behaving like blue hyperlink.

Edge of widget - extra pixels along portion of edge of bottom, and edge of cart tab.

It looks fine in Chrome, shows up in Firefox and IE.

Sal 5/1/14 01:04 - Fixed. Please test after next deployment.

SP, 5/6/12 - tested, fixed.

Validation error pop-up - behaves differently depending on clicking OK v. X'ing out.

Sal 3/27/14 00:29 - Fixed, please test.

SP, 4/3/14 - Fixed, issue closed.

Attempt to search for 120 x 120 furniture bag: When validation error triggered, if I click OK button to clear it, then click reset, error reappears. However, if I 'X' out of the error or click outside of the box instead, reset works - error doesn’t reappear and widget settings clear. 

 Attempt to search for 120" wide layflat. When validation error triggered, click OK, attempt to change category  (to Furniture, which allows 120" width), error reappears. But if I X out of error or click outside box instead, error doesn't reappear and I am allowed to change category.

Reset now clears out Ship Zipcode

ED: Fixed.

Judy tested 3/11 - done

Selecting Cradlepacked in Widget shows exact same item in YMAC

ED: Corrected, no search performed now for a MOD YMAC if the packaging option has cradle packed selected in the widget.

3/26/14 (Judy) - tested - closing.

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.

Clicking Save and Continue on Address step does not work "Nothing Happens" if the cart has a MOD item in it.

ED: Corrected issue in CheckoutShippingStepModel.InitiateStep().

Exact Match MOD Item not working in Results

ED: Corrected view code to accomodate, also requires PRODUCTMODITEM.READ to be modified to NOT return "MOD" in the part number field for temp mod items.

Joe: PRODUCTMODITEM.READ modified to NOT return "MOD" but MOD# or Null.

 The position of the Save Item Popup is not correct.

Sal 3/27/14 00:26 - Fixed, please test.

The save item popup is not positioning itself in the correct location when it comes up.  I believe this is a result of the way the height increases as it loads up.  I would suggest setting the min height  to the set height of the box after it loads rather than having the popup build up.

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

RPC$CONTACTITEM_GETBYID is broken it comes back with the following error messages:
When getting a Stock Item:
(3A) Cannot Read CONTACT.ITEM.XRF.USR file, 01*17251*00017 Test Plan: SAL10
When getting a Mod Item:
(3D) Cannot Read QUHDR file, MOD1027 Test plan: SAL11

2/7/14 Joe: Item.Type was not set correctly, fixed and cleaned up other minor other bugs in RPC$CONTACTITEM_GETBYID and RPC$CONTACTITEM_GETBYFILTER, also checked the RPC$CONTACTITEM_SAVE for MOD and Stock items.

2/25/14 16:02- I was able to delete both stock and mod items out of my saved items list. This bug is resolved.

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.

Price Breaks MOD shadowboxes in IE do not have rounded bottoms. They are squared off.

Sal 5/1/14 17:08 - Fixed, please test.

Test

gray box is too dark (should be #E0E0E0 and is currently #C0C0C0). The spacing around text is too tight. Needs more space horizontally and vertically. Label headers should be bold and the word "price."

Sal 3/27/14 00:22 - Fixed, please test.

Return Custom Price Breaks for MOD items 

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

Show Centerfold Tooltip for Perforated Centerfold Sheeting.

Sal 3/26/14 21:37 - Fixed, please test.

Judy 4/15/14 - Centerfold tooltip problem is fixed, but have same problem with Perforated Sheets-Gusseted  (catalog code 409) not showing gusseted tooltip like Gusseted Sheeting (catalog code 403)

Sal 4/30/14 8:04 - Fixed, please test after next deployment.

Judy 5/5/14 - Tested-looks good

Judy 4/30 8:47am-Centerfold tooltip is fixed. But I noticed that Sheets Perforated-Gusseted is missing the tooltip - it should be the same tooltip as GUSSETED Sheeting (on the Film & Sheeting menu)

Sal 4/30/14 10:52 - Not deployed by the time Judy tested. Fixed, please test after next deployment.

N/A MOD Price for Gusseted Perf Sheeting with pkg = Rolls, Boxed 

Sal 1/28 10:02 - This will hopefully be fixed after Wayne is done fixing the pricing program on bug #36 and #41.

Sal 3/24/14 16:12 - Seems to be fine now, please retest.

Printing Direction forcing Vertical when it shouldn't 

5/5 - Judy is reviewing.

Venting text boxes not working correctly on a quick search.

Sal 1/21/14 13:40 - Placed code to only set the changed attribute only to controls that do have a value, excluding those that have "" and "0". Now venting seems to work fine on a quick search.

Screen Heading incorrect for MOD Price Breaks 

Sal 2/7/14 18:13 - Changed code to update titles correctly as per new Design. Please test on Monday after deployment.

Judy 2/26/14 - Done

 Qty Change on Cart not updating the quote

1/28 5pm - Issue was on UI side, quote quantity was updated correctly based on what was passed in

Problem when receiving 'incompatible data' error code from MOD Item Check program

Sal 1/15 11:31 - The hard error part is solved. But we are actually not getting any stock items -nor ymac items-  for this configuration. Waiting for Judy's response on this.

Sal 1/17 14:23 - Now trapping the right exception, Please retest on Monday after deployment.

Judy 1/20 6:30pm - re-tested and all issues are gone. Issue with stock selection was due to missing web data. I have notified Cliff to add 'octene' to the items in category 118.

UI is not trapping the correct error when going after the MOD Cradlepacked YMAC result on the Shop Results.

To duplicate:

• In section 2 category choose Liners – Gusseted LLD (catalog cd & ruleset 118)
• W: 16 D: 14 L:36 G: .58 (Notice it is point 58)

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.

Full Gauge disabling is not working 

Sal.1/14 15:27 - John added code in avante side and I added code in _InfoGauge.vbhtml to fix this, if John's code needs to be reverted (its hiding the icon at times where it was usually visible), my code will take effect disabling the checkbox in the popup. Please test.

Sal 1/16 10:20 - I keep getting the wrong "disabled" state from the database when I change something like a dimension, so the checkbox doesn't get enabled/disabled appropriately, will keep looking into this.

Sal 1/17 10:05 - Found out the problem is when user has changed to full gauge manually, then any default values coming from db get discarded. This needs to be handled by the validation engine and reset fields. Will get in touch with John to implement this.

Judy 1/17 11:30-full gauge is ALWAYS disabled now. I can't click the checkbox even when I s/b able to.

Sal 1/29 12:09 - We need some validation logic to handle the situation where the user changes the state of the fullgauge checkbox, from then on that value will be persisted until they manually change it again, then that new value will be persisted. Default values will not take place any longer and we have the situation where we want to override their value if the current configuration requires fullgauge and they had previously unchecked it. Judy will put this validation logic in place in avante or have someone do it.

Judy 1/31 @ 11:15 - I have added the full gauge validation program and it is working now. The only thing I noticed if you choose VCI first, then enter dimensions, you get the error right after enter 1mil in gauge (you aren't allowed to click Full Gauge before this time, so it looks like you are getting an error but never got the change to choose it.  I can live with this scenario. 

MOD Price Breaks - Results
Sal 1/7/2014 14:13 - Was passing the parent category, now passing the child category and seems better, but price still off by around 80cents in average. Will need to be checked in Avante.

Sal 1/14 17:05 - This will hopefully be fixed after Wayne is done fixing the pricing program on bug #36.

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

Entering 3 add'l MOD price breaks on the price break popup from results is returning invalid break prices:

Std breaks were displayed as: 20 @ 36.81; 40 @ 35.37; 60 @ 35.23.  I entered the same qtys 20,40,60 in 'change breaks' and prices returned were 1.71, 1.14, and 0.86 ... way off.

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.

Availability 'Link' for MOD Items in Results doesn't do anything. 

Sal 3/24/14 20:48 - Fixed, please test.

Judy 4/15/14 - tested - popup now comes up but looks like it's the stock info (ie, 7.28 cases can ship from sterling - the 7.28 for the MOD item referes to thousands and it has to be made first before it can ship.  The popup must have different data for a MOD item. Re-opened.

Sal 4/30/2014 08.10 - Fixed please test after next deployment. 

Re-test

20X8X20X2.5 - Pkg = Rolls (didn't change any level 3):

1. Minimum Qty in MOD Results defaulting to 35M and s/b 8.3M (check BP FCT.MINIMUM.MODQTY for sheets - same problem may exist for Tubing)

Judy 1/7/14-6:40pm - I tested and this looks good for perforated sheeting. Closing bug.

2. Leadtime is incorrect at 1/5/14 instead of 12/30/13. Looks like it's defaulting to 2 weeks leadtime instead of using the work center's lead time. (See what values you are getting from UI in BP WEB.MOD.LEADTIME) *** I FIXED THIS ON 1/2/14 - WAS USING OPER# INSTEAD OF WORKCTR# (JUDY)

Gusseted Perforated Sheets (SOR) - incorrect 'Boxed' Price 

Sal 1/7/2014 13:35 - Error seems to be in RPC$MODPRODUCT ITEM_GETBYFILTER based on 3 test plans by John where all that changed was the packaging, all three returned same price.

Sal 1/8/14 10:06 - Seems to me the RPC$MODPRODUCTITEM_GETBY FILTER is not working correctly as far as the pricing goes for this case scenario. We're passing the same config, just different packaging.

Sal 1/14 10:47 - Manually changed to rolls, boxed then clicked find and I still got the same price for both rolls, boxed and rolls, cradlepacked. Still think the problem is with the pricing in RPC$MODPRODUCTITEM_GET BYFILTER.

Sal 1/14 16:58 - The routine that gets the mod items (GetModSearchItems) is now setting PKG to Rolls, Boxed whenever it is Rolls. Pricing issue still remains, Judy has Wayne looking into the pricing program.

Judy 1/14 5:10pm-Wayne is looking into why Box1 Total Qty is zero - this is why it can't calculate the boxed upcharge.

Judy 3/25/14 - Re-tested.  Prices for both boxed and cradlepacked match Avante (117.60 Boxed; 115.86 Cradlepacked)

20X8X20X2.5 - Pkg = Rolls (didn't change any level 3):

Two MOD results show when I leave pkg as 'Rolls'.  The first option is showing pkg as just 'Rolls' - should this be 'Rolls, Boxed'?  If so, price is incorrect.  Showing same price as cradlepacked, which is in the YMAC section.  Boxed rolls are more expensive than cradlepacked so price s/b different.

When the user clicks Find, if the Packaging is Rolls, change it to Rolls, Boxed and continue processing.

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”.

1) Sheeting and Tubing (any type) should not be charging a Full Gauge upcharge when the Full Gauge flag is set.  The pricing is off between old site and new for the amount of the full gauge upcharge. Try Gusseted Tubing 8x4x3mil Non-Slip Metallocene 15%:

Avante=20 rolls x 40.11 = 802.20 *** this is correct

Web    =20 rolls x 43.78 = 875.60 (has a full gauge of 73.375)

From the MOD Pricing Spec:

Full Gauge Upcharge (criteria 43):

1. If Full Gauge: Full Gauge Upcharge Base x .10
2. If not Full Gauge: 0
3. ROLLSHEET/ROLLTUBE - If Full Gauge=Y: Full Gauge Upcharge Base x 0.00 ...

Re-tested 12/9 - looks good

2) The web quote 82228 has no work center info (primary operation s/b EX1200 - refer to Avante quote 82229. Not sure if this is a tubing issue or if it's related to Metallocene%, which was an issue but has been corrected.

Re-tested 12/9 - still no work center info

12/11 (judy) - I found that for SOR, ROLLSHEET & ROLLTUBE, the MOD pricing routine isn't passing back the labor time in MOD pricing array field 32. Gave back to Wayne.

12/13 (judy) - SOR now has work center, but labor hours are incorrect.  I haven't retested ROLLSHEET/ROLLTUBE.  PRICE< 31> = 221.0 (which is correct) but < 32> = 5.990 and s/b 13.34. Calc is Roll Wgt (37.8) / Oper Rate (221.0) x #rolls (78) = 13.34.

01/21/14 (Judy) - re-tested - everything looks good (price, work center, labor hrs) except price breaks are slightly off (2-3 cents off from Avante - some higher some lower).  s/b 40 @37.531 (web has 37.5584); 60 @36.148 (36.1197); 80 @35.144 (35.1115).

5/9/14 (Judy) - I've retested everything (unit price, price breaks, labor hrs, work center) - everything looks great. Closing.

Done

SOR (Perforated Sheeting) - results select not working

Judy 1/22/14 - only stock selection is for singlewound Perf Sheeting.  All 19 items in ruleset 408 have the folded flag = Y, but you can't select folded in packaging unless you are looking for a bag or furn bag. Checking w/Cliff and Owen on this. I will take over this bug from Sal.

Judy 2/3/14 - Singlewound is now working (after Cliff removed 'folded' flag from stock.  Centerfold still isn't working. Waiting for bug #50 to be fixed so that SOR centerfold works like centerfold sheeting. Still unsure whether gusseted selection will show the correct YMAC for 30x30x60.  Should show 60x60 stock item.

5/5/14 (Judy)-SW 60x60x2 shows 004973. CF 30x60x2 shows 004973. these look good.  But Gus 15x15x60x2 only shows MOD. Should it also show stock 004973? Checking w/Owen

5/8/14 (Judy) - after discussing with John and Owen, we decided that:

1. centerfold 30x60 will return stock 60x60 item 004973 as exact match with MOD 30x60 boxed and MOD 30x60 cradlepacked - this is working
2. singlewound 60x60 will return MOD 60x60 singlewound boxed as exact match with stock 60x60 centerfold as stock YMAC and MOD 60x60 singlewound cradlepacked as second YMAC - this is working
3. 15x15x60 gusseted is currently returning MOD boxed as exact match and MOD cradlepacked as YMAC. Not sure if we can get this to work as a stock YMAC at phase I, so we are closing this bug.

Venting - Default Values Incorrect/Database Updating Incorrect

Sal 1/7/2014 12:50 - This bug seems a to be a duplicate of bug 15. Judy made a change, now textboxes show disabled if nothing has been selected for HOLESIDE.
Now we need to make sure the default values program for NBRHOLES runs in order to get the right default values for the other 3 textboxes in that section. Judy will check that program....

Judy 1/7 6:30pm-The default.value rules for random venting/between holes isn't working because it s/b same as the value in SHOP.FROMBTM, but that is zero (even though a 5 shows on the widget).  Either SHOP.BTWNHOLES default is executed before SHOP.FROMBTM, or SHOP.FROMBTM isn't being returned to the back end.

Sal 1/14 16:09 - Judy figured it out that by the time the btwnholes default value program runs we're not replacing the frombtm input value with its new default value. Judy will either run the frombtm default value routine inside the btwnholes routine or will update the frombtm parameter value with its new default value.

Sal 1/15 15:42 - John fixed it, please test.

Judy 1/17 - I re-fixed BTWNHOLES default and added add'l fixes to the BTWNHOLES validate program. The UI Side now looks good for Random Venting, but the data isn't getting to the back end for the following:  #Holes coming back as 0, From Bottom coming back as 0, Between Holes coming back as null.  From side is the only one returning to the back end correctly.
Judy 1/21 - Re-tested ... all info getting to back end now.

When I choose venting, a few issues in Spacing section:

1. If I choose Random Venting: #Holes s/b enabled for entry but isn't, Inches from Bottom showing 0 instead of default value, Inches from side is okay (showing 4), and inches from bottom showing a dash instead of default.
2. So I switched to 'user specified' and entered a '2' in each of these 4 fields. When it created the quote, the configuration had the following values:
   1. #Holes = 0
   2. Inches from Bottom = 0
   3. Inches Between Holes = null 
      1. 1. Inches from side has the correct info (2)

Metallocene% not returning correctly from UI 

Sal. Clicking Find now posts 15 or whatever the textbox value may be.

12/4-Retested and SHOP.METALPCT appears to be coming to back end as null so logic still isn't working... Judy

Sal 1/6/2014 10:55 - Fixed a couple weeks ago..

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.

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?

When I create a quote for gusseted sheeting (catalog code 403), the QUDET record has BAGS as an item# instead of ROLLSHEET. 

12/10 - tested - this is fixed (judy)

Sheeting Slit Type/Folded in Half

I don't think that Sheeting Slit Type or Folded in Half are making their way to the back end.  It's not in SHOP.SHEETSLIT or SHOP.FOLDED so therefore is not in configurator or part of the MOD item description

12/9-folded in half now ok after I added Y/N flag to SYSTBL MOD.CRITERIAXRF.LAD.  SHOP.SHEETSLIT still not making it to back end.

12/9 Sal. Judy fixed "Folded", me and John fixed "SheetSlit". Please Retest.

12/10 (judy) - I retested after deployment and still no SHOP.SHEETSLIT getting to back-end. 

12/10 (judy) - looks good now.  Closing.

Printed - Existing Plate Defaults 

Sal 1/6/2014 09:30 - ValidateSearchField is returning ResetFields but ValidationErrorLevel = 0, s/b 2.

Sal 1/6/2014 10:30 - JP modified WEB.PLATENBR.VALIDATE to return ERR.LVL=2 in this case, pre-existing plate numbers now update the interface correctly with RESET.VALS, please retest.

Judy 1/8-this is still not working.  Before this fix, it was enabling the Print Color, direction, and orientation.  But now it doesn't enable anything and it still doesn't display the existing plate description and image dimensions.  I waited until after deployment to test this.

Sal 1/8 15:40 - Data is now being returned, need clarification as to why it needs to be enabled for editing.

Sal 1/14 16:01 - This is now fixed please re-test.

Judy 1/17 11:45am-Defaults for stock and custom plates now looks good.  Found issue with return to database when saving the MOD item: (1) *** 1/21 Judy-this is still a problem***No plate description is returned to database in SHOP.PLATEDESC.  (2)  FIXED 1/21-Judythe data in SHOP.PLATENBR has too much info. s/b returning only the plate number (ie, CP0005), not with the -H or -V.  What is being returned is "CP0005-H". This messes up what's in configurator and what is written to QUDET.USR<12>.

1/22 Judy - plate desc now makes it to back end. Closing this bug.

When selecting Printed/Existing Stock Plate SP0003 - no defaults are occurring on Plate Desc, Image Hgt, Image Width. RESET.VALS should now contain default data for these fields. 

1/17(Judy) - issue with defaults is fixed.  reopened for issues with data returned to DB.

Saved Items Selection 

Sal 1/28 9:59 - This may be caused by the locations no longer working correctly after moving customer part number items from contact to customer level. Will retest after done fixing locations in Avante.

Sal 2/6/14 15:54 - Except for locations all other filtering is working. We can now close this bug as it makes no reference to locations.

Judy 2/26/14 - tested date/item#/dimensions search and looks good.

PCC ‘DIE’ items 6690,6693,6695 have no description showing

PCC ‘NEW’ ITEM 6615,30,45,50,55 have no gauge (mils) showing – ITMMST has a gauge in the item description but nothing in DIM4 ??? Not sure why. Check w/Julie?

5/5/14 (Judy) - I fixed the PCC "DIE" - no description was showing because DEV was missing the generic name code 251-MERCHANDISE BAGS WHT LD.  I've added to SYSTBL in DEV and these items now look fine.  I sent Julie an email asking why newspaper bags have a zero gauge in Dim4 of ITMMST.  I will fix these once I have heard back from her.

5/6/14 (Judy) - I heard from Julie that dimensions have been entered for newspaper bags.  I made same changes on DEV items and all looks good.

Selecting "Liners – Gusseted LD" which has defaults of Cases and Clear. It’s selecting the correct 11 records, but the item desc for 003289 and 003296 say BLK (but they are defined as clear in the ITMMST web fields).  Why does desc say BLk? 

1/12/14-These 2 items had an incorrect generic name category of 190 (BLK LINERS).  I told Julie to change to 180 (these were wrong on LIVE too) and I changed on DEV. (Judy)

Centerfold Sheeting Message

Sal 3/27/14 00:43 - Fixed, please test.

Judy 4/15/14 - Tested-looks good

Centerfold Sheeting Message explaining to "enter 24” width to open to 48”" is showing for singlewound sheeting too and shouldn’t be.  Msg only applies to centerfold sheeting.

Gusseted Sheeting Message explaining how to enter width has ‘enter’ spelled incorrectly as ‘enteer’

Results-Minimum Qty 

Sal 1/6/2014 16:11 - John has fixed RPC$MODPRODUCTITEM_
GETBYFILTER, it now returns PROD.TYPE correctly.

Sal 1/6/2014 16:13 - WEB.REQUESTEDQTY.VALIDATE now gets PROD.TYPE but it's still not triggering the validation for quantity, sent email to Judy and John asking for assistance on this.

Sal 1/7/2014 09:49 - Seems to me it's working fine now, please re-test.

Judy 1/7/14 6:05pm - still not working.  I can enter any quantity, even if it's below minimum.  The PROD.TYPE param is still coming to the back end as 300 and s/b 302.  I am working with 'gusseted tubing' 8x4x3mil.  Minimum is 20, but I can change to any number.

Sal 1/8/2014 - Changes were not yet published. Please re-test today.

Judy 1/8 - retested minimum and price issues and both are now fixed.

MOD Tubing or Sheeting by the Roll –

(1) it allows me to change the qty to < minimum qty.  It doesn’t allow this for Bags .  What I found is that PROD.TYPE isn't getting sent from UI to back end when the results quantity is changed for a MOD item. This doesn't affect BAGS, but sheeting and tubing have logic based on PROD.TYPE which isn't working.  Once you figure out why it isn't sent for quantity changes, please make sure that PROD.TYPE is being sent for Count, Freight, and Price Break changes too.

(2) When I change the qty to be < minimum then change it back to > minimum, the unit price gets all messed up.  It goes from $38 to $3.80 (MD issue??). The pricing issue doesn’t occur with BAGS when changing qty. The pricing issue may be on the back end, or may be fixed once the minimum qty fix is complete because it most likely needs PROD.TYPE too.

Tubing (or any continuous item) – the item size in the results area is showing a length and shouldn’t be (no length on continuous).  It is showing as 8x4x0 3mils.

5/5/14 (Judy) - I retested ...this was already fixed awhile back.

 Shop Widget

Results Area-Incorrect Fld Name

Sal 3/28/14 10:17 - Fixed, please test.

Judy 4/15/14 - tested - looks good

1. Results area – incorrect field heading: "Count/Thou".  *** this should say Count/Case (when in cases) or Count/Roll (when on rolls and not Continuous Sheeting/Tubing). This is based on the category and packaging selections.  In my test, I had Layflat Bags, Rolls, Cradlepacked.
2. Same as #1 except for continuous sheeting and tubing.  Heading says Count/Roll and s/b Feet/Roll.  Continuous items have no      length … packout is entered in ‘feet per roll’.  Continuous items are flagged in CATALOG.CD.USR.

Full Gauge Issue

1- Sal: RPC$MODPRODUCTITEM_GETBYFILTER is returning "FULL.GUAGE" s/b "FULLGAUGE". Please re-test

2- Fixed. Please re-test

3- Please re-test

(judy) re-tested 12/11 - all is fixed

1. I chose Layflat Bags, 30x30x1.7, VCI, Std Blue VCI/Tint in cases to zip 60499.  These options should force FULL GAUGE, but that isn’t happening.  Is the Full Gauge Default program executing?
2. After selecting FIND, it defaulted to a packout of 450 and s/b 400.  I think this may have been caused by the full gauge issue above, so I’m not worried about that yet.  But when I changed the 450 to 400 the 400 didn’t seem to stick.  The quote was created with a packout of 450.
3. On the second quote I created for the above, I clicked on Full Gauge manually.  The quote still doesn’t say Full Gauge and the price is still off.

Zip Code Validation

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

1. When in venting and choose normal or butterfly, all questions on the right are enabled.  If answered out of order, validations are not working correctly.  I believe we said that each section would become enabled only after the previous section has been answered (if applicable). 1/2/14-Only field still enabled right away that shouldn't be is 'holes per item'. If you enter anything, you get stuck in range error "1-0" because we don't have enough info yet. (Judy)
2. Order of questions in the 'Spacing' section are incorrect.  They s/b in order: (1) Holes per Item (2) Inches from Side (3) Inches from Bottom (4) Inches Between Holes.  The 'inches from side' question needs to be moved up to position 2. 1/2/14-This is fixed (Judy)
3. When selecting 'random venting' (I was working with Furniture Bags but I think this happens with any category), the 'spacing' section is not being disabled/defaulted correctly:
   1. Holes per Item is enabled (which is correct) 1/2/14-shouldn't be enabled until prior section has been selected (Judy)
   2. Inches from side is disabled but is not showing the default value which is automatically calculated 1/2/14-this is fixed
   3. Inches from Bottom is enabled (s/b disabled) and is not showing default value which is automatically calculated 1/2/14-still not showing default - shows "0" (Judy)
   4. Between Holes is disabled but is not showing default value which is automatically calculated. 1/2/14-still not showing default - shows "-". (Judy)
4. It doesn't appear that the validation programs are executing for Inches From Bottom, Inches From Side, or Inches Between questions.  This may be same reason why there are issues in 3. above with default values and enabling.  I checked WEBCRITERIA.USR and the program names to execute are loaded there. 
5. If I get error on 'holes per item', continues to next field after I click ok ... doesn't stop me from entering something invalid. 1/2/14-This has been fixed (Judy)
6. NAMED.PARAM SHOP.HOLESIDE (alignment section) is not getting set by the web no matter what I choose, so I cannot test my validation programs

Issues happen at IE9 and Firefox

12/31/13 (Judy):

1. Nbr of Holes, Inches from Bottom, and Inches Between are not being written to the database (config has 0, 0, and null respectively).
2. wHEN 'RANDOM VENTING' is selected, 'inches between holes' is disabled as it should be, but it isn't populated with anything.  Is it running the default.value program?

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.

Packaging: When I choose product categories Furniture Bags or any type of Sheeting/Sheets/Tubing, packaging is correctly defaulting to 'Rolls, Cradlepacked'.  If I go into Packaging group, I see that only 1 'cases' option is grayed out:

• Cases is disabled - both radio button and text are gray (this  is correct)
• Rolls, Cradlepacked is selected and enabled (this is correct)
• Rolls, Boxed is enabled (this is correct)
• Cases, Polylined - radio button is gray but text is enabled *** TEXT S/B GRAY

Venting enabling not always occurring correctly.

Sal 5/6/14 10:00 - Fixed, please test after next deployment.

I am not seeing the Full Gauge flag getting set to TRUE based on logic in WEB.FULLGAUGE.DEFAULT.VALUE.  I checked that this routine has been added to WEB9001 routines to be called, and it was there.  It looks like this program is not being executed at all.

1/23/14 - This was fixed in bug#18 below (Judy)

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.

Right align numerical data so it sits closer to "%" 

4/25/14 - I did not notice any difference? In the Level 3
Materials and Additives section, the data is left aligned for additives with percentages. I have included a screenshot of the staging server. 

I am looking to bring the data closer to the percent. Right align data in the entry field. Thanks. 

4/29/14 - He is talking about the entry fields. I also entered data into metalocene and uvi/uva, clicked find, went back in and the additives were unchecked but still showed in the materials hover. Cathy

Please test after next deployment

Increase vertical spacing by 10px. The spacing is too tight. It's currently 10px and should be 20px space total.

How to find this bug?
(Selects "Layflat" in category drop down within the widget and then clicks "Mat & Additives" level 3 menu.)

Sal 5/1/14 10:21 - Already fixed please test.

Steve 5/5/20012 - Looks good.

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.

Widget - remove gray arrows in initial state of widget when none of the level 3 text appears.

ED: Changed, arrows are hidden initially, shown if user selects a category, hidden again on reset.

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

Please test after next deployment

Shop

Widget - center "Find" text and icon in button. Is currently located too far left and too high vertically.

ED: Adjusted css

Wdget - make tab roll over the Laddawn purple (#850d6e) and not orange (exception is "Cart" tab).

ED: Changed rollover color to our purple.

Homepage - Change "Laddawn or Your Own Item #" text color to #999999.

ED: Changed color for all watermarks to #999999.