✔ Create new history model

[jon-nfc]

History is a core feature that tracks the changes to a model, including related models.

📝 Details

Create a new model that will be a proxy model for history entries. This model will then be used (proxied) by each "model's history" which will contain only the model details.

This model should replicate the current history table with the exception of the model details which will subsequently move to their "own model history table" per model.

This base model must contain a function that is used to create the history entry. the before, after, model fields should be passed directly to this function. Function should return bool

🚧 Tasks

• Model Created
• [ ] Model tag added to app/core/lib/slash_commands/linked_model.CommandLinkedModel.get_model() function
  • [ ] Tag updated in the docs

Note

Ensure that when creating the tag the following is adhered to:

• Two words are not to contain a space char, \s. It is to be replaced with an underscore _
• As much as practical, keep the tag as close to the model name as possible

• Admin Documentation if applicable

• Developer Documentation if applicable

• User Documentation

• 🟨 Migrate old date to new tables

Old history table models

appsettings
cluster
clustertype
configgrouphosts
configgroups
configgroupsoftware
device
devicemodel
deviceoperatingsystem
devicesoftware
devicetype
externallink
groups
knowledgebase
knowledgebasecategory
manufacturer
operatingsystem
operatingsystemversion
organization
port
project
projectmilestone
projectstate
projecttype
service
software
softwarecategory
softwareversion
team
teamusers

---

🧪 Tests

• Unit Test Model
• Unit Test Serializer
• Unit Test Tenancy Object
• Unit Test ViewSet
• Function Test ViewSet
• Function Test API Metadata
• Function Test API Permissions
• Function Test API Render (fields)

---

• Abstract test cases
  • checking if entries created for Add, and Update of a model.
  • on delete of model confirms history is deleted
  • Child model Add, Delete and update entries never be delete if child model is deleted

✅ Requirements

A Requirement is a must have. In addition will also be tested.

• [ ] Must have a model_tag not a required feature as the hitory is a log not an item

---

• Model contains the "create entry"
  • returns bool for success/failure