In order to handle which car statuses are shown at some Grid lists we have created a set of setup pages in order to manually change which car statuses can be shown:
~/SetupEntities/NewUsedSetupCarStatusFilters
- Setup statuses that filter the vehicles, at UsedVehiclesGridListWithMappedStatuses page.
~/SetupEntities/UsedSetupCarStatusFilters
- Setup statuses that filter the vehicles, at InventoryVehiclesGridListWithMappedStatuses page.
~/SetupEntities/MapCarStatusesForActionsShowedAboutReservations
- Setup statuses to show reservations actions, at VehicleCardPage page.
~/SetupEntities/MapCarStatusesForActionsShowedAboutSales
- Setup statuses to show sales actions, at VehicleCardPage page.
~/SetupEntities/TestDriveCalendarEligibleCarStatuses
Filtering at the pages UsedVehiclesGridListWithMappedStatuses and InventoryVehiclesGridListWithMappedStatuses can now be changed from a setup key that is configurable from the above pages.
Any actions on the VehicleCardPage page can now be changed from a setup key that is configurable from the above pages.
For manual changes, the setup keys are:
- NewAndUsedPageMappedCarStatuses
- UsedPageMappedCarStatuses
- ReservationsActionsMappedCarStatuses
- SalesActionsMappedCarStatuses
Development notes
At InventoryManager class, 2 new methods were implemented:
- GetEligibleCarStatuses
- Returns a list with the string representation of each CarStatus enum based on the business logic we want to execute.
- CanExecuteBusinessLogicByCarStatus
- Returns true or false if the given car status exists in the business logic we want to execute.
In conjuction with the above methods there exists the following enum which can be considered as "mapping" for the 4 setup pages above:
- CarStatusBasedBusinessLogic
- This enum basically contains the name of the setup key used for each set of car statuses.
0 Comments