Several things are done here, the results of which are unilaterally assumed by all other SimpleDesk functions. - work out which departments are applicable, and which department we are currently in (as far as possible) - set up general navigation - see if the URL or POST data contains a ticket, if so sanitise and store that value - see if a msg was specified in the URL, if so identify the relevant ticket - add in the helpdesk CSS file - identify the sub action to direct them to, then send them on their way.

• since: 1.0

This function sets up multiple blocks to be shown to users, defines what columns these blocks should have and states the rules to be used in getting the data. Each block has multiple parameters, and is stated in $context['ticket_blocks']:

• block_icon: which image to use in Themes/default/images/simpledesk for denoting the type of block; filename plus extension
• title: the text string to use as the block's heading
• where: an SQL clause denoting the rule for obtaining the items in this block
• display: whether the block should be processed and prepared for display
• count: the number of items in this block, for pagination; generally should be a call to {@link}
• columns: an array of columns to display in this block, in the order they should be displayed, using the following options, derived from {@link}:
  • ticket_id: the ticket's read status, privacy icon, and id
  • ticket_name: name/link to the ticket
  • starting_user: profile link to the user who opened the ticket
  • replies: number of (visible) replies in the ticket
  • allreplies: number of (all) replies in the ticket (includes deleted replies, which 'replies' does not)
  • last_reply: the user who last replied
  • status: the current ticket's status
  • assigned: link to the profile of the user the ticket is assigned to, or 'Unassigned' if not assigned
  • urgency: the current ticket's urgency
  • updated: time of the last reply in the ticket; states Never if no replies
  • actions: icons that may or may not relate to a given ticket; buttons for recycle, delete, unresolve live in this column
• required: whether the block is required to be displayed even if empty
• collapsed: whether the block should be compressed to a header with count of tickets or not (mostly for {@link}'s benefit)

• Assigned to me (staff only)
• New tickets (staff only)
• Pending with staff (for staff, this is just tickets with that status, for regular users this is both pending staff and new unreplied to tickets)
• Pending with user (both)

• see: \shd_count_helpdesk_tickets()
• since: 1.0

$context['dept_list'] contains the list of departments that the user can see, key/value pair, array is ordered according to the ordering specified in the Departments administration area. The key for $context['dept_list'] is the department's id, with the array content being: - id_dept - departmental id (numeric) - dept_name - department's name - tickets - an array containing three elements, open, closed and assigned - containing the counts thereof for each department for the current user. - new - boolean whether this department has some new items to be read by the current user The linktree is also modified to inclue the department list.

• see: \shd_get_unread_departments()
• since: 2.0

This provides the ability to see all of a given type of ticket at once without paging through them, which are all sortable.

• see: \shd_main_helpdesk()
• since: 1.0

Much like the main helpdesk, this function prepares a list of all the closed/resolved tickets, with a more specific list of columns that is better suited to resolved tickets.

• see: \shd_main_helpdesk()
• since: 1.0

Much like the main helpdesk, this function prepares a list of all the deleted tickets, with a more specific list of columns that is better suited to recyclable or permadeletable tickets.

• see: \shd_main_helpdesk()
• since: 1.0

Actually performs the queries to get data for each block, subject to the parameters specified by the calling functions. It also sets up per-block pagination links, collects a variety of data (enough to populate all the columns as listed in shd_main_helpdesk, even if not entirely applicable, and populates it all into $context['ticket_blocks']['tickets'], extending the array that was already there.

• see: \shd_recycle_bin()
• since: 1.0

In order to centralise the list of actions to be displayed in a block, and in its counterpart that displays all the values, the lists of columns per block is kept here.

• see: \shd_recycle_bin()
• since: 1.0

Parameter: $block

Expected type: string

The block we are calling from: - assigned: assigned to me - new: new tickets - staff: pending staff - user_staff: pending with user (staff view) - user_user: pending with user (user view) - closed: resolved tickets - recycled: deleted tickets - withdeleted: tickets with deleted replies