Background actions when using client deceased / inactive logic
Understand what background tasks are performed when a client is deceased or inactive
When the client deceased / inactive process is initiated, the following workforce data is updated in the system.
Single Jobs
- Job object:
- Future single jobs that have one of these statuses (Queued, Pending Allocation, Pending Dispatch, Dispatched, Ready), will be cancelled (job status updated to Cancelled) with below information populated from the configurations for single jobs:
- Cancellation reason
- Cancellation note
- IsBillable
- Future single jobs that have one of these statuses (Queued, Pending Allocation, Pending Dispatch, Dispatched, Ready), will be cancelled (job status updated to Cancelled) with below information populated from the configurations for single jobs:
- Job Service Item object:
- Associated JSIs will have the data populated in the below fields:
- Cancellation checkbox updated to True
- Cancellation reason
- Cancellation note
- IsBillable
- Associated JSIs will have the data populated in the below fields:
- Job Allocation object:
- Future job allocations of above single jobs that does not have one of these statuses (Deleted, Completed), will be deleted (job allocation status updated to Deleted)
- The late cancellation process (Activities created for the Resources to get paid for) will kick in for the eligible jobs.
Group Bookings
- Group Attendee object:
- Group attendees of future group jobs that have one of these statuses (Queued, Pending Allocation, Pending Dispatch, Dispatched, Ready) will be cancelled with below information populated from the configurations for group jobs:
- Attended checkbox updated to False
- Cancellation reason
- Cancellation note
- IsBillable
- Group attendees of future group jobs that have one of these statuses (Queued, Pending Allocation, Pending Dispatch, Dispatched, Ready) will be cancelled with below information populated from the configurations for group jobs:
- Job Service Item object:
- associated JSIs will have the data populated in the below fields:
- Cancellation checkbox updated to True
- Cancellation reason
- Cancellation note
- IsBillable
- associated JSIs will have the data populated in the below fields:
Group Event Templates
Group clients of group event templates that have status equal to Active, will be removed/deleted.
Single Jobs in Base Templates
- Any single jobs (past or future) belong to base templates will be removed/deleted from the base template (the association between the job and the base template will be removed)
- When the single jobs happen to be future jobs and belong to a base template, they will be cancelled and removed from the base template at the same time.
Group Jobs in Base Templates
- Group Attendee object:
- Group attendees of any group jobs (past or future) that belong to base templates will be:
- Cancelled with below information populated from the configurations for group jobs:
- Attended checkbox updated to False
- Cancellation reason
- Cancellation note
- IsBillable
- Cancelled group attendees will not be included in the replication process
- Cancelled with below information populated from the configurations for group jobs:
- Group attendees of any group jobs (past or future) that belong to base templates will be:
- Job Service Item object:
- Associated JSIs will have the data populated in the below fields:
- Cancellation checkbox updated to True
- Cancellation reason
- Cancellation note
- IsBillable
- Associated JSIs will have the data populated in the below fields: