Database glossary

a
  • Addon - Tools in the Boost.space system that extend primary modules with additional functionality, allowing customization of workflows to fit your company's needs. They offer features such as creating forms, managing projects, and facilitating communication. Each addon integrates with others, enhancing the overall functionality of your workspace.
  • Admin - A user role in Boost.space with comprehensive system access, including the ability to add, remove, and manage all system levels. Admins can oversee all users, configure system settings, create custom fields, and manage modules and addons. Admin can also access Integrator and manage automations.
  • API token prioritization - In Boost.space, this feature allows you to set priorities for API tokens, determining which data sources can overwrite others during data consolidation. This ensures accurate and efficient updates by merging data from multiple sources based on assigned token priorities.
b
  • Boost.space system - A platform that centralizes and synchronizes company data from internal and external sources, offering a suite of modules and addons for project management, CRM, data visualization, and more. Has many features to optimize your workflow!
  • Business cases addon - One of the addons of the Boost.space system. With this addon, you can easily analyze and evaluate potential business scenarios.
  • Business offers addon - One of the addons of the Boost.space system. With this addon, you can easily create and customize business offers.
  • Business orders module - One of the modules of the Boost.space system. In this module, you can easily manage your business orders.
c
  • Calendar addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business calendar and schedule.
  • Charts addon - One of the addons of the Boost.space system. With this addon, you can easily visualize and analyze your business data through charts and graphs.
  • Contacts module - One of the modules of the Boost.space system. In this module, you can easily manage your business contacts.
  • Contracts addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business contracts.
  • Custom branding - Boost.space allows administrators to personalize the system's appearance to align with their company's brand identity. This includes customizing logos, login screen backgrounds, favicons, and system colors.
  • Custom field - A feature in Boost.space that allows administrators to define and manage additional data fields within each module, tailoring the system to specific organizational needs.
  • Custom fields with functions - Just like in regular tables, in Boost.space you can apply dynamic calculations to data stored in numeric fields and correlate them using mathematical functions. You can easily include the results of additions, subtractions, divisions, etc. in user-defined custom fields with functions.
  • Custom triggers and actions - In Boost.space, this feature enables you to automate workflows by defining specific conditions (triggers) that initiate automated responses (actions). For example, you can set up a trigger to detect when a record's status changes and configure an action to send a notification or execute a webhook in response.
d
  • Dashboard addon - One of the addons of the Boost.space system. With this addon, you can easily view and analyze your business data in one place.
  • Data consolidation - A Boost.space feature that merges data from multiple sources, allowing integration of diverse datasets into a unified view. Using API token prioritization, it determines which data sources overwrite others, ensuring accuracy and consistency across your system.
e
  • Error - Service is unavailable due to a failure, a service responds with unexpected data or the validation of input data fails.
f
  • Forms addon - One of the addons of the Boost.space system. With this addon, you can easily create and collect data through customized forms.
i
  • Invoices module - One of the modules of the Boost.space system. In this module, you can easily manage your business invoices.
  • Item - Items are rows in records (order/request/invoice/purchase...)
k
  • Key column - In Boost.space, the Key Column is a designated field that uniquely identifies records within a space. It is essential for data consolidation, as it determines how data from various sources is merged into a single record. For instance, selecting 'email' as the Key Column ensures that any incoming data with the same email address updates the existing record rather than creating a duplicate.
l
  • Label - In Boost.space, a label is a tag that can be added to items within a module. It's a flexible tool used to categorize and organize data, making it easier to customize workflows and processes.
  • License - Licenses to enable access to certain features.
m
  • Manager - In Boost.space, a Manager is a role within a space that allows an individual to manage members and other managers, view and manage records, and modify space settings, such as status lists and labels.
  • Member - In Boost.space, a Member is a role within a space that permits an individual to view and manage records using existing statuses and labels. Members cannot manage other members or modify space settings.
  • Menu editor - In Boost.space, the Menu Editor is a feature that allows administrators to customize the system's navigation interface. It enables the creation and management of menus by adding modules, folders, shortcuts, and embedded content. Administrators can tailor menus for individual users, controlling their access to specific modules and enhancing overall user navigation.
  • Mobile and desktop app - Boost.space has an Android, Windows, Mac, iOS or Linux apps with push notifications. Have data at your fingertips at any time (as long as your phone battery is charged).
  • Module - a module is an application or tool designed to handle specific business functions, such as CRM, project management, or inventory. The system's modular architecture allows you to activate only the modules you need, enabling customization and scalability as your business requirements evolve.
  • Multicurrency database - All modules that work with currencies have the ability to add currency exchange rates and automatically recalculate prices.
  • Multilingual database - Save your data in multiple languages. Important for multi-language product databases etc.
n
  • Notes addon - One of the addons of the Boost.space system. With this addon, you can easily create and organize business notes.
