System Name Glossary
DonorPoint uses plain-English labels in the admin interface, but underlying system names (used in scripts, expressions, API calls, and event handler names) sometimes differ. This table maps display labels to system names.
Record Type Names
| What You See in the Admin | System Name | Used In |
|---|---|---|
| Form / Page / Campaign | campaign |
Scripts, API, event handlers |
| Transaction | purchaseOrder |
Scripts, API, event handlers |
| Line Item | orderItem |
Scripts, API |
| Item (template) | orderableItem |
Scripts, API |
| Recurring Donation | recurringDonationInstance |
Scripts, API, event handlers |
| Volunteer Record | volunteerInstance |
Scripts, API, event handlers |
| Segment / List | contactGroup |
Scripts, API |
| Employee Record | (employee relationship) | employeeRelationship in scripts |
| Workplace Campaign Year | givingCampaign |
Scripts, API |
| Community Campaign | teamCampaign |
Scripts, API |
| Catalog | commerceCampaign |
Scripts, API |
| Mass Email Job | emailSolicitation |
Scripts |
| Email Template | emailDefinition |
Scripts |
| Custom Field Definition | customProperty |
Scripts |
Transaction Type Values
When filtering transactions by type in scripts or reports, use these values:
| Display | System Value |
|---|---|
| Received (payment collected) | RECEIVED |
| Pledge | PLEDGE |
| Payment (against pledge) | PAYMENT |
| Invoice | INVOICE |
| Refund | REFUND |
| Void | VOID |
| Declined | DECLINED |
| Authorization | AUTHORIZATION |
| Chargeback | CHARGEBACK |
| Memo | MEMO |
| Deposit | DEPOSIT |
| Payout | PAYOUT |
Transaction Status Values
| Display | System Value |
|---|---|
| Active | ACTIVE |
| Test | TEST |
| Deleted | DELETED |
Why These Names Exist
DonorPoint’s class names reflect its origins. “PurchaseOrder” was the original name for transactions in a commerce-oriented system. “Campaign” was the original name for forms. “GiftWrap” was an early product name (hence the com.bigriver.giftwrap package). The resource bundle system displays business-appropriate labels everywhere in the admin interface, but the underlying names remain in the data model, API, and scripting layer.