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

(1) search for furniture bags & then change qty on item 3205 to 10, available should change from 6/5/2014 to 6/7/2014 (manufactured item)

(2) search for saddle pack deli bags & then change qty  on item 6700 to 1000, available should change from 6/5/2014 to 9/3/2014 (purchased item)

Quantity, s/b: "Quantiy 8.4 Thou"; missing "Count/Case 450" on far right.

Labels listed vertically should be bold gray.See Steve's revised spec below. (I would refer to the original spec but I felt the fake data in it would confuse matters...)

Staging

Steve's revised spec

Get a spinner when I hover over 'Yes" under exact match. In firebug the error is "item is not defined" ?; within the pop-up I can hover elsewhere and hovers work fine, but when I close out of popup, site has frozen up. Need to close tab and reopen. (This doesn't seem to happen when item is not an exact match.)

Cart save message

Field 53 of the contact record stores which pop-ups they do not want to see.  These codes are found in SYSTBL SUPPMSG.LAD. UI needs too call  RPC$CONTACT_SUPPRESSMSG. Pass in FLAG = ASC.

Specs have a "don't show me this again" checkbox; this is not showing in the staging version.

Some of the DEFAULT.VALUE back-end widget programs aren't working correctly because they no longer have the default value of all previous fields.

Note: Bug #240 has been canceled.  This takes its place.

UI Side - when calling RPC$SEARCHFIELD_GETDEFAULTVALUES, need to pass to the back end a delimited list of the shop widget field names for any field that has 'changed'. 

DB Side - Modify RPC$SEARCHFIELD_GETDEFAULTVALUES (again) to update the SHOP. named params with the default value for each field.  Only update the SHOP. name if the field has NOT changed (if it exists in the delimited list sent by the UI, do not change the contents of the SHOP. param).  *** This is logic that you already coded awhile back (without the list of changed fields), and since setting some of the defaults was causing major problems with the widget because default.value was null (overlaying dimension fields such as Width, Length, Gauge), we removed the code.  Unfortunately, the code was not preserved (sorry). 

Also, please remove the special logic in FCT.BTWNHOLES.DEFAULT.VALUE, FCT.COLOR.DEFAULT.VALUE and FCT.OPACITY.DEFAULT.VALUE where it's executing FCT functions to try to determine the default value of previous fields.  Once this new logic is in place, you should just be able to use the SHOP. variable (ie, replace DMATERIAL with SHOP.MATERIAL)

To test, try Layflat Bag, In Materials check 'VCI'.  The FCT.COLOR.DEFAULT.VALUE program should immediately change Color = Std Blue VCI and FCT.OPACITY.DEFAULT.VALUE should immediately change Opacity = Tint.

2nd test: Layflat Bag, 12x24x2mil, Venting, Normal, Random Venting, One Side, 3 Holes per item:  defaults s/b: 4" from side, 5" from bottom, 5" between holes

Design adjustments for Share Shadowbox (part 2 - Share with Customer)

1. Delete "X" should be white when using this orange format. Gray when using white/gray stroke format.
2. Entry field data too close to entry box. Please move over 4px.
3. "%" is touching entry box. Move over 4px.
4. Labels should use #666 gray.
5. Description header/text and Specifications/text indented. Please align with rest of elements.
6. Please remove single quotes in both paragraphs.

• PS: Freight terms should not be included when sharing items or carts with customers. -sp, 6/4/12

A couple of bugs with validation errors and behavior when going between both aminefree choices and and incompatible color selections.

Hold off until bug 259 is done