o
  • Owner - In Boost.space, an Owner is a role within a space that grants comprehensive control over that space. Owners can manage members, managers, and other owners, view and manage records, edit space settings—including status lists and labels—and have the authority to delete the entire space.
p
  • Payments addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business payments and financial transactions.
  • Pre-made custom fields - We pre-made hundreds of custom fields and mapped them in our integrations. Thanks to this feature, you can synchronize hundreds of custom fields with a few clicks.
  • Products module - One of the modules of the Boost.space system. In this module, you can easily manage your business products.
  • Projects addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business projects.
  • Purchases addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business purchases.
r
  • Record - In Boost.space, a record is a single data entry within a module, like a row in a database. For example, a contact in the Contacts module or a task in the Tasks module.
s
  • Sandbox environment - Create a copy of your system instance and use it as a Sandbox test environment. Test features and work with your data risk-free. You can re-generate the Sandbox environment at any time so that it will match your main system instance.
  • Space - In Boost.space, a space is a subunit within a module that helps organize and categorize data, ensuring clarity even with large volumes. For example, within the Contacts module, you might have spaces like "Client Database" or "Supplier Database." Access to each space is restricted to users who have created it or have been granted access.
  • Statuses - In Boost.space, statuses are indicators assigned to records within modules to represent their current state or progress. They can be system-defined, such as "Active" or "Done," or custom-created to fit specific workflows. Statuses help track and manage tasks, projects, and processes efficiently.
  • System instance - In Boost.space, a system instance is a distinct environment tailored for a specific team or organization. It encompasses all users, modules, spaces, records, data, and configurations unique to that entity, ensuring independent operation and customization.
  • system roles - There are two roles of the Boost.space system: a) Admin that can access system settings and has all permissions + can manage automations b) User that can perform actions based on the permissions that were given to him by admin.
  • System settings - Main settings of the Boost.space system that is accessible only by admins. You can change a variety of things here (custom fields, actions and triggers, design, etc.)
t
  • Tasks module - One of the modules of the Boost.space system. In this module, you can easily manage your business tasks.
u
  • User - Can use the system on a limited basis based on the rights assigned by the admin.
w
  • Wall addon - One of the addons of the Boost.space system. With this addon, you can easily communicate and collaborate with your team.
  • Warehouses addon - One of the addons of the Boost.space system. With this addon, you can easily manage your business warehouses and inventory.
  • Work hours addon - One of the addons of the Boost.space system. With this addon, you can easily track and manage your work hours.

Integrator glossary

abcdefghijklmnopqrstuvwxyz
a
  • Action module - You can create, read, update, or delete data with an action module. Action modules are the most common type of module and can be at the beginning, middle, or end of a scenario. There is no limit to the number of action modules in your scenario.
  • Aggregator - An aggregator is a type of module that allows you to merge multiple bundles into one single bundle. Aggregators are useful in making data readable for certain modules or generating meaningful output. Boost.space Integrator offers:
    • Array aggregator
    • Numerical aggregator
    • Table aggregator
    • Text aggregator
  • API token - A secure code used to authenticate and authorize access to API endpoints, enabling users to connect with third-party applications.
  • Array - Within a bundle, data items of the same type are sometimes in an array. You can find an array by looking at the details of a bundle. Depending on the details of your scenario, you can map other modules to a specific item in an array or use iterators and aggregators to manipulate your data into other formats. When mapping, Boost.space Integrator marks arrays with.
  • Array aggregator - When designing a scenario, use an array aggregator to merge multiple bundles into one single bundle. This may be necessary to format data properly for subsequent modules. The array aggregator also lets you define your target data structure.
  • Auto commit - The Auto commit option defines how Boost.space Integrator processes data transactions. Enabling Auto commit switches all operations to the commit phase. In the case of an error, data commits immediately and you cannot restore any lost data.
b
  • Blueprint - Boost.space Integrator lets you import and export scenarios via a blueprint, a file in JSON format. Your blueprint contains all of your modules and settings except for connections. When importing from a blueprint, you must add your connections.
  • Break error handling directive - Using a break directive lets you resolve errors manually and helps when you want more human oversight of errors. When an error occurs, the break directive stops the execution of subsequent modules and stores the error in the queue of incomplete executions. Then, the break directive creates a separate record for each bundle that causes the error (available under the Incomplete executions tab > Details). Here, you can manually resolve the error and process all unprocessed bundles. The scenario execution history shows the status as a Warning.
  • Bundle - A bundle is a chunk of data and the basic unit for use with modules. A bundle consists of items, similar to how a bag may contain separate, individual items.  
