Skip to content

Under development

Xavi edited this page Aug 26, 2018 · 3 revisions

The features below may be incomplete due to development status or because we already work with them in our corporate server and don't need to develop them completely.

Departments

Member departments are not yet configurable within PanicHD menues. If you want to use in PanicHD your Laravel app existing department list, you may:

  • Fill up "panichd_departments" table with your data or delete and replace it with a view of another table of yours, keeping needed fields for PanicHD
  • Enable departments in PanicHD by changing PanicHD "departments_feature" configuration setting in the menu configuration > other

Department notices

It deppends on a table structure that is not created by PanicHD. The package only holds department models and behaviour.

You can assign -laravel auth- users to departments (table migration not included in PanicHD). Each made relation is understood as a "department user": An user account that is linked to the department. To do the trick, these "department users" may own each department email or distribution list email. When you create a ticket and you specify an owner wich is a "department user", there will happen two things that do the magic:

  • An email will be sent to "department user" email containing the ticket information: The department employees get email notice about the new ticket.
  • All real users that belong to that department will see (and will be able to read) this ticket on top of the ticket creation page

With this feature working, when there is an scheduled or unexpected issue that may affect a department (or anyone), you only need to create a ticket that is owned by the affected department to let the users in that department know what you're informing of. They'll receive an email automatically and also you can post any updates of that issue on the ticket. Our intention here is to avoid multiple tickets, phone calls or emails that may slow down your work.

Clone this wiki locally