This documentation should only contain classes from the /obj hierarchy.
How to document a class
The name of the page should be the same as the name of the class.
It is not necessary to document every method and variable, that kind of detail belong in the source code. The documentation should describe the purpose of the class, basic usage, complicated things, dependencies on other parts of Microbizz, external resources, and everything else that isn't suitable for inclusion in the source code. An example of typical use is a good thing.
Base objects
Record
Record2
Record2Bulk
Customer
Project
Todo
Tool
User
Person
UI elements
FileUI
Form
Infobox
Layout
LayoutButtons
LayoutModuleBar
LayoutTab
LayoutTopmenu
Quickmenu
Record2QuickEdit
Record2QuickEdit2
Sidebar
SettingsUI
Timeline
Integrations
See also Technical documentation
ApiBridge
CVR numbers
Direct Connect
FileSync
IntegrationScalepoint
Legacy Integrations
Mailgetter
Pentacon integration
VINTERMAN integration
Sync
Sync integration
Sync Briox
SyncEconomic
Sync Exchange
Sync Proforma
Logs, jobs, data manipulation
Jobs and jobdemon
JobData
Log (old)
LogProfile
Import filter
Export filter
Update filter
Ratelimit
Recfilter
Report
Mails, messages, notes
Custmail
MailQueueEntry
SMS
Stodo
SupportTicket
Thread
UserCommunication
Configuration
Functionality (mixed)
Policy
Security
SecurityG
SecurityRestrictions
Map/Gps
Gps
Map
MapLayer
RouteFinder
RouteTSP / RouteMTSP
RouteViewer (javascript)
Other classes
Account
CustomerSubscription
CustomField
CustomFieldUI
DriveLog
DocumentMaster
EDI - general
FilterRegexp
InspectInstance
Intl
InventoryTodoItem
InvoiceCostgroup
InvoiceFee
InvoicePricing
Kiosk
Mdate, Mtime and MdateTime
Parser
Privacy
PrivacyConsent
Procedure
QuestionAction
QuestionForm
Registration
Route
Salary
SalaryRule
SalesProduct
SalesProductFavorite
Stock
Table
TodoAccordPayout
TodoTemplate
TodoSLA
TodoState
TodoWorkpoolGenerator
ToolServiceAgreement
ToolProtocol
Translation
Tutorial
UserCheckinGuard
Version
Workarea
Workplan
Xnet