c
  • Clone module - When you need a quick duplicate of a module (for example when using data store modules on each branch of a router), use the clone module command to make an exact duplicate of your module. It appears instantly and has the same settings and variables as the original module. You can then drag it to wherever you need it and customize the settings. Changes in the original do not affect the clone and vice versa.
  • Clone scenario - You can duplicate a scenario from the Scenario tab by using the Clone option on the drop-down menu for the scenario. Possible uses include sales with multiple pipelines. Use the Clone scenario to create a duplicate scenario and customize it for each pipeline. Changes in the original do not affect the clone and vice versa.
  • Commit error handling directive - Stops scenario execution if an error occurs but retains any successfully processed data. Use this when you want to capture completed actions even if subsequent modules fail.
  • Commit phase - Commit is the third phase of scenario execution. If the operation phase is successful for all modules, the commit phase begins and makes all data changes permanent. This means that Boost.space Integrator sends information to all the services involved in the operation phase about its success.
  • Connection - Unique, active service acces point to a network. There are different types of connections (API key, Oauth…).
  • Converger - A converger is the counterpart to the router module and merges several routes into one route. There is no converger module available in Boost.space Integrator, but there is a workaround, that allows you to reduce the duplication of modules in different routes.
  • Copy module - When working with multiple scenarios, use the copy module command to create a duplicate of your module that you can paste to any scenario. It functions similarly to cutting and pasting text on your computer. Although cloning a module is faster, copying allows you to paste the module in another scenario. Copying a module will also copy any filters before the original module. You can also box select (shift + drag) several modules and copy them with the ctrl + C shortcut. This is helpful when creating complex scenarios.  
  • Custom apps - Create your own custom apps to be used in the integrator engine and share them with users in your organization.
  • Custom functions - Create and execute custom JavaScript functions in your scenarios.
  • Custom variables - Edit and manage your data across multiple scenarios at once.
  • Cycle - A cycle is the operation and commit/rollback phases of scenario execution. A scenario may have one or more cycles (one is the default).
d
  • Data loss - The data loss option enables data to be lost if Boost.space Integrator fails to save a bundle to the queue of incomplete executions (e.g. due to a lack of free space). Enable data loss to prevent interruptions in the overall scenario execution, e.g. a scenario where it is imperative the scenario keeps running and the incoming erroneous data is not that important.
  • Data store - A data store is a built-in database in Boost.space Integrator. You can use data stores to store data from scenarios or transfer data between individual scenarios or scenario runs. Your account includes data stores, so you do not have to register at a third-party service.
  • Data structure - When you create a data store, you need to create a data structure that formats your data store in Boost.space Integrator. Think of the data store as a spreadsheet and the data structure as the headers. The data structure defines the kind of data (i.e. text, numeric, etc.) that the data store records. You can view and manage your data structures from the data structures page. You can reuse your data structures.
  • Data transfer - Data transfer is the amount of data transferred through your scenario.
  • Diagram - The diagram is a visual representation of your scenario and appears exactly the same way as you see your scenario in the Scenario editor. Use the diagram tab to quickly view:
    • the execution history of your scenario.
    • the number of operations and data consumed.
    • the controls to manage the scenario.
  • Directive (error handling) - A directive allows you to control how Boost.space Integrator handles errors. There are six error-handling directives:
    • Rollback
    • Commit
    • Resume
    • Ignore
    • Break
    • Retry
f
  • Finalization phase - Finalization is the fourth and final phase of scenario execution. The finalization phase closes open connections (e.g. FTP connections, database connections, etc.) and marks the scenario as completed.
  • Full-text execution log search - Search and quickly identify any item in your scenario execution history for faster and more effective troubleshooting.
  • Functions - Functions you can use in Boost.space Integrator - create, update, delete, get, search.
i
  • Ignore error handling directive - Use the ignore error handling directive when you want a scenario to continue processing the next bundles if an error occurs. The ignore directive does not process the bundle where the error occurred through subsequent modules. The scenario execution status is marked as Success. The ignore directive is the default when you use a module instead of an error-handling directive.
  • Incomplete execution - Sometimes Boost.space Integrator cannot successfully finalize a scenario execution due to an error. Boost.space Integrator stores incomplete executions in a folder named Incomplete Executions. Each stored incomplete execution can be resolved either manually or automatically.
  • Initialization phase - Initialization is the first phase of scenario execution. During the initialization phase, Boost.space Integrator creates all necessary connections (for example, to databases, email services, etc.). The initialization phase also checks if each module is capable of performing its intended operation(s).
  • Integrator - Part of the Boost.space system, where you can create your connections and automate your processes.
  • Integrator item - An item is data that is part of a bundle. There are several different types of items: text, number, boolean (yes/no), date, time, buffer (binary data), collections, and arrays. You can find these details by clicking on the inspector at the upper-right of your module.
  • Iterator - When creating a scenario, use an iterator to divide one bundle into smaller separate bundles. Subsequent modules then process the bundles separately. One common use is when automatically uploading email attachments to a cloud drive. You can find iterators under the Flow control of the tools section.
