Notice: React: 3.x | Store: 0.x

Portal

MyAccount is a canonical app built in all VTEX stores. This app serves as a hub of apps, meaning that it is the entry point for all apps that want to be available for the store's customers.

The app is responsible for handling customer's personal data such as: profile info, passwords, addresses, orders and credit cards. Orders and credit cards are responsibilities of other two apps that come per default with the MyAccount, respectively, these apps are: vtex.my-orders-app and vtex.my-cards.

Be aware that VTEX does not offer support for a customized My Account. For more information, contact the front-end developer responsible for the module.

This app provides a few extension points in order to allow apps to customize stores' experience as needed.

First, make sure you have the store-builder as a dependency in you manifest.json:

Now, create the file store/interfaces.json and define some interfaces:

If you want to block the editing of the document in the my account form, use the props blockDocument

Prop name	Type	Description	Default value
blockDocument	boolean	Enables or disables editing the document field in MyAccount	undefined

---

Usage: To block the document field, follow these steps:

1. In the index.tsx in /react file, the blockDocument property is received from the main store. Pass this property on to AppRouter

2. Pass the property to the ProfileEdit component

3. In the ProfileEdit component, pass the property to theProfileFormBox component

4. In the ProfileFormBox component, pass the property to theProfileContainer component. Just remembering that this component is imported from the vtex.profile-form app

5. Follow the steps below in the app ** vtex.profile-form **

The names my-app-link, my-app-page, MyAppLink and MyAppPage may be whatever it makes more sense for you app.

Lastly, create a store/plugins.json file like so:

Creating a my-account-page component

Now create a new file in the root of the "react" folder with the name "MyAppPage.js".

In this example you will have two new pages /account/#/support and /account/#/points, rendering the UserSupport and UserPoints components respectively.

Creating a my-account-link component

This component will receive a prop called render. You must call it with an array of objects with the properties name and path. This will create the link given the name and the path provided.

Example of an MyAppLink implementation:

After creating a new page, you can define the default path that will be rendered when the user opens the URL /account/.

1. Open the Site Editor admin (/admin/cms/site-editor).
2. Navigate to the My Account page
3. Click on the "My Account - Home" extension point on the Site Editor's menu
4. Fill the field "My Account's default path" to the new path

Following the previous examples, we could fill it with "/points", to open the UserPoints page.

Inside the Profile page, right above the edit button, there is another extension point. This one is intended for stores that collect custom data from their customers (such as their hair color or their pet's name). This extension point allows your component to display such information without breaking the page layout.

Usage: Your component shall not render anything: you will simply call the render prop with the appropriate data and it will be displayed together with the user's default information. You should pass in an array of objects containing label and value props. label is the name of the field you which to display (such as Hair color) and value is the value for such field (such as brown). Keep in mind that you must run any necessary preprocessing in your data by yourself before displaying, such as masking or localizing your texts. Also, it is up to you to fetch the data from wherever it is.

Example

If you are going to display tailored data inside your customer's profile, you probably want to edit that info too. The last extension point, my-account/profile/input, lets you do that. It will place whatever content you want inside the profile editing form, right above the 'toggle business fields' button, and also use functions provided by you to validate and submit that content.

Usage: Your component may render form components, texts or anything else as desired. We recommend sticking to VTEX's Styleguide or your own design guidelines to avoid breaking the style from the rest of the form. You also receive two props, registerValidator and registerSubmitter. As their names suggest, you must use them to register your validation and submission functions with the main component. You should use componentDidMount to do that. This way, when the user hits 'Submit', your validation function will be called. We then expect you to validate all of your fields and display messages to the user if necessary. If something is invalid, your function should return false in order to halt the submission process, and return true otherwise. The function may either return the boolean value directly or a Promise which will resolve to the appropriate boolean value. When all validation is passed, the form enters submission state. It will now send the default profile information to VTEX's databases and call your submit function so you can do the same. Do not place user interaction or anything related inside that function besides submitting, since the app will return to the display page as soon as all the submitter functions finish executing and anything you display will probably not be noticed by the user.

Example