System glossary
a
- Addon - Tools in Boost.space system. With them you can customize your workflow to fit your company's needs. They offer a range of features from creating forms and managing projects, to chat functionality and more. Each addon integrates with others, enhancing the overall functionality of your workspace.
- Admin - Admins in Boost.space have exclusive access to system settings. They manage the overall system setup, including appearance, language, currency, user settings, and the availability of individual modules to users and teams.
- API token prioritization - Prioritize what integration sources can overwrite each others' data.
b
- Boost.space system - Centralization and synchronization platform, where you can organize and manage your data.
- 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 - Make the system your own, with company colors, logo, custom login screens, and much more.
- Custom field - A feature in Boost.space that allows you to define and manage data within each module according to your specific 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 - Define your own conditions for triggering an automated action. The trigger is followed by one or more actions. Using this feature you can prepare user-defined notifications, send emails or use webhooks to start complex automations.
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 - Act of merging data from more than one source.
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 - Is a thing that determines which column is unique and also by what data is merged (email, order number...)
l
m
- Manager - Can manage members and space managers, view and manage items. Can modify space settings.
- Member - Can view and manage items while using existing statuses and labels.
- Menu editor - Add your corporate cloud applications to the Boost.space home page and turn Boost.space into a comprehensive corporate platform. You can also create a different menu for each user and decide what modules he has access to.
- 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 - The module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts)
- 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 - Can manage members, managers and owners of a specific space. Can view and manage items. Can edit settings of a given 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.
- Plan - Combination of a license (enabled features) and tier (numeric limits) and a subscription period (monthly / yearly).
- 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 - One row in the Boost.space database. These are individual rows under spaces in each module. For example single products, but not their variants.
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 - Subunits are created within modules to maintain organization and clarity, even with large amounts of data.
- Statuses - Create statuses for each module separately to create an ideal environment for efficient and consistent work.
- System instance - One specific Boost.space system. For example, one person can have 3 instances of the Boost.space system.
- system roles - There are two roles of the Boost.space system: a) Admin that can access system settings and has all permissions 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.
- Tier - Tiers set numeric limits on.
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
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 - The API token is a multi-digit code that allows a user to authenticate with cloud 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 - Use the commit error handling directive when you want to stop the execution of the scenario completely but still have the sent data. When there is an error, the commit directive:
- stops execution immediately
- does not process the subsequent modules
- ignores all unprocessed bundles
- 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 - An operation is a task performed by module.
p
- Parallel scenario execution - Process multiple incoming items instantly, at the same time, instead of one after the other.
r
- Real-time execution monitoring - Visually monitor, isolate, and troubleshoot workflow executions immediately in real-time.
- Repeater - When you need a module to perform a task multiple times, for example, make an API call, use a repeater. Placing a repeater module before another module makes the subsequent module repeat its task. You can confirm by inspecting the bundle's output by the subsequent module.
- 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
- 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 - The system key is the name of your Boost.space system.
- 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 - Every scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the clock/lightning icon to another module.
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.