** **

1. ability to create request

2. formworks

3. payments work/stripe

4. successful submission of the form 

5. see in database

6. receive email and customer data

7. slack should get a notification of scheduled 

8. Amin users are able to dispatch 

9. complete service

** **

 QA Testing Proposed — V 

• Users can create manual entries for a driver.

• Users can see the location details where drivers and riders have passed self-assignments; 

• In Progress & needed for development relevant checks Vizcayanance
  > Users can edit driver profiles w/ NFT: TODO WEB3 > Use case adds to matrix testing: true.

• *Vizcayanance > Use case is dev environment and testing criteria for Florida drivers criteria data; *

1. Get more for your ride with Web3 Profile NFTs.
   i.e., Templates for test bucket criteria. 

2. What is the target release date for new features? TBD.

**Vizcaya - Policy Update Any new Updates?  (HR Internals);

NFT Card Element
(https://opensea.io/assets/matic/0x2953399124f0cbb46d2cbacd8a89cf0599974963/25363633882811259677655475115441041506376770999752812718481829689430659563521);

Event Name Booking
A simple SHA1 hash function for JavaScript supports UTF-8 encoding. Example (https://github.com/emn178/js-sha1); **

    <nft-card

    contractAddress="0x2953399124f0cbb46d2cbacd8a89cf0599974963"

    tokenId="25363633882811259677655475115441041506376770999752812718481829689430659563521">