Ticket

---

Ticketing is a base model within Centurion ERP. This base provides the core features for all subsequent sub-ticket models. As such extending Centurion ERP with a new ticket type is a simple process. The adding of a ticket type only requires that you extend an existing ticket model containing only the changes for your new ticket type.

Core Features

• Centurion Object assosiate to ticket

Assosiate object to ticket

All models within Centruion ERP can be assosiated to a ticket unless otherwise stated. Whenever the model is created, a meta model is created and used at runtime.

History

Ticketing does not use the standard history model of Centurion ERP. History for a ticket is kept in the form of action comments. As each change to a ticket occurs, an action comment is created denoting the from and to in relation to a change.

Model

When creating your sub-model, do not re-define any field that is already specified within the model you are inheriting from. This is however, with the exception of the code docs specifying otherwise.

Testing

As with any other object within Centurion, the addition of a feature requires it be tested. Test for ticketing follows the model test suites, however the source for the inherited tests are the ticket tests that your model inherits from. for instance if you extend TicketBase, your test suits will inherit from TicketBase model tests.

About:

This page forms part of our Project Centurion ERP.

Page Metadata

Version: ToDo: place files short git commit here
Date Created: 2025-04-16
Date Edited: 2025-09-23

Contribution:

Would You like to contribute to our Centurion ERP project? You can assist in the following ways:

• Edit This Page If there is a mistake or a way you can improve it.
• Add a Page to the Manual if you would like to add an item to our manual
• Raise an Issue if there is something about this page you would like to improve, and git is unfamiliar to you.

 

ToDo: Add the page list of contributors