AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
      • Log Rule
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
        • Log Solution
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  • Module Standards
  • Inheritance Standards
  • Entity Standards
  1. Checks
  2. Domain Model

Domain model standards

Check ID
DOM_0005

Category

Standards

Summary

This check will ensure that your domain models meet your standards.

Options

See the table below for all available options.

Pass

The domain model or model element matches your standards.

Fail

The domain model or model element does not match your standards.

Module Standards

Option Name
Details

Security Roles

The maximum number of security roles that a module may have. Default: 5

Maximum Entities

The maximum number of entities that a module may have. Default: 50

Maximum Logic Flows

The maximum number of logic flows (microflows + nanoflows) that a module may have. Default: 150

Inheritance Standards

Option Name
Details

Administration Module

If TRUE, entities may not inherit from Administration.Account. Default: TRUE

System Module

If TRUE, entities may not inherit from the System module (except for System.FileDocument, System.User and System.Image). Default: TRUE

Limit Inheritance

If TRUE, inheritance must be limited to a maximum of 2 levels. Default: TRUE

Entity Standards

Option Name
Details

Maximum Access Rules

The maximum number of access rules that an entity may have. Default: 15

Maximum Associations

The maximum number of associations that an entity may have. Default: 15

Maximum Attributes

The maximum number of attributes that an entity may have. Default: 20

Maximum Event Handlers

The maximum number of event handers that an entity may have. Default: 5

Maximum Optional Validations

The maximum number of optional validations that an entity may have. Default: 5

Maximum Validations

The maximum number of validations that an entity may have. Default: 10

Delete Behaviour

If TRUE, associations must define a delete behaviour. Default: TRUE

PreviousAnonymous users cannot change unlimited length stringsNextAnonymous user access restricted

Last updated 12 months ago