SoftEXIT Studio Glossary

SoftEXIT Studio’s AI-assisted application design capability. The AI Architect helps configure the Studio platform from natural-language requirements rather than generating a separate application codebase.

A Studio capability for packaging, distributing and installing reusable applications and application components. It allows organizations to add prebuilt functionality without starting every solution from scratch.

Software that provides reusable capabilities for building and running business applications. Studio supplies configurable data, forms, grids, dashboards, reports, security and other components on a common platform.

A field type that automatically assigns a formatted sequential identifier to a record, such as CASE-0000001.

The use of a device camera or scanner to capture barcode values. Studio can use scanning with supported fields and lookups to speed data entry and record identification.

A visual component used to present application data graphically. Studio supports multiple series and can use application data to create dashboard visualizations.

A record related beneath another record in a parent-child relationship. For example, Calls can be child records of a Client, allowing multiple calls to remain connected to one client.

A reusable Studio building block used to present, enter or analyze information, such as a Grid, Form, Chart, Gauge or Report.

A configurable interface for creating, viewing and editing records. Studio forms can include validation, sections, multiple columns, conditional behavior and specialized field controls.

A tabular component for browsing and working with records. Studio grids support paging, sorting, filtering, grouping and aggregates.

The process of receiving information from users or external systems and storing it as application data. Studio supports forms and external input interfaces for controlled data intake.

Field types for storing dates or dates with time values. Studio supports date filtering, including relative date filters for reporting and data views.

A defined piece of information stored on a record, such as Company Name, Status, Amount or Created Date. Field definitions determine the type of data and how Studio presents and validates it.

Controls that protect sensitive fields from unauthorized viewing or editing. Studio can mask protected fields and restrict access based on permissions.

Rules that determine whether entered information is acceptable before a record is saved. Validation helps improve data quality and enforce application requirements.

A dashboard visualization for displaying a measure or KPI. Studio supports radial and linear gauge presentations.

A field for storing location information that can be presented with an external map link.

Data organized through related parent and child records. Studio supports nested relationships so applications can represent structures such as Companies → Contacts → Activities.

A text field designed for values that need efficient searching or lookup behavior.

A field that references a record in another table. Lookups allow related information to be connected without duplicating the referenced record.

SoftEXIT’s approach to lightweight application workflow behavior using configurable rules such as conditional requirements and visibility rather than requiring a large workflow process for every business rule.

A data-view option that limits records to those associated with the current user, allowing applications to present personalized working sets.

A platform that enables business applications to be created primarily through configuration rather than traditional application programming. SoftEXIT Studio provides reusable components and data structures for this purpose.

The record above one or more related child records. A parent can provide context and a relationship for multiple subordinate records.

A one-to-many relationship in which one parent record can be associated with multiple child records. This is a core way Studio models connected business information.

A numeric field intended for percentage values. Studio can format and aggregate percentage data in supported components.

A stable identifier used by Studio to identify certain objects or records independently of display names or other changeable values.

A field that limits users to predefined choices. Studio supports single- and multi-select picklists and can present selected values as chips or formatted report text.

A field marked for additional security. Protected values can be masked and access can be controlled through the appropriate permission.

The use of a camera to capture QR-encoded information for supported Studio data-entry and lookup scenarios.

A single stored instance of a table’s data. For example, one company, contact, contract or inventory item can be represented by a record.

A data model that organizes information into related tables. Studio uses relationships between tables so connected information can be maintained without placing everything into one flat structure.

Studio’s configurable reporting capability for selecting data, applying filters and producing formatted output, including PDF export.

A security approach in which capabilities are granted according to assigned roles and permissions. Studio uses roles, permissions and access groups to control application access.

A Studio application workspace that organizes menus, views, tables and other components into a usable business application.

A column-based view for organizing records by status. Studio Status Boards can support record creation within columns, configurable dragging behavior and read-only operation.

A defined collection of records with a common field structure. Tables represent business entities such as Companies, Contacts, Risks, Contracts or Inventory Items.

A configured presentation of application information. Views can contain components and can be organized into groups and menus for users.

A collection used to organize related Studio views and control how they are presented within an application.