Table of Contents
Overview
The Custom Objects in Ordway is part of Ordway’s broader extensibility and configurability strategy. It allows you to extend the platform beyond standard data models to support unique business processes, additional data requirements, and advanced auditability needs.
Custom Objects enable you to model and manage data that does not naturally fit into Ordway’s standard object structure.
Why Custom Objects are Needed
Ordway provides a rich set of standard objects such as Products, Plans, Customer Accounts, Subscriptions, and so on. Each standard object has a predefined lifecycle and supports actions. However, during real-world implementations, customers often require:
Additional master data not supported by standard objects
Transactional data outside the subscription lifecycle
Business-specific entities and workflows
Enhanced audit and reporting requirements
Custom Objects address these gaps by allowing customers to define and manage their own data structures.
What are Custom Objects
A Custom Object is a user-defined data entity that allows you to store additional business-specific information.
Each Custom Object:
Has a name and description
Contains custom fields
Supports record creation, updates, and deletion
Can be automated using workflows
Is accessible through APIs
Custom Object Structure
Each Custom Object consists of:
Object Name – Identifies the object
Fields – Define the data captured
Records – Individual entries created for the object
Relationships – Links to other objects (if applicable)
Custom Objects vs Standard Objects
| Standard Objects | Custom Objects |
| Predefined by Ordway | Defined by customers |
| Fixed schema and lifecycle | Fully configurable |
| System-driven actions | Customer-defined usage |
| Limited extensibility | Designed for extensibility |
Custom Objects add extra data when needed and do not replace standard objects.
Enablement & Availability
Custom Objects are a paid add-on feature
Enablement requires an entitlement and approval process
Customers must contact Ordway Support to request access
Once enabled, Custom Objects become available for configuration and use within the application.
Key Use Cases
Custom Objects can be used to:
Track business-specific records (for example, internal approvals, audits, or custom processes)
Store integration-related data
Support customer-specific workflows
Extend reporting and analytics capabilities
Enable API-based integrations to show selected or generated data to customers in the Customer Portal.
Note: Custom Objects framework enablement is managed by Ordway. Customers must contact Support if this feature has been purchased.
Custom Object Capabilities
The Custom Object Framework supports the following capabilities:
Object Definition
Create new custom objects
Define object metadata such as name, menu group, and numbering behavior
Add, update, or delete custom fields
Control visibility in reports
Record Management
Create, view, edit, and delete custom object records
Validate records based on field definitions
View records in list and detail views
Workflows
Use custom objects in workflows
Search or look up custom object records
Retrieve field values
Update custom object records through workflow actions
Templates
-
Reference custom object fields in:
Email templates
PDF templates
Use custom object data in the context of related standard objects
Reporting
Enable custom objects for reporting
Use custom object fields as report dimensions and filters (based on access permissions)
Custom Objects Management Workflow
Once the feature is enabled, a Custom Objects menu becomes available. This serves as the central hub for managing all custom objects.
View Custom Objects
To access Custom Objects
When you enabled Custom objects feature, the In the Custom object feature is show up under Setup.
Click Custom Objects. The Custom Objects page is displayed with lists of all existing Custom Objects and provides options to create or manage them.
Comments
0 comments
Please sign in to leave a comment.