(self)
return self.initial_schedule and self.initial_schedule.ui_type == Schedule.UI_TYPE_CUSTOM_IMMEDIATE
The custom immediate schedule is provided for backwards-compatibility with
        the old framework which allowed that use case. It's not as useful of a
        feature as the custom daily schedule, and the framework isn't currently
        responsive to changes in the custom immediate schedule's events (and neither
        was the old framework), so we restrict certain parts of the UI when editing
        a custom immediate schedule.

        If these edit options are deemed to be useful, then the framework should
        be updated to be responsive to changes in an AlertSchedule's AlertEvents.
        This would include capturing a start_timestamp and schedule_revision on
        the AbstractAlertScheduleInstance, similar to what is done for the
        AbstractTimedScheduleInstance.
The custom immediate schedule is provided for backwards-compatibility with
        the old framework which allowed that use case. It's not as useful of a
        feature as the custom daily schedule, and the framework isn't currently
        responsive to changes in the custom immediate schedule's events (and neither
        was the old framework), so we restrict certain parts of the UI when editing
        a custom immediate schedule.
The custom immediate schedule is provided for backwards - compatibility with the old framework which allowed that use case . It s not as useful of a feature as the custom daily schedule and the framework isn t currently responsive to changes in the custom immediate schedule s events ( and neither was the old framework ) so we restrict certain parts of the UI when editing a custom immediate schedule .
def editing_custom_immediate_schedule(self):
        """
        The custom immediate schedule is provided for backwards-compatibility with
        the old framework which allowed that use case. It's not as useful of a
        feature as the custom daily schedule, and the framework isn't currently
        responsive to changes in the custom immediate schedule's events (and neither
        was the old framework), so we restrict certain parts of the UI when editing
        a custom immediate schedule.

        If these edit options are deemed to be useful, then the framework should
        be updated to be responsive to changes in an AlertSchedule's AlertEvents.
        This would include capturing a start_timestamp and schedule_revision on
        the AbstractAlertScheduleInstance, similar to what is done for the
        AbstractTimedScheduleInstance.
        """
        return self.initial_schedule and self.initial_schedule.ui_type == Schedule.UI_TYPE_CUSTOM_IMMEDIATE
def editing_custom_immediate_schedule ( self ) : return self . initial_schedule and self . initial_schedule . ui_type == Schedule . UI_TYPE_CUSTOM_IMMEDIATE