Select layflat; then color/opacity (leaf green/tint); then expand materials menu; then select anti static - aminefree pink. BUG-1:Do not get error message (should see 033:  ERR.MSG = "Color must be Pink for AmineFree Pink" (and “do you wish to continue?”, and color being changed to pink only after saying Yes). Instead, no msg, and color menu automatically changed to pink, tint.

After selecting milspec type, color menu disabled. (Good?)

Next, click amine free clear/color - get 'pink cannot be selected for aminefree clear/color; continue yes/no, click yes. Color menu reenables, changes to clear (Good.)

Open color menu - select leaf green/tint. Reopen materials menu.

Aminefree clear/color still selected (Good); all other anti-stat parameters still intact. Switch to aminefree pink; BUG-1 (again): no error message; color menu automatically chagnes to pink/tint...

BUG-2: color menu is still enabled ...

Reopen color menu; pink/tint selected; change color to med blue; get error msg: 'color must be pink for amine free pink; click ok; top menu selection changes to pink, tint, but medium blue radio button still selected onscreen - remains this way even after collapsing color menu, expanding materials (don't make changes), then reexpanding color menu.

Availability Date in Results for a Purchased Stock Item is incorrect when there are no purchase orders

6/4/14 JC:  issue involved the REQUEST.QTY not being initialized.  Changed code to set REQUEST.QTY to 1 if REQUEST.QTY = ""

Created new deli bags items in DEV.  These are purchased items, and they have no p/o's established yet.  They have no inventory in INVWHS yet (except for one of the items).  When I do a search for Saddle Pack Deli Bags, I see the 6 items 6700, 6703, 6705, 6707, 6710, 6713.  All have a date of tomorrow (it's late in the day). Only item 6700 has inventory.  The other 5 items have no inventory and no purchase orders but are also showing tomorrow's date.  The purchasing lead time is 90 days, so it should be showing DATE()+90 as a date for these 5 items.  Please check logic in WEB.AVAILABILITY.OPTIONS.

Also, LD.INCLUDES WEBPRODUCTITEM.READ has a hardcoded qty of 1 with a note saying this should be replaced with REQUESTED.QTY at some point.  Please investigate what is needed from the UI to make this program work with REQUESTED.QTY instead of a hardcoded 1.

When I click the purple product name/dimensions for this particular item in the cart, it does not expand to show full product description. However, it does expand when it is in the results list.

Design adjustments for Share Shadowbox

1. Please increase vertical spacing by 15-20px.
2. "Share this Item" font should by Scala Sans bold and not arial.
3. "Sharing with a customer? text should be 16 px bold arial black. Also tighten up
   line-spacing by 2-4px.
