Which task is NOT part of adding a generic schedule to a line of business?

Adding a generic schedule to a line of business involves several key tasks that ensure the schedule is properly integrated and functional within the product model. Creating a generic schedule data model is essential because it sets the framework for how the schedule will store and manage data. Configuring schedule properties in the product model is also necessary, as it defines how the schedule behaves and interacts within the broader context of the product and its various conditions. Additionally, configuring the schedule's user interface is important to ensure that users can easily interact with and input information into the schedule.

On the other hand, deleting existing schedules is not a task typically involved in the process of adding a generic schedule. This activity pertains more to maintenance or cleanup rather than the creation and integration of new schedules within the policy or business context. Hence, the focus of the question is on tasks specific to the addition of a schedule rather than its removal or alteration.