Laddawn.com : Action items

New Issues + Agenda for 9/6/12

What should the user see if they make a selection that would cause the "open" section to become disabled? Do we collapse the section, or disable all the controls inside the section.

When you discuss this, don’t forget. We will not be changing any values, because they didn’t set anything. However, that section is expanded with nothing answered. So it would not reset their options, they said not printed.I guess I could rephrase this question to be “do we want to disable whole sections for anything other than selecting a product category?
For instance: If the user clicks on printing (expanding that area) then they enter a width of 6 thereby disabling the printing area. What should the user see?

Answer: This selection is going to reset your printing options. Do you want to proceed? (Answer - Yes; printing menu closes up, and is grayed back.)

If the user had not made any changes in the "open" section of area 3 that needs to now become disabled, close the section, do not validate for mandatory fields, and disable the link.

New issues + Agenda for 8/30

Please log any NEW issues here as well as topics for the 8/30 agenda

Status of action items from 8/23
Developers' concern about additional categories that are made, in some cases stocked, as layflat and gusseted; particularly when "all" is left in the depth field.
Status of key programming tasks - John, on behalf of everyone, what are they, and where do they stand.

Current issues

^{The "Edit Document" button is not working as intended. We're working on a solution. To access the file, go to Tools menu, select Attachments, and download a local copy of "issues test.xslx." If you wish to make a change, please save a local copy and upload the file with the exact same name (Confluence has versioning).}

Meeting notes and action items, 8/23

Misc housekeeping

Susan continues to research solutions for simple issue tracking - these include spreadsheet (whether embedded in wiki page or not), Outlook tasks, and perhaps other tools such as Sharepoint or open source solutions that Ed and John have used. Do we also need a separate bug tracking tool, or would a generic issue/task tracking tool suffice? Ed and John to research that.

Widget and Level 3 issues

Yes, the programmers would like to get the Level 3 stuff completed soon so we should focus on it. Owen, they liked what you had done in terms of defining the relationships and validations between choices that would be made in the shadwoboxes. That said, this is work that they can do and you shouldn’t worry about doing this moving forward. What they really need is the details of how the individual fields will lay out and function in the screen, the overall “design”. Here is an overview of how I think the boxes will layout and function. Let’s review, and fine tune:
1. M&A: Since the material is generally a single choice and the additives multiple choice we thought they should be kept separate. We could use a drop down for materials. That said it seemed logical to make two separate check box lists and have the logic disable and enable available choices in both lists that have resulted from other choices made inside and outside of this shadowbox. Note: some additive fields would have/reveal and addition box for the “percentage” when/where required.
2. Colors: Two drop down lists or check box lists of available color and “type”. The logic would enable/disable based on previous choices and require one color and one type choice.
3. Printing: It was decided that all questions should be displayed so that the customer understood what was available. The logic would enable/disable individual questions and or make default choices based on previously answered questions.
4. Venting: It was decided that all questions should be displayed so that the customer understood what was available. The logic would enable/disable individual questions and or make default choices based on previously answered questions.
5. Packaging: For consistency we should use a shadowbox and have a drop down list of available choices. The list should disable any choices that were unavailable due to previously answered questions. NOTE: Judy reminded us that we have to account for “Folded In Half” where applicable. Maybe we just have a “Folded In Half” checkbox when available.
  ACTION ITEM - OWEN TO CONFIRM NO LATER THAN TUES, SOONER IF POSSIBLE. STEVE HAS BEGUN WORK, BUT WILL RECEIVE MORE SPECIFIC GUIDANCE BASED ON ABOVE TUES.
  UPDATE - 8/28/12: The recommendations above need to play out as part of the iterative design process. We expect another round of designs from Steve Borowick on Thursday, and plan to present them (probably still works in progress) at 8/30 programmers meeting.
We came to general agreement on how the overall validation logic was going to function in the Shop Widget:
1. When a field is entered the system will validate the rules for that field. If there is an error it will return an error and reset the field to its original state. If the field is not in error it will then validate all other fields in the widget to see if any new errors have been caused as a result of the newly entered field. If so, the system will return error offering the option to reset the field that has been “placed” in error or reset the field that was newly entered. When applicable the error message will describe the range that is valid for the error field. As each error is detected and acted on the system will recheck all other fields again to make sure the full configuration is errorless. We should have Steve design a popup/dialogue box for errors.
  ACTION ITEM - OWEN TO CONFIRM NO LATER THAN TUES, SOONER IF POSSIBLE
  CONFIRMED 8/28/12
Programmers had some concerns about the “text information” associated the Level 3 boxes. Would prefer to just go “Modified” when something was changed rather than trying to abbreviate various choices for various boxes. Owen, I couldn’t remember how adamant you were about the abbreviations. Alternative could be a “tooltip” over the word “Modified”.
ACTION ITEM - OWEN TO CONFIRM NO LATER THAN TUES, SOONER IF POSSIBLE
Discussed with Owen 8/28/12; for Materials & Additives, he is OK with "Modified" representing all changes; however, he'd prefer that his original specs be used for the other menus.
Any time a choice is made in the widget the default values of all other fields will change accordingly. This will happen only to fields that have not been updated previously by the user. We agreed to tow this line in the Packaging screen (or other screens) even if the user had brought up the screen but made no change to the choice.
ACTION ITEM - OWEN TO CONFIRM NO LATER THAN TUES, SOONER IF POSSIBLE
8.28.12 - upon further review with Owen we decided that clicking on a Level 3 choice should set the fields of information to "changed" status so that a warning was issued if they were to be overwritten later. IT seemed logical that if a user did go to the screen he was likely "confirming" the information in the screen and that we should not then override without a notification.
Micron issue resolved - group agreed that UI for mils addresses this.

Proposed agenda items 8/23

Level 3 requirements
Resume discussion of dimension validations? (See 8/14 below.)
The text that you want on the main screen when various choices are made on those pop-ups. Some documentation says Standard / Modified, other documentation says abbreviations. If the answer is somewhat mixed, ie if the abbreviations are longer than 20 characters, use modified.
How do we want to handle validation errors? May relate to the second bullet point.
How will enabled vs disabled fields be shown on the screen. Are we going to gray them out or hide them?
John, Judy, Cathy, Ed - log agenda items here if you have any

Agenda 8/14

We did not meet as planned, although we had a conversation with Judy about validations for dimensions.

Action items from 8/9:

Owen

- Flesh out requirements for level 3 menus in the Shop widget.
- Something else that I didn't get
- Judy added: Owen will supply programming with a spreadsheet of low/high width ranges for stock item categories (including transmetallic shielding)
- STATUS OF THESE?

Ed

- Finish integrating Neptune's work into the Shop widget and restore operability.
- Create "mid-tier groups" for. Search Field and Search Group. (N-Tier objects)
- Follow through on color specs for shadow boxes and widget tabs.
  - We still want blue borders for shadow boxes opened from Cart screen, and purple borders for shadow boxes opened from the other 4 purple tabs.
  - We still want the Cart tab to be blue, whether it is the active tab or not.
- DONE

Judy

- Program validation routines (and other routines - what were they again? Judy added: up to 4 routines per question: VALIDATE, ENABLED, GETLIST, DEFAULTVALUE) in John's absence.
- Someone will create a template to simplify and standardize programming. Cathy added: John sent a template to us on Friday not sure if it is complete. (I stuck this under Judy, but wasn't sure who is responsible for this. And when are you shooting to have it done?) Judy added: I am going to attempt the first set of programs for WIDTH this week while John is gone. Other validation routines from above bullet will be a joint on-going effort
- STATUS OF THESE?

Susan

- Research issue/task tracking solution, wiki-based or other. STATUS: Some progress made, still researching. SP, 8/22
- Capture in Shop tab requirements:

Tension between desire to "let them do anything they want" v. conflicts between dimensions (W, D, L, G - level 2) and level 3 menus (mainly printing and venting) - forward/backward sequence of entry of choices.

1. 1. Incomplete dimensions - Printing cannot be set til dimensions entered. Attempt to set printing will generate warning that dimensions needed in order to proceed with printing choices.
  2. If dimensions are set, printing set, then dimensions changed, routine will check existing rules to see if it can be done; if some new dimension doesn't work, or requires further printing/venting input (calls prior settngs into question), warning will appear. ( ? )

STATUS:See notes from discussion on 8/14; more detail is probably needed. -SP, 8/22

- Get answer: Ed and John need to know what happens after full gauge selected to indicate the choice made. Susan will follow up with Steve et al. (part of Steve's backlog). Anticipating showing in widget, and including in details for search results. STATUS: This has been decided; am in process of updating Shop requirements page, and have reviewed with Ed. -SP, 8/22
- Some items are microns not mils. (missed this part) - a concern not an immediate concern. STATUS: Will capture as an issue to be discussed at a future date.