Signals
Django includes a signal dispatcher that allows adding reactions on certain actions easily. Besides djangos built-in signals juntagrico sends the signals below.
Job signals
job_canceled
Trigger: Job is saved with the cancelled flag set (and the flag wasn’t set before).
Arguments:
instance: The job instance that was cancelled
Default receivers:
handle_job_canceled: Send notification email to members that were signed up to that job and remove them from the job.
job_time_changed
Trigger: Existing job is saved with a changed time field
Arguments:
instance: The job instance whose time was changed
Default receivers:
handle_job_time_changed: Send notification email to members that are signed up to that job.
subscribed
Sender: Job
Trigger: Member subscribes to a job
Arguments:
instance: The job instance that the member subscribed to
member: Member that subscribed to the job
count: The number of assignments
Default receivers:
none
Subscription signals
sub_created
Trigger: A new subscription has been saved.
Arguments:
instance: The subscription instance that was created
Default receivers:
handle_sub_created: No action.
sub_activated
Trigger: A subscription, where deactivation date and activation date was not set already, is being saved with an activation date.
Arguments:
instance: The subscription instance that was changed
Default receivers:
handle_sub_activated: Checks that none of the members has overlapping subscriptions when this one is activated, and raises an exception otherwise. Sets the activation date of the parts and the join date of the members according to the new activation date.
sub_deactivated
Trigger: A subscription, where deactivation date was not set already, is being saved with a deactivation date.
Arguments:
instance: The subscription instance that was changed
Default receivers:
handle_sub_deactivated: Sets leave date of all members of subscription to the deactivation date. Sets the deactivation date of active parts and deletes parts that have not been active yet.
sub_canceled
Trigger: A subscription, where cancellation date was not set already, is being saved with a cancellation date.
Arguments:
instance: The subscription instance that was changed
Default receivers:
handle_sub_canceled: Sets cancellation date of all active parts of subscription and deletes the not yet active parts.
Extra subscription signals
extra_sub_activated
Trigger: None
extra_sub_deactivated
Trigger: None
Subscription part signals
sub_part_activated
Trigger: A subscription part, where deactivation and activation date were not set already, is being saved with an activation date.
Arguments:
instance: The subscription part instance that was changed
Default receivers: None
sub_part_deactivated
Trigger: A subscription part, where deactivation was not set already, is being saved with a deactivation date.
Arguments:
instance: The subscription part instance that was changed
Default receivers: None
Member signals
member_created
Trigger: A new member has been saved.
Arguments:
instance: The member instance that was created
Default receivers:
handle_member_created: Send email to admins, that member has been created
member_canceled
Trigger: A member that had no cancellation date set, is saved with a cancellation date.
Arguments:
instance: The member instance that was changed
Default receivers: None
member_deactivated
Trigger: A member that had no deactivation date set, is saved with a deactivation date.
Arguments:
instance: The member instance that was changed
Default receivers:
handle_member_deactivated: Remove the member from all activity areas.