Progress Rollbase Data Model

The Progress Rollbase object-oriented data layer provides complete visual control at the metadata-level without requiring any programming expertise. Use point & click wizards to create objects (i.e. tables) and relationships between them. Add fields, create components and configure advanced data behavior. Design and customize enterprise-level data models all from within the comfort of your browser.

Objects

Object definitions are the basic building block of all Progress Rollbase applications. You can define Objects to represent any kind of business data such as a Customer, Employee, Product, Quote, Invoice, Purchase Order, Partner, Project, Meeting, Candidate, Requisition, etc. Objects consist of many subcomponents which, when combined together, form an enterprise-level business entity that can be used in one or more applications.

Fields

Fields are the basic building block of object definitions that determine what kind of data is stored with each object record. Fields are used in pages, views, charts and other object components to display and input object data. Progress Rollbase allows the creation of over 25 different field data types. For each field you can define sophisticated validation rules, permissions, auditing behavior, and much more.

Relationships

Relationships represent connections between objects and are a fundamental component of any sophisticated business application. Each relationship's behavior is controlled by cardinality (e.g. 1-1, 1-Many, Many-Many) as well as other properties and attributes. Progress Rollbase allows you to create any number of relationships between any objects, including hierarchy relationships.

Conversion Maps

Conversion Maps are used to define how object records can be converted from one object type into another enabling easy integration between and among Progress Rollbase applications. Conversion maps can be saved and reused in workflow events or manually invoked by users.

Unique Indexes

Progress Rollbase includes robust duplicate prevention capabilities in the form of field uniqueness enforcement and validation. When this control at the individual field level is not enough, unique indexes can be used to define duplicate prevention rules by defining groups of fields which should never contain the same selections for any given record.

Email Templates

Email Templates are designed for generating personalized messages to individuals or multiple recipients in HTML or plain text formats that can incorporate record and related record field data. Email Templates are often used in conjunction with workflow events to send alerts and notifications.

Document Templates

Document Templates are designed for generating personalized documents (Word, Excel, HTML or plain text) that can incorporate record and related record field data. Document Templates are often used in conjunction with Workflow Events to automatically generate and send documents.