URLs

---

This specification is to detail the URL path requirements for Centurion ERP development.

Details

The following URL patterns are required for navigation:

• /<module>/<model>

• /<module>/<model>/<primary key>

• ~~/<module>/<model>/<common pk>/<child_model>~~

• ~~/<module>/<model>/<common pk>/<child_model>/<primary key>~~

• /<module>/<common model name>/<model>

• /<module>/<common model name>/<model><primary key>

• ~~/<module>/<common model name>/<model>/<common pk>/<child_model>~~

• ~~/<module>/<common model name>/<model>/<common pk>/<child_model>/<primary key>~~

The url path pattern will be used by both the end user facing URL and the API URL for accessing the backend.

URL path patterens will be in format:

/<module>/<model>/<primary key>

sub-path names are as follows:

• <module> is the module the url falls under

• <model> is the Django model name

• <primary key> is the Primary key of an individual item.

Example of a device url: /itam/device[/<int:pk>].

The above url path pattern does not work for common models that are accross different modules. As such, for common models, the parh patter is as follows:

/<module>/<common model name>/<model>/<primary key>

sub-path names for common models are as follows:

• <module> No change

• <common model name> the common model name, this will be the Django model name

• <model> The sub-model name. i.e. the name that differantiates it from the common model name.

Example for a request ticket: /assistance/ticket/request[/<int:pk>] .

Requirements

These Requirements are to be read as a must be done unless otherwise stated. URL requirements are as follows:

• All characters are lowercase

• space characters are replaced with underscore _

• Back-end and API access to have /api prefixed to the path.

About:

This page forms part of our Project Centurion ERP UI.

Page Metadata

Version: ToDo: place files short git commit here
Date Created: 2024-09-27
Date Edited: 2026-05-17

Contribution:

Would You like to contribute to our Centurion ERP UI 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