Migrate "Customers > Outstanding" page

[MatShir]

Part of Symfony migration project
Type: page

Enable B2B mode in Customer Setting then go to Customer to find the Oustanding page.

• Migrate page Migrate "Customers > Outstanding" #20288
• Multistore header: Specs

Check-List (copied from #13989)

App layer

Controller / routing

• All controller actions are migrated and protected with @AdminSecurity annotations when eligible and @DemoRestricted annotations when eligible
• All links targeting this page are updated: either using _legacy_link or updating the code
• The new SF routes have _legacy_link and _legacy_parameters provided and explained
• Controller catches Domain Exception and translate them nicely
• Add/Edit controllers must catch global Exception in order to handle ModuleErrorException

Template

• Twig templates must contain relevant blocks to allow partial extension by modules
• Twig forms must have form_rest() and form_errors()
• JS being used on the page can be used as enabled extensions and use a PageMap for selectors
• Use @PrestaShop instead of PrestaShopBundle for template root path aliasing

Conventions

• The new controller actions comply with our naming convention
• The new SF routes names and paths comply with our naming convention
• The new Twig template names comply actions with our naming convention
• Created files (controller, JS assets, CSS assets and twig views) must be in the right folder following the convention
• CSS being added must follow theme conventions

Core layer

• Commands and Queries only use native types but internally use VOs
• All Handlers must have an Interface

Conventions

• The created SF service names comply with our naming convention
• The created files must follow the folder convention (Domain, Core, Adapter...)

Polishing

• The legacy controller and templates files are gone
• If PR includes a new concept/mechanism, documentation must be written
• JS and CSS assets must be compiled and up-to-date
• License headers must be up-to-date
• New hooks have been added to the hooks list and the SQL updates
• Performance must be correct: page loading time, filtering/sorting/searching response time, actions response time

Testing

• Commands and Queries are tested with Behat tests
• Eligible Core classes are covered with unit tests*
• Controller is covered with survival test
• (soon) Controller is covered with E2E tests using puppeeter
• If we break E2E tests because IDs change, we must update the E2E tests

*Eligible = easy to isolate and unit tests provide values (for example testing getters/setters is useless)

[Progi1984]

@MatShir Do you know if this issue needs to be remained opened ? I think all is done.

I checked the header multistore and it's present.

Ping @matks

[Progi1984]

I check all points. And i fix a last point in #27649.