#pricing module

Jan 4 

Janice - meeting notes

Location Price Change Authorization v. Price Change Authorization - Both have same design, but utilize different loads --> Is this based off the user? Who do we ship each screen to?

Price Change Authorization - Price Change Auth, you select 1 price list NOTE: FCL would be using Location Price Management (i.e. “Store Price Management”)

Location Price Change Authorization - Store level pricing, each store has it’s own price list - Grouping the authorization and creation screens together - Columns are shown to display information based off of the location price management creation screen - They mass authorize, verify, or rectify data on the other screen - Right click context menu to get full functionality; can access analysis view, which is essentially a dashboard of analytics *Phase 2 of management screen? - To delete from price change data line from authorization screen, the user must navigate back to the management screen - User can be hit with a price change that contains an error, which, in theory, can be edited/rectified on the location price management screen - Details option pulls user back to Location Price Management screen to view/(alter)?

Data vs. no data and column  When column headers are dragged with no data, the view remains as a grid  - This is preconfigured based on the code in use

Maria - meeting notes

Questions - What are the key requirements of this screen?  - Phase 1 priorities? - Will the authorization screen just be 1 screen? Keeping the screens separate 

What do you envision the screen as? Envision/Ideas:

1. Notification center inspiration (aka the grid) Home screen >  “Subject” - Permanent Price Change/Price change type “Message” - Description “Store” - Works in Store “Transaction” - Price Change link “Create Date” - Date it comes in “Action” - Authorize - Top left Toggle > View for “all users”, change terminology? - Default off for both super users and store users - Super users, has the toggle - Store users, it would be nice to not appear at all

2. Standard SP design screen Grid headings and details - Essentially, copy off of what exists on authorization screen - Price Change > have this as a link so they can hop back to it in the screen - Error > hard stop is the start date because it’s back dated. Authorization button disabled, user has to click price change link  - Stores would have the hover details Top Panel - Super users should still default to works in store, have same function --> Store field Options panel - Leave filter

Mi9 BA Flow TWO scenarios for auth: *NEEDS pending authorization

1 -->  - user without permission to auth a price change (create, hit req auth) - user with proper permissions with permission hits auth

2 --> super user authorizing multiple price changes from multiple stores off FCL mainframe