(self)
return (self.configuration_filter_value['active'] or '').lower() != 'false'
The `active` parameter is only used for debugging.

        To use it, just pass active=false into the URL and the report will then only show
        inactive schedule instances.

        This shouldn't be made part of the user-facing filters because an inactive schedule
        instance might show a next event due timestamp that looks confusing. For example,
        for a one-time reminder that sends today at 9am, after it sends it will show as inactive and
        have a next event due timestamp for tomorrow at 9am because it has moved past the last event
        in the schedule and that's what deactivated it. That's normal behavior but would look
        confusing to a user.

        This can be a useful tool for developers when debugging.
The `active` parameter is only used for debugging.
The active parameter is only used for debugging .
def show_active_instances(self):
        """
        The `active` parameter is only used for debugging.

        To use it, just pass active=false into the URL and the report will then only show
        inactive schedule instances.

        This shouldn't be made part of the user-facing filters because an inactive schedule
        instance might show a next event due timestamp that looks confusing. For example,
        for a one-time reminder that sends today at 9am, after it sends it will show as inactive and
        have a next event due timestamp for tomorrow at 9am because it has moved past the last event
        in the schedule and that's what deactivated it. That's normal behavior but would look
        confusing to a user.

        This can be a useful tool for developers when debugging.
        """
        return (self.configuration_filter_value['active'] or '').lower() != 'false'
def show_active_instances ( self ) : return ( self . configuration_filter_value [ 'active' ] or '' ) . lower ( ) != 'false'