EXT: Abile Tickets Management¶

Table of Contents¶

EXT: Abile Tickets Management 1

Introduction 1

What does it do? 1

Screenshots 1

Users manual 2

FAQ 3

Adminstration 3

FAQ 3

Configuration 3

FAQ 3

Reference 3

Tutorial 4

Known problems 5

To-Do list 5

Changelog 5

Introduction¶

Users manual¶

• This extension is meant to be used in an intranet environment. Your visitors must be authenticated before accessing this extension as it references a frontend user entity.
• The default style sheet display the extension as a box (400 pixels width). You are encouraged to extends the style sheet to feet your needs.
• There are two frontend plugin. The first one is targeted toward “regular” frontend users, the second one is targeted toward “administrative” frontend users.
• “Regular” frontend plugin: frontend users may manage and create new tickets. When creating a new ticket, the available categories depends on the usergroups. The frontend user can personalized the display from the preference screen.
• “Administrative” frontend plugin: frontend users receive and respond to tickets. The tickets they can manage are based on their respective categories. Only the tickets from the categories matching the frontend usergroups are displayed.

Adminstration¶

• The administration of tickets is done from the frontend. The users owning a ticket may delete it as well as the administrators with matching permissions.
• The administration of tickets categories is done from the backend. The backend administrator is responsible for creating new categories and assign the “regular” and “administrative” frontend usergroups.

Configuration¶

Installing the Abile Tickets extension should be an easy task. From the extension manager, go to “Import extensions from online repository” and enter the key “abile_tickets”. The extension will be registered as a frontend plugin. To insert the plugins inside a page, create a new content in the page and select the ticket plugin from the plugin section. Next is to define the page in which the tickets' categories will be stored. Set the “Startingpoint” to this page.

• You may control the display of the extension. This is achieved by overwriting the default TSconfig properties, overwriting the stylesheet or unseting the current one, and providing your own templates. Exemples of how you can overwrite the Tsconfig are presented in the Reference page.

• Templates

  The extension makes use of the Smarty template engine. This is a geat way to seprate the logic from the display. Furthermore, it aims at helping you to develop your very own templates. In order to so so, you must configure the location of the directory were you will prepare the templates. Thisis achieve through the “templatesDir” property. In this directory, you must create to new directories called “templates” and “templates_c”. In the new “templates” directory, you must insert the three templates “editScreen.tpl”, “listScreen.tpl” and “viewScreen.tpl”. The “templates_c” directory is used by Smarty as a cache folder and must be writable. You'll find the default templates directory at the root of the Abile Tickets extension.

plugin.tx_abiletickets_pi1{
 #address of the email sender
 email.from
 #name of the email sender
 email.fromName
 #organization of the email sender
 email.organization
}
plugin.tx_abiletickets_pi2{
 #address of the email sender
 email.from
 #name of the email sender
 email.fromName
 #organization of the email sender
 email.organization
}

plugin.tx_abiletickets_pi1{
 #location of the template and template_c  Smarty templates
 templatesDir =
 #number of results to display
 listView.results_at_a_time = 10
 #number of pages to browse from
 listView.maxPages = 5
 #Should we send an email to notify the user that he recieved a ticket
 email.sendEmailOnCreation = 1
 #Should we send an summary email to the user after he created a ticket
 email.HTMLMail = 1
 #address of the email sender
 email.from
 #name of the email sender
 email.fromName
 #organization of the email sender
 email.organization
}
plugin.tx_abiletickets_pi2{
 #location of the template and template_c  Smarty templates
 templatesDir =
 #number of results to display
 listView.results_at_a_time = 10
 #number of pages to browse from
 listView.maxPages = 5
 #Should we send an email to notify the user that he recieved a ticket
 email.sendEmailOnReply = 1
 #Wether or not we should send HTML based templates
 email.HTMLMail = 1
 #address of the email sender
 email.from
 #name of the email sender
 email.fromName
 #organization of the email sender
 email.organization
}

Tutorial¶

Create a ticket category and assign the usergroups. A “Sender Group” is a usergroup with access to the “Regular” frontend plugin. A “Reciever Group” is a usergroup with access to the “Administrative” frontend plugin.

Create a page called “Ticket” and insert the “Regular” frontend plugin. Then, create a page “Ticket management” and insert the “Administrative” frontend plugin.

Known problems¶

Please give us a maximum of feedback (good and bad). Also, we encourage you to provide us new translations.

To-Do list¶

• Correct the spelling and the grammar.
• Translations

Changelog¶

November 11 2004: orgininal posting.

EXT: Abile Tickets Management - 5