Can't add Blackout Schedule to application scopeIssue Customers are using a Global scoped application to move configurations between instances. When adding a Blackout Schedule to the application, the Schedule Entries aren't included.ReleaseXanaduCauseThis is because the Business Calendar Entry table does not extend the Application File table (see below).Application File (sys_metadata) -> Business Calendar (business_calendar)--> Schedule (cmn_schedule)---> Condition Schedule (cmn_schedule_condition)----> Blackout Schedule (cmn_schedule_blackout)Business Calendar Entry (business_calendar_span)-> Schedule Entry (cmn_schedule_span)ResolutionThis is working as expected. The Business Calendar Entry table does not extend the Application File table and hence the table records will not moved if the application is deployed to another instance. To move records to the target instance, please consider using import sets or create the records dynamically via script.