k
  • Key (data store) - When creating a new data store, you can assign unique identifiers to each record. Boost.space Integrator will create a key for you if you leave the key field blank. You can also map the value of your key to make it easier to find information in your data store.
  • Keychain - The keychain helps you to administer the keys you have stored in Boost.space Integrator. Each key is a unique identifier used for encryption.
m
  • Mapping - Mapping links the modules in your scenario. When you map an item, you connected the data retrieved by one module to another module to perform the desired action. For example, you can map the email address and subject lines from the Email > Watch emails module to Google Sheets > Add a row and create a spreadsheet of email addresses and subjects.
n
  • No-code workflow builder - Design, build, and automate with a visual drag-and-drop interface.
  • Numerical aggregator - A numerical aggregator lets you apply functions like SUM or AVG to numerical values. The numerical aggregator then returns the results in one bundle.
o
  • Operation - Operations are tasks in integration scenarios, similar to "operations" in Make.com. Each action, like reading or updating a record, counts as one operation. They’re essential for data syncing between apps and reset monthly. Going over the limit pauses syncing until you add more or upgrade your plan.
p
r
  • Real-time execution monitoring - Visually monitor, isolate, and troubleshoot workflow executions immediately in real-time.
  • Repeater - A module that repeats tasks multiple times, often used for making repeated API calls, like uploading multiple items or processing lists.
  • Resume error handling - Use the Resume directive when you want scenario execution to continue even though an error occurs. The Resume directive allows subsequent modules continuing processing as if no error took place. The Scenario execution history displays the status as Success.
  • Rollback error handling - Use the Rollback directive when you want to mark the error and return modules to how they were before the scenario ran. The Rollback Directive stops the scenario execution immediately. Then a rollback phase starts on all modules to revert each module back to its initial state. The Rollback directive marks the scenario execution status as Error.
  • Rollback phase - Rollback is a phase that occurs when there is an error during the operation or commit phase on any module. The scenario execution stops the operation or commit phase and starts the rollback phase, reversing all changes in data.
  • Router - A router allows you to add new routes to a scenario so you can branch your flow into several routes and process the data within each route differently.
s
  • Scenario - A specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive.
  • Scenario execution history - Boost.space Integrator maintains a history of your scenario and records:
    • The date that scenario execution started
    • Status (success, warning, or error)
    • Execution duration
    • Number of operations spent during the scenario run
    • Size of transferred data
    • Link to detailed information, where you can inspect all data in that particular execution received and how the data was processed
    You can view this information by clicking on history in Scenario detail or in the Diagram. Viewing from the diagram allows you to see currently running executions and stop them if necessary.
  • Scheduling - Boost.space Integrator allows you to define when and how often an active scenario runs. Use the Schedule setting panel under the Options tab and choose Scheduling to set your preferred schedule.
  • Sequential processing - Using the Sequential processing options allows you to monitor and resolve errors in greater detail. If you enable sequential processing, Boost.space Integrator stops processing the task sequence until you resolve all incomplete executions. With sequential processing enabled, you can address all incomplete executions in the order in which they occurred. If you disable Sequential processing, the scenario continues to run according to its schedule with repeated attempts to rerun the incomplete executions.
  • System key - A unique identifier for your Boost.space system, ensuring secure and accurate connections across integrations.
  • System variables - Get detailed information about your scenarios, current executions, teams, and organizations.
t
  • Table aggregator - You can use a table aggregator to create a table from multiple bundles. The table aggregator merges values based on your specified column and row parameters and outputs into a single bundle. One possible use is compiling blog posts or emails into a single email summary.
  • Trigger - The initial event that starts a scenario. It can be an action, a scheduled time, or a custom event, and is essential to define at the beginning of each scenario.
w
  • Webhook - A webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers.

Marketplace glossary

abcdefghijklmnopqrstuvwxyz
a
  • AI Credits - These credits allow users to access advanced AI functionalities within the Boost.space system.
  • AI Field - AI field is enhanced with artificial intelligence, providing smarter insights and automated functionalities to optimize data processing and decision-making.
  • Appflow - Complex pre-made workflow that combines one or many automation scenarios and optionaly database structure.
m
  • Marketplace - Marketplace is a space where users can purchase Appflows, explore our partners, and learn how to become a partner themselves.

Billing and Policy glossary

abcdefghijklmnopqrstuvwxyz
a
  • AI Credits - These credits allow users to access advanced AI functionalities within the Boost.space system.
  • Appflow - Complex pre-made workflow that combines one or many automation scenarios and optionaly database structure.
m
  • Marketplace - Marketplace is a space where users can purchase Appflows, explore our partners, and learn how to become a partner themselves.