Offsite Sales Management

BRD: https://drive.google.com/open?id=1d6QudieBw6lKjG89LNkaOylmzmHC_8RdpJti9yNb_t4

FRD: 
https://docs.google.com/document/d/1lkwisaP8r0Y0QljsdxMzuyHkdQrEFb9_hWuj8vHyrJE/edit?usp=sharing
 

Business Purpose Chick-fil-A would like to add functionality to InFORM for tracking sales captured outside the boundaries of a physical restaurant. The functionality, titled “Offsite Sales Management” or OSM for short, would provide restaurants with the ability to specify a physical location located outside of the restaurant. The location entered in InFORM will be pushed to the Point of Sale (POS) for selection.

Detail To gain greater business visibility into where sales are being physically captured, and to determine which sales locations are most profitable (i.e. is selling at that stadiumn 1x/week really making me money?), a new Offsite Sales Management page is being requested for Restaurant users to track the different physical locations where they sell product outside of the Restaurant. This listing of locations would then be passed down to the Store’s POS Server via Livelink --i.e. the same methodology we use for Customer accounts and PettyCashCategories. From there, ServicePoint would consume the list so that a ServicePoint user could choose from a list of Offsite locations when they take a register offsite. Sales then get tagged as being tied to a specific offsite location, which is passed back to InFORM.

Detailed listing of requirements:

• Create a new MxConnect page called “Offsite Sales Management”.
• This new page should be accessed under the Daily Sales drop-down on left hand navigation pane in MMS. The new MxConnect Offsite Sales Manangement page should then display within a frame.
• Navigate to the Offsite Sales page and see a listing of each of my Restaurants.
• After selecting one of my Restaurants in the drop-down I can then choose from the saved Offsite locations tied to that Restaurant number, or create a new location (max length of 30 characters for name).
• Once I create an Offsite location, a  unique "ID" value is generated for storage purposes only in the InFORM system. This value can be displayed but not edited.
• I can edit any of the data fields except for OSM ID and click "Save" to save my changes. Attempting to navigate away with unsaved changes results in a warning message prompting to save, similar to other MxC pages.
• I can check/uncheck the "Active" flag for a location. For this initial feature request, both Active/De-activated locations will still show in the drop-down list.
• When creating OR editing a location, enforce a full address is entered--Address Line 1, City, County, State, and Zip are required fields whenever a save is performed of either a new or existing record.
• When De-Activating a location, an email is sent to ServiceNow with Month of de-activation (I.e. “This Offsite Sales Location has been ended with end-date: September 2018”)
• In the top right section of the OSM page, a text section with basic instructions should be visible (see mockup) than can include HTML tags and edited by a system admin.
• Each time a new OSM is created, or an existing OSM is saved, InFORM should generate a new XML file listing the ACTIVE OSM names to send down to the POS.
• The file being generated needs to include both the OSM Name as well as Address Line 1, Address Line 2, Address Line 3, City, County, State, Zip. See mockup.
• The file should be placed via Livelink in the C:\Program Files\Radiant\Lighthouse\CFAConfigDataImporter\Import directory on the POS server (same as Petty cash file and customer account file).
• Livelink should be updated to properly pass through a new transaction attribute- the OSM ID which user selected--and store this in InFORM in the transaction data model. Note: for this initial request, we do not need to display this data anywhere in the UI (the additoinal OSM attribute will be sent to our real-time streams and intial reporting will be done via that channel).
• When LIvelink passes down the information to ServicePoint, the address should also be included in the XML file. See mockup XML file attached here.

ServicePoint -

File Push:

File format for servicepoint file consumption.

The file will be different from previous service point files because of address fields.

File Pull:

What will be in the TLD file to identify the OSM?

What should the RLD changes be?

 
HLE Notes