-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d56ad89
commit 5e66a3f
Showing
1 changed file
with
98 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,105 @@ | ||
| # Glossary of Terms | ||
|
|
||
| {% hint style="info" %} | ||
| This page is a work in progress! Check back for more terms as they're added.\ | ||
|
|
||
|
|
||
| {% hint style="info" %} | ||
| This page is an egg waiting to be hatched! | ||
| Our glossary is organized alphabetically, with each tab containing 2-3 letters. Click through the tabs to find your term that stars with the corresponding letter. | ||
| {% endhint %} | ||
|
|
||
| This section will soon provide concise definitions for API-specific, programming, and Rewst terminology, alongside key data concepts. Keep an eye on this space—we're excited to bring you a comprehensive guide that will support your understanding and use of our platform. | ||
| {% tabs %} | ||
| {% tab title="ABC" %} | ||
|
|
||
|
|
||
| <table data-full-width="true"><thead><tr><th>Term</th><th>Definition</th></tr></thead><tbody><tr><td>Actions</td><td><strong>Actions</strong> are specific tasks that live inside a workflow in Rewst. Actions are grabbed from the menu, dragged onto the workflow UI, and executed as a task when the workflow runs.</td></tr><tr><td>API</td><td>Short for Application Programming Interface, an <strong>API</strong> is a set of protocols that allow actions on a platform in a programmatic manner. APIs power Rewst's integrations, enabling actions that workflows perform.</td></tr><tr><td>Automation</td><td><strong>Automation</strong> refers to the process of using technology, including Rewst's platform, to perform repetitive tasks without human intervention. It enables businesses to increase efficiency, accuracy, and consistency by automating various processes, from simple notifications to complex multi-step workflows.</td></tr><tr><td>Context Variables</td><td>Context Variables are variables accessed via the CTX prefix within a running workflow in Rewst, for dynamic processing.</td></tr><tr><td>Crate</td><td>A <strong>Crate</strong> is a pre-built automation. Crates within Rewst contain workflows, forms, triggers, templates, and scripts bundled together for easy deployment.</td></tr><tr><td>Crate Marketplace</td><td>The Rewst <strong>Crate Marketplace</strong> is the area of the Rewst platform where users can find and install Crates, offering a range of pre-built automation solutions.</td></tr></tbody></table> | ||
| {% endtab %} | ||
|
|
||
| {% tab title="DEF" %} | ||
| | Term | Definition | | ||
| | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Filter | Specific to Rewst's extension of Jinja, filters are python functions surfaced in the platform and used to modify variables or expressions within a workflow, providing additional control over data processing. | | ||
| | Form | A **form** is a way to collect data within Rewst. Forms can contain static and dynamic fields to retrieve information, which is then passed into the workflow upon submission. End-users can be given Form URLs to fill out necessary information prior to triggering a workflow's execution. | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="GHI" %} | ||
| | Term | Definition | | ||
| | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ||
| | HTTP Request Method | This specifies the action to be performed on a resource within an API, e.g., GET (retrieve data), POST (create data), PUT (update data), DELETE (remove data). | | ||
| | Integration | **Integrations** in Rewst allow the platform to connect and communicate with other software or services. Through integrations, Rewst can interact with various third-party applications, such as your PSA, RMM, email platforms, or cloud services, enabling you to extend the functionality of your automations and create more cohesive experiences. | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="JKL" %} | ||
| | Term | Definition | | ||
| | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Jinja | **Jinja** is a templating language used in Rewst for processing data within workflows. Based on Python, Jinja allows for more powerful manipulation of data, including filtering and custom formatting. | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="MNO" %} | ||
| | Term | Definition | | ||
| | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Organization | A group or entity within the Rewst platform that may have its own variables, forms, workflows, and users, **organizations** enable multi-tenanted management and customization of the platform according to specific client needs. | | ||
| | Organization Variables | Also known as **org variables**, these are specific variables used within an organization or sub-organization in Rewst. They can be referenced in workflows and may be inherited or overridden by sub-organizations. | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="PQR" %} | ||
|
|
||
|
|
||
| | Term | Definition | | ||
| | ---- | ---------- | | ||
| | | | | ||
| | | | | ||
| | | | | ||
| {% endtab %} | ||
|
|
||
| {% tab title="STU" %} | ||
| | Term | Definition | | ||
| | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Template | In Rewst, **templates** are used as a central store for repeated text, allowing for consistency across different actions and workflows. | | ||
| | Transitions | **Transitions** are elements found at the bottom of every action in Rewst that determine the path the workflow will take. Transitions can be based on success, failure, always, or custom-defined Jinja conditions. | | ||
| | Triggers | **Triggers** are components in Rewst used to initiate workflows or perform actions based on specific events or conditions. They can respond to various events, such as form submissions or webhook responses. | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="VWX" %} | ||
| | Term | Definition | | ||
| | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Workflow | In the context of Rewst, a **workflow** is a series of automated actions that are executed in a specific sequence based on triggers and conditions. Workflows enable users to design, execute, and manage multi-step processes, bringing together various integrations to accomplish a particular task. | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="YZ" %} | ||
| | Term | Definition | | ||
| | ---- | ---------- | | ||
| | | | | ||
| | | | | ||
| | | | | ||
|
|
||
|
|
||
| {% endtab %} | ||
|
|
||
| {% tab title="#" %} | ||
|
|
||
| {% endtab %} | ||
| {% endtabs %} | ||
|
|
||
| Stay tuned for updates. |