...

• The audit process starts when the user clicks on the "Audit Restaurants" button in the /restaurants age

• The user will be sent to a new route /audit-products (to be defined/confirmed with UX team)

• On this new page, we'll show the new products table for the audit restaurants experience

  • If the user goes out to another page or cancels the operation, he’ll need to restart the audit process again

  • We want this experience for now to be close to what we already have on the /editor flow

• Besides the ability to filter what's been presented on the table, the user can also download products status (the filtered products to a CSV file)

To understand the complete flow check this Figma: pending info

Check the proposed solution below to understand the navigation, technically speaking: https://rbictg.atlassian.net/wiki/spaces/IBC/pages/5243863171/DRAFT+-+Solution+Audit+unavailable+products+on+DOP#New-front-end-page-development

Today we already know that the application has performance problems to deal with big content on the table (high loadings, slowness, etc.). To deal with this problem, we have the following proposals:

1. To-do

2. To-do

✅ Proposed Solution

New front end page development

...

export interface AuditProductsState {
  auditableProducts: Record<string, desiredFragmentHere>;
}

/**
 * Audit products redux store
 */
export const auditProducts = createModel<RootModel>()({
  state: {
    auditableProducts: false,
    filters: {
      // any desirable filter, if we want
    },
  } as AuditProductsState,

  reducers: {
    /**
     * Method to set the auditableProducts
     */
    setAuditableProducts(state, payload: desiredProductsInterface) {
      return { ...state, auditableProducts: payload };
    },

    // any other filter reducer if necessary
  },

  selectors: slice => ({
    auditableProducts() {
      return slice(state => state.auditableProducts);
    },
  }),
});

import { Models } from '@rematch/core';

// ...rest of the code
import { auditProducts } from './audit-products';

export interface RootModel extends Models<RootModel> {
  // ...rest of the code
  auditRestaurants: typeof auditProducts;
}

export const models: RootModel = {
  // ...rest of the code
  auditProducts,
};

Front end to-do: Do we need a pagination system? The solutions to deal with performance problems and queries will answer that.

• Note: If yes, we can consider using the Material UI pagination component because it is very flexible and we can customize the visuals if we want (the app appears to lack a pagination component for the tables)

Solutions to deal with performance problems and queries

To-do

📈 Metrics

...