Financial Assurance Module
  • Financial Assurance Module Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • User roles and permissions
    • Financial Assurance Module Navigation
    • Overall User Interface
    • Engagements section
      • Creation of Engagement
      • Reporting of Engagement
      • Submitting of Engagement
      • Finalize the Engagement
      • Export of Engagement
      • Cancellation of Engagement
    • Staff Spot Checks section
    • FAM workflow
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Backend Module structure
    • Data Model
    • Fixtures & management commands
    • Integration with permissions framework
    • Interaction with VISION
    • API Documentation
      • Error Handling
    • Frontend
      • Module structure
      • Build process
      • Tests
Powered by GitBook
On this page
  1. TECHNICAL DOCUMENTATION

Fixtures & management commands

To manage some data we use fixtures & custom commands. Mostly custom commands are used for managing email templates and for updating permissions, because their definitions are complex and hard to control using fixtures.

  • python manage.py loaddata audit_staff_organization - load information about UNICEF audit organization

  • python manage.py tenant_loaddata attachments_file_types - load list of file types for attachments

  • python manage.py tenant_loaddata audit_risks_blueprints - load full set of risk blueprints questions) which are used for Micro Assessment questionnaire & for some similar blocks

  • python manage.py loaddata audit_groups - load set of required groups for module

  • python manage.py update_notifications - update email templates

  • python manage.py update_audit_permissions - update module related permissions

All commands are designed to be safely executed multiple times without data duplication, so they are recommended to run after every deployment to be sure that actual data will be provided.

PreviousData ModelNextIntegration with permissions framework

Last updated 6 years ago