4. Please make sure Yes/No radio button are black. They look gray on the staging server version.
5. Remove colons on To, CC and Subject labels
6.  Tighten up vertical spacing between entry fields by 2-4 px.
7. Make cover note text #666 gray. Also, remove all text after 1st sentence.
8. Increase vertical spacing after Purple rule by 8px.
9. Move data fields closer to labels. "Standard, clear, sideweld, should be 16px away from largest label, "Material & Additives"
10. Place 1px gray line around image. Should be same color as rule used as label dividers. (#CCC)
11. Place 1 px pipe #CCC in between print and cancel links.

On the heels of the task below in 252 (returning MOD 1362 to widget), reopened M&A menu; changed material from 'non scratch' - to 'standard' additives appearing to re-set after changing material (boxes all now unchecked) - but seem to be retained in the M&A hover tooltip - before (1)  and (2)  after clicking find.

Before clicking 'Find'

After clicking Find

I returned a MOD I had just saved to the widget (MOD 1362). I notice the following issues with the way the Godzilla results are shown:

1. Since I intentionally pulled MOD 1362 into the widget (v. entering parameters from scratch that match it...) should it be included in the Godzilla results? Seems confusing. But for sake of argument let's assume it should be included...
2. Since they are one and the same thing - the stuff that is highlighted in yellow should  not be highlighted - they're not differences, they're matching attributes. And the line in the "Exact Match" column should begin, "Yes" not "No."
3. Materials is listed too many times in the 2d Godzilla result.
4. This has some/all of the same issues reported previously in 229

 Cart Name not clearing between users (potential problem for CE)

SP, 5/29 - see also issue 228.

Login as contact 17278, place item in an unnamed cart, logout;  do not close browser; login as contact 17264 who does not have an active cart; go to cart, cart name is now the prior bill-to number (33224).

All additives are selectable and should not be; and am able to run search.

Customer creation using contact number for contact (attribute 26), should be null

Janice 5/30/14:  the drop ship flag is not being set properly.  This needs to be fixed on the UI side as well as the backend.  UI needs to send the proper flag via SHIP.MODE and the backend needs to set the drop ship flag on the customer accordingly.

In checkout, entered new customer information & when the order was created, it created a new customer but the contact is the contact number, this should be null.  Also, the drop ship flag (attribute 17 in CUSTMST.USR) is not being set.

Janice 5/30/14:  the SB user (CUSTMST.USR <2>) needs to be modified as well:  IF OPERATOR # '' THEN set to SB user ELSE "WEB" & inactive flag (CUSTMST.USR <75>) can be null - doesn't need to be 0.

Open 

M&A menu, Metallocene - line wrapping

Chuck 06/02/2014 Test after next deployment

sp, 6/4/14, fixed

Can we squeeze "storage" onto the same line? Would prefer that this does not wrap; if it does, would prefer storage to align under "Metallocene"

Staging:

Specs:

Done

I ran a tubing search with widget settings that I thought would return a stock match (1885) but it only returned MODs; I finally figured out that it was setting gauge to full as soon as I selected "layflat tubing" (not easy to notice if you're not expecting it). I tested all the other categories under tubing & sleeves and it is happening for gusseted tubing; not happening for any of the others in that group.

Since we make these products at nominal gauge it should not be forcing full gauge, correct?

Searching using the item number produces the exact stock match, plus two less expensive, nominal gauge MOD results:

Cannot add to cart.

SP, 5/29 - 11:30 am. Worked with Sal; it seems to be working. Could be a latency issue. Will keep an eye on it. Marking "hold."  Will close if it doesn't happen again today.

Reversing width/length produces correct YMAC result?

2-part issue with zip code

Zip code not clearing between unique users; an unlikely scenario for real customers, but a potential problem for CE. (Clicking reset and clearing cache do not resolve; zip persists.)

Regardless, zip code not passing from saved item back to widget.

Log in as Joan (customer 002180).

Joan's starting widget - populated with zip code last used by Sally (and NOT by Joan; Sally works for customer 2916):

Joan's active cart (upon login - no searches or additions since login):

Joan's saved items:

Result after pulling MOD 1343 into widget - widget not back-populating with the original zip code for the saved item.

Started from scratch. Cleared active cart; started with empty cart and no zip in it. Reset widget (had to clear zip field manually). Returned Saved MOD 1329 to widget. Got prompt for empty zip code. This should not happen; item should back populate with its original zip code and is not.

(Discovered while testing issue 194.) Something funky going on with MOD pricing when going from results to cart.

Ed - please work with Wayne on this for DB information.

1-Fresh MOD result, after clicking "Add" (with min quantity; data correct)

2-View upon moving to Cart tab (price is correct, but there is a spacing issue)

3-After rounding quantity up to nearest K (Price plummets.. incorrect data?.)

Back End DEFAULT.VALUE programs need to know what fields have been changed

6/4/14 (Judy) - I canceled this bug.  It was re-entered as bug #259 above and assigned to Chuck and Wayne.

DEFAULT.VALUE programs need the SHOP. variables to contain the default values from previous fields.  If we know which fields have been manually changed (meaning the UI won't use the default value), we can change the SEARCHFIELDS program to reset the SHOP. variable to the default value.

Once this is complete, Judy will revisist all DEFAULT.VALUE program to remove un-needed logic.  All programs should the be able to use the SHOP. variables.

I think this is happening when spaces are typed - 2 variations below.

Save item from result (RIGHT)

Vs. Save item from cart (WRONG)

Availability date and pricing are off for this stock select search

6/2/14 (Judy):

1. price on first item is because this is a new item from marketing and no price has been established in DEV.DATA.  This is a data problem.  I have setup a price for Butler in DEV.
2. 12:00 availability date - we've discovered that this happens on all new items from marketing where the Plant/Item Parameters haven't been established yet (so we don't know if the item is Made/Purchased/Transferred).  We're thinking that the UI should either display null if no date is returned or possibly 'Click Chat'.  This situation shouldn't occur on LIVE because this info has to exist for MRP to plan for the item properly.  This is definitely a DEV data issue.  But we should handle it more gracefully on the customer-facing side. 

Related to issue 30 & 102?

Cannot access anything having to do with saved items.

SP, 5/29, seems to be resolved. Closing.

Strange things happen (inconsistently) with MOD availability date when I toggle freight for results.

Different packaging should not change the availibility date of an item.

Search 1: 1 MOD exact, 1 MOD YMAC, both have 6/20 avail. date. Toggle freight for first result to not included; date changes to 6/11. Toggle freight for YMAC result to not  included, date changes to 6/11. Toggle freight back to included for each  - date remains at 6/11.

Search 2: 1 MOD exact, 1 MOD YMAC. Both have 6/20 avail. date. Toggle freight for first to not included, date changes to 6/11. Toggle freight for YMAC, date stays at 6/20. Toggle freight back to included for each, date remains at 6/11 for both.

WEBPRODUCTITEM_GETBYFILTER is sorting by GAUGE.  This dictionary is correctly setup as a N’umeric Right-Justified field, but because the data in this ITMMST field has the decimal point stored, it doesn’t sort correctly.  Right justified it sees 1.25 as being higher than 1.5.  Left justified fixes this problem, but once we get to 10+ the sorting will be wrong again.

Specs say:

"To get a Godzilla result you need to enter all required dimensions including gauge; but gauge matches in Godzilla will still include items with different gauges. "

See also issue # 165 - this is another 'no results when there should be' set of results. I believe I should be getting the "We can make gussetted bags - enter full dimensions bla bla bla"(and close stock matches?)

Editorial/formatting issues with Godzilla

 Chuck (06/04/2014): Please test after next deployment. Not sure what CSRL is either. It's coming from the database. Maybe 'Case/Roll' count.

SP, 6/4/14 - reopening, but most orig issues have been fixed (thanks)

We should strip out CSRL; I suspect it is a prefix to "Count"; it's not intuitive - "count" should be sufficient.

Most issues fixed, see comments in cell to the right, and issues noted below which I did not see first time around:

Under Exact Match column head:

• What is CSRL? - let's eliminate
• Please insert spaces after period and commas. Fixed
• Items should not wrap; use ellipses if content spills onto another line.Fixed
• Exact Match column head should end with question mark.Fixed

Product comparison tooltip box:

• Only differences should be highlighted in yellow; since Sally is the user who just ran this search, she should not be highlighted here.Fixed
• Should be "Count/Case 450" Fixed, but at the time I failed to also note that quantity should be "8.44 Thou."
• Font colors, bolding of labels, do not conform to spec. However, I have a question in to Steve about consistency; I will update w/details later.
  (SB) 1. Please make all labels #666 gray and bold (Item Owner, Ship to, Count/Roll or Count/Case, Quantity, Materials, Color, Printing, Venting and Packaging.Fixed
• (SB) Make all content black and regular text. Sally Draper should not be in bold.Fixed
• (SB) Pleas move entire tool tip to the left so it doesn't float outside the shadowbox so much. If it needs to expand dynamically, have it do so within the original shadowbox if possible.Fixed
• (SB) We should place colons after Ship To, Count/Roll and Quantity labels.Fixed

Tried this as two different users, 2 different bill to organizations.

Update (3:25 pm): Here is another wrinkle - these 2 different users from 2 different organizations seem to have the same active cart - though the contents are different. I am pretty sure I had saved Joan's cart under that name before creating Sally's cart from scratch. I am pretty sure I never named Sally's cart "joan's humonguous cart"; I will attempt to recreate from scratch.

Update 3:33 pm - logged sally out and logged back in. Cleared cart. Started new cart w/same 2 stock items. Saved as "Sallys petite cart"; logged sally out, logged back in as Joan. Widget was populated with zip code used for Sallys petite cart. Searched for some new items. Put in cart, clicked to cart, cart already named as sally's petite cart.

The "joan's humonguous" and "sallys petite" appear in both users saved carts lists. Here is Joan's

1-I get partial red error message, in spite of apparent success sharing the item.

2-There is no sharing history showing in saved items list for the item being shared (mod 1266,  customer 2916, contact 17279) - am guessing it just hasn't been programmed yet, reporting just in case.

Godzilla issues

SP, 6/4/14 - confirmed w/Judy that if an item exists in both a cart and the saved items list, there should be one entry in the list per location.

To test Godzilla, I ran a search for something similar to but different from one of my saved items:

• Saved MOD1266 - 17 x 8 x 23 x 004, blue/tint, non-scratch, 300/cs
• Fresh MOD: 17 x 8 x 003, standard M&A; color-clear, 400/cs .

I got the Godzilla result verbiage and link (good); clicked link to open pop-up; expected to see "saved items" as one of the locations (and MOD1266 under names/tags column). Instead, only saw saved cart (4/22) as location. Based on hover details, I had clearly returned MOD1266 as the similar item. I clicked the saved cart link and was brought to saved cart tab with empty list, but the cart name field was populated.  (Not sure what happened to all the saved carts, I am pretty sure there were some recently.)

Saved item that fresh search was based on:

My fresh result

My Godzilla pop-up

Differences between saved and fresh highlighted appropriately.

• Missing Saved Items as a location?
• Missing "MOD1266" from name/tags column? (Also, tried similar searches with other MODs that have product location / use tags, and those are not showing in this column either..)

This is what I saw when I clicked Saved Cart link:

• Was the cart old enough to have expired? Before I re-read the specs, I would've guessed that if the Cart had expired, we would not see it as a location in the Godzilla pop-up, or that we could still access an expired cart on this tab.
• Actually, the specs say expired carts are their own distinct type of location, and describe what should happen when you click "expired cart" -"Clicking on this will bring the expired item back into the widget and through to a result."

In Progress

I am not getting the prompts I should be getting when returning Saved MOD to widget and changing freight terms or zip code.

5/28 (Judy) - this has not been programmed yet

The design specs state:

Once Find is clicked (with new zip) or freight terms are changed - user is prompted to answer question regarding intent for this quote (verbiage needs work; we will not reference quote numbers ) - 

Is it your desire to:

(a)    revise your current quote [0001] or

(b)    create a new quote [0002]?  

Either way, you must save to preserve your changes .

Answering ‘a’ will reprice quote 0001 with this zip code and/or freight terms, based on original resin price and quote clock.

Answering ‘b’ will create a new quote in progress with this zip code and/or freight terms, based on today’s resin price.

I am not getting that prompt.

Not seeing pricing history when I expected to. Either Wiki specs are wrong (or I am misunderstanding them) or this is a bug. Please advise.

5/27 (Judy) - Per John, this has not been programmed yet.  Will be taken care of when we add the 'changing existing price' question. I will leave this bug open so that it can be tested when programming is complete.

Logged in as customer 2916, contact 17279. Retrieve MOD 1294 saved on 5/8.

Widget seems to back populate appropriately and shows 1294 as an exact match (presumably with current resin prices).

RE what should happen next (when all the user has done is retrieve the item), the Wiki states:

• Pricing shown is based on current resin prices. It is autosaved as a new quote (0002) with a new quote clock (T+14).
• Q: Does the user have to save to preserve changes? What happens when the user saves or adds to cart at this point?
  • A: Saving is not necessary since the pricing autosaved as a new quote, and no other changes were made. However, clicking “save” is an opportunity for the user to modify tags, or the part number in the case of MODs. The saved item dialog box opens with original tags (and optional part number if applicable).

When I return to Saved Items, I do not see any pricing history icon (see design series 4 within Saved Item design specs):

The entry fields (active and disabled) need some adjustment.

1. Remove inner shadow on entry fields (Ship to, Size & Gauge). Leave the background white.
2. Disabled entry fields (ties in with issue #4). Remove inner shadow. Make stroke #ccc gray. Make background #eeeeee. Make disabled text #666666.

Leave in focus entry field as is. looks great.

Leave drop down as is.

Related to Susan's discovered issue #165.

I tried to do a broad search and it just froze. No results would show.

Wayne - please test this to see if it is still an issue.  If it does not happen, please make sure to check with Steve on his steps to try and recreate.  We think ths may be fixed.

sp, 6/5/14 - I don't think it "froze" for Steve; I think he thought it froze b/c he got nothing. please be sure to look at #165. To this day, I continue to get no results for certain searches when I should - incomplete dimensions for products that we should be able to make (and quote, with complete dimensions given).  I don't log them b/c we have this issue and #165 already open and assigned. Please let me know if you'd like to see additional examples.

1. Move icon closer to "Find" text
2. Make button width smaller by 15-20 px
3. I'd like the drop shadow softened. It's too dark and floated to the right.
   I'd like to try using css-box shadow x-width of 0 and adjusting the blur radius and spread-radius to closer match the designed version.

Ed: Adjusted accordingly. Please specify a color in the future, no guessing here! 

Deployed to staging Friday, 23 May @ 4:30pm

Issue  I:

Selected micro-perf; all other fields appeared disabled, but I could not proceed with that selection due to validation error. Tested in production and there are no further inputs when micro-perf is selected.

Issue II

Changed venting selections from micro-perf to normal, random, both sides - entered 3 in number of holes...

...and got this error:

These settings are allowed in production with a bag of this type/dimensions:

I was able to proceed without getting error with normal, random, one side, 3 holes and normal, user specified, 3 holes, 2" side, 2" bottom, 6" between. Was able to click Find, widget scrunched up,but then nothing happened - didn't get a spinner. After 3 minute wait, abandoned all hope.

Gauge not fully resetting with product class/category change.

Chuck (06/03/2014) The full gauge is coming back from the database for all sheeting. This I by design.

Edits/formatting in zip code conflict pop-up

Chuck (06/03/2014): Test after next deployment

Sp, 6/4/14 - fixed

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.

Ed: No line breaks needed, adjusted css accordingly. Hyphen is a data issue from back end messaging, write up bug as separate issue.

Deployed to staging Friday, 23 May @ 4:30pm

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.

Not getting market place results.

Janice - test this on Avante and see Judy

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.

Chuck: 06/03/2014: Please test after next push to staging

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.

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.

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

  And with 11W/all-D/all-L, 2 gauge, I get this:

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

SP, 5/27 - cleaned out outdated reports above. Issue still happening with certain searches that I am able to execute on production site (albeit with complete dimensions).

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

Availability pop-up, stock, full quantity not available at primary warehouse

SP, 5/27 change status to hold due to open questions RE availability pop-up functionality (see 188+189)

Please see edits below.

Availability pop-up, stock, full quantity not available at alternate or primary warehouse

SP, 5/27 change status to hold due to open questions RE availability pop-up functionality (see 188+189)

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?

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

Test

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

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

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.

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.

Sal 5/23/14 9:58 - John is looking into adding the packaging group to our current business object to address this issue.

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.

Judy 6/3/14 - re-tested but 'x' on error box still leaves bad data and allows you to 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.

Chuck 6/2/2014 - test after next deployment

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. 

Chuck (06/03/2014) - Sorry, I thought you were referring to the dashed '–' in the textbox. I changed the border to be #CCCCCC as well. Please test after next deployment and let me know if the dashed should go back to #999999.

FF

Chrome

Shop