Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: CFA 2019R2
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      CFAMX 2019R2 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      5
    • Work Type Classification:
      Sustaining

      Description

      Story
      As an Operator in InFORM, I would like addresses for Offsite Sales Locations validated upon saving them.

      Notes
      HotSchedules will use SmartyStreets for Offsite Sales Location addresses entered in InFORM. The user will input the address in the Address 1 field. When the first values are entered and space is entered, the first call to the Autocomplete API will take place. The call made by the Autocomplete API is not considered a hit (or a charged call).

      US Autocomplete API

      1. Does not validate street number
      2. Returns valid street+city+state combinations
      3. When consuming smartystreets api, the host header must be set to the value provided by smartystreets
      4. We currently do not start autocompleting until a street name is typed
      5. SmartyStreets offers a City and State filter
      6. Geolocate - prefers address suggestions in the user’s city/state depending on IP address

      The US Street Address API is the actual validation performed on the address. This call is a charged call and returns the county and zip code for the location.

      US Street Address API

      1. Provides full validation of address
      2. Response returns validated address along with county and zip code
      3. Addresses that validate to multiple addresses will allow for selection of the correct address
      4. At most an address will only require one request to validate after it is submitted and multiple addresses come back
      5. Request that have no response (no address matched the result) will require more since the address will need to be corrected and validated again
      6. Once submitted/saved, will validate address (cost per call)
      7. Two outcomes
        • 1st possibility: no address found
        • 2nd possibility: multiple address - North, South. Missing ..etc
      8. Enter City and State and UI will not let you enter County or Zip Code
      9. Once you hit save, multiple addresses found, you need to pick, N. or South
      10. Populate other data gathered by the original call. After you make a selection, it disregard the other changes and not recall the api.
      11. Toast Messages on OSM UI:
      12. No valid address found (Red - Error)
      13. Multiple addresses found (orange/yellow - warning)

      Acceptance Criteria
      Auto Complete
      Confirm when typing the beginning of an address and hitting space and typing a letter, a box is displayed with results.
      Confirm the returned values are similar to the address value entered.
      Confirm the values in the box are sorted with locations closest to location first.
      Confirm the user can select one of the returned results.
      Confirm after selecting a returned result, the city and state values are entered in the UI.

      Street Address
      Confirm if no address is found, a error label is displayed.
      Confirm the error label for no addresses found is in red
      Confirm when an address has several hits, the user can select the correct address.
      Confirm when an address has several hits, a warning message is displayed in orange.
      Confirm after the address validation is performed, the county is filled in.
      Confirm after address validation is performed, the city, state and zip code are filled in.
      Confirm the user can enter a new address 1 and validation is performed again.

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                staten.putnal Staten Putnal (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 9h 40m Original Estimate - 9h 40m
                  9h 40m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11.25h
                  11.25h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.