Hi Rohan,

Yes, you can customize the Angular classic component to work differently for different pages. Here are some approaches you can take to achieve the desired customization:

Custom Filters: To have different sets of filters for different pages, you can make the filters configurable by using input properties. For example, you can create an input property called filters and pass different filter configurations to the component based on the page. Inside the component, you can then use these filter configurations to display the appropriate filters.

Conditional Visibility: If you want to show/hide buttons based on specific requirements or for certain pages, you can use conditional rendering techniques. You can add boolean input properties to control the visibility of buttons and set their values based on the requirements or page context. Inside the component's template, you can use Angular's structural directives like ngIf to conditionally render or hide buttons based on these input properties.

Dynamic Redirection: If you want the "Create" button to redirect to different add pages based on the current page, you can again use input properties to pass the respective page URLs to the component. Inside the component's logic, you can handle the button click event and programmatically navigate to the appropriate add page using Angular's Router module.

You can customize the component to adapt to different pages with varying filters, button visibility, and redirection behaviors. Leverage Angular's component-based architecture and features like input properties, conditional rendering, and routing to achieve the desired customization.

If you need further assistance or have specific questions regarding implementation details, feel free to ask.