RAPTIX Glossary

A

Access Policy (Knowledge) A named rule that controls which roles can read a piece of knowledge-base content and what happens when access is denied — options include hiding the content entirely, returning a soft message, or showing a safely redacted version. Why it matters: Ensures only the right people receive sensitive information when they ask the AI assistant a question.

Action Button (Workflows) A labelled button shown to a task assignee on the approval screen (for example, "Approve", "Reject", "Return for Revision"). Each button name, color, and behavior is configured by the workflow designer and drives which path the process takes next. Why it matters: Gives team members domain-specific decision options rather than a generic yes/no, reducing confusion and mis-routing.

AI Agent Node (Workflows) A workflow step that runs an artificial-intelligence model to analyze data, generate content, or make a routing decision — using a prompt template, optional knowledge-base lookup, structured output, and confidence-based branching. Why it matters: Adds intelligent, automated judgment to a process step without requiring human review of every record.

ALL Merge (Workflows) A Merge Branches setting that holds a workflow in the merge node until every parallel branch has finished before continuing. Why it matters: Guarantees that no step is skipped — useful when downstream work depends on all parallel branches completing.

ANY Merge (Workflows) A Merge Branches setting that resumes the workflow as soon as the first parallel branch finishes, regardless of the others. Why it matters: Keeps the process moving at the speed of the fastest team without waiting for slower branches.

App (Applications) A self-contained internal tool available through Applications. An app can contain App Builder pages, runnable workflow forms, documents, and workflows, depending on the workspace and the user's access. Why it matters: Each app serves a specific business purpose — from timesheets to procurement forms — and can be updated without rebuilding from scratch.

App Builder The Enterprise-only builder used to create and edit data-driven application pages. It is opened from Applications when the user's plan and permissions allow it. Why it matters: Teams can maintain internal forms and dashboards while RAPTIX keeps access to the builder separate from access to run published pages.

Applications The RAPTIX area at /applications that brings together workspaces, applications, pages, runnable workflow forms, documents, and workflows. What appears depends on the user's plan and permissions. Why it matters: Users have one place to find and open the operational tools available to them.

Approval Table (Workflows) A per-row decision view used by configured workflow approval tasks. It records approve, reject, or hold decisions together with the approver's identity and timestamp. Why it matters: Process managers can bulk-review hundreds of line items and have a full audit record of every individual decision.

Approval Timeline (Workflows) A visual, chronological list of every step in a workflow instance — showing who acted, what decision they made, when they made it, and any comment they left. Why it matters: Gives everyone involved full transparency into a process without needing to ask for status updates.

Assistant (AI Agents) A configured AI personality set up by an administrator, with a name, icon, knowledge scope, system prompt, and access restrictions. Users choose an assistant from the AI Agents Hub and open a conversation with it. Why it matters: Different assistants serve different purposes — one may answer HR policy questions, another may navigate engineering documents — so users always go to the right source.

Audit Log (Documents / Applications / Knowledge) A tamper-evident, chronological record of every action performed — uploads, downloads, permission changes, policy assignments, page views — along with who performed the action, when, and from which location. Why it matters: Supports compliance reviews and incident investigations by providing a complete, accurate history of who did what.

Auto-Save (Workflows) A background process that automatically saves the current state of a workflow being designed, creating a timestamped version entry every 30 seconds when unsaved changes exist. Why it matters: Work is never lost to an accidental browser close or network drop — the latest state is always protected.

Auto-Sync (Knowledge) A configured rule that automatically detects when a new document is uploaded to Documents and immediately submits it to the knowledge-base pipeline for processing — without any manual action. Why it matters: The knowledge base stays current with no administrative effort — new documents are instantly available for AI-assisted search.

B

Batch Approval (Workflows) A task mode in which the assignee reviews an entire dataset — for example, a spreadsheet of purchase line items — and records a separate approve, reject, or hold decision for each row in a single screen session. Why it matters: Dramatically reduces the time needed to process large volumes of records that all require individual decisions.

Branch (Workflows) An independent path on a workflow canvas. Branches are created using Split, Conditional Branch, or If/Else nodes, and allow different logic to execute in parallel or based on conditions. Why it matters: Models real-world processes where different outcomes or departments need to act simultaneously or independently.

Breadcrumb (Documents / Applications) A clickable navigation trail showing the current location within a hierarchy — for example, Workspace > Project A > Invoice Folder. Clicking any level jumps directly there. Why it matters: Users always know where they are and can navigate up the hierarchy in a single click.

C

Cache A temporary store of recently calculated data that makes screens load faster. RAPTIX manages caching automatically — there are no administrator-facing cache settings to configure. Why it matters: Dashboards and statistics load instantly even with large data volumes, with no tuning required.

Citation (AI Agents) A numbered reference (for example, [1] or [2]) embedded in an AI assistant's answer, linking directly to the exact passage in the source document that supports that statement. Why it matters: Every factual claim can be verified against the original document in one click, building trust in AI-generated answers.

Classification (Knowledge) A security label assigned to an access policy — the available levels are Public, Internal, Confidential, Restricted, and Top Secret. The classification determines who can see the content and what masking rules apply. Why it matters: Organizations can align knowledge-base security with their standard data classification scheme.

Condition Node / If/Else Node (Workflows) A workflow node that evaluates one or more data conditions and routes the process to a "Yes" or "No" branch depending on the result — for example, routing automatically if an amount is below a threshold. Why it matters: Automates routing decisions that would otherwise require manual assessment, reducing delays and human error.

Conditional Branch Node (Workflows) A workflow node that evaluates multiple named conditions and takes the path of the first one that matches. Unlike an If/Else node, it supports more than two possible outcomes. Why it matters: Handles multi-outcome routing cleanly — for example, routing to Finance, Legal, or HR depending on the request type — without nesting multiple If/Else nodes.

Conversation Thread (Workflows / Documents) A chat-style, chronological record of all comments left by every participant across every level of a workflow or document task — similar in appearance to a messaging app. Why it matters: All discussion, questions, and clarifications about a request are in one place, so nothing is buried in email chains.

COUNT Merge (Workflows) A Merge Branches setting that resumes the workflow after a specified number of parallel branches have finished, without waiting for the rest. Why it matters: Useful when a process can proceed once a quorum of approvals or responses has been received, rather than waiting for unanimous completion.

D

Dark Mode A visual theme for RAPTIX that uses darker backgrounds and lighter text. It can be switched on or off using the toggle in the top bar, and the preference is remembered indefinitely. Why it matters: Reduces eye strain in low-light environments and is a personal preference that every user can set independently.

Dead-Letter Queue (DLQ) (Workflows — Email Trigger) A holding area for emails that the Email Trigger node received but could not process due to errors. When the number of consecutive failures reaches the configured threshold, the trigger automatically pauses to prevent further problems. Why it matters: Administrators can inspect failed emails and resolve issues without losing the incoming data or triggering runaway automation.

Deadline (Workflows) A due date configured on a task node, after which automated reminders and escalation actions take effect. Deadlines can be fixed dates, relative durations, or values read from workflow data. Why it matters: Nothing falls through the cracks — tasks escalate automatically when they are not acted on in time.

Digital Signature (Documents) An annotation tool that places an approval mark (stamp, handwritten ink, or typed text) on a PDF within the document viewer. The annotated version is saved as a new document version. Why it matters: Documents can be formally marked and approved within the platform without downloading, printing, or using a separate signing service.

Duplicate (Workflow / Template) A copy function that clones an existing workflow or communication template into a new, independently editable item. The clone contains all the original configuration but is saved under a new name. Why it matters: Reuses proven designs as starting points, saving significant setup time and reducing errors.

E

Email Trigger (Workflows) A workflow start node that monitors a designated mailbox and automatically launches a workflow when an incoming email matches configured filter rules — such as sender address, subject keyword, or attachment type. Why it matters: Turns an email inbox into an automation input — invoices, requests, or notifications arriving by email can start a structured approval process without any manual intervention.

Embedding (Knowledge) The process of converting a document chunk into a mathematical representation so the knowledge base can find it using meaning-based search rather than keyword matching. Why it matters: Users can ask questions in plain language ("What is the maintenance interval for Unit 5?") and receive precise answers even if the exact words differ in the document.

End Node (Workflows) A node that marks the terminal point of a workflow branch. When the process reaches an End node, that branch is considered complete. A workflow can have multiple End nodes for different outcomes. Why it matters: Clearly defines where each path in a process finishes, ensuring the engine correctly records completion.

Engine Dashboard (Workflows) The main monitoring screen for Workflows, showing all running and completed workflow instances with their status, creation details, and progress. Includes filters by status, creator, and workflow type. Why it matters: Gives managers and administrators a real-time view of all active processes so they can spot bottlenecks or stuck instances.

Entity (Documents) The highest-level organizational unit in the Documents document hierarchy, typically representing a project, department, or business object. Below an Entity are Instances, then Fields, then Files. Why it matters: Documents are always filed in context — attached to the right project record — rather than scattered in unstructured folders.

Escalation (Workflows) An automatic action taken when a task passes its deadline without a response — typically reassigning it to a different person, sending additional alerts, or advancing the workflow to a defined fallback path. Why it matters: Ensures that overdue tasks are never simply forgotten — the process continues even when the original assignee does not respond.

External Approver Portal (Workflows) A secure, no-login web page sent by email link to people outside the organization — such as vendors or contractors — who need to approve or reject a workflow task. The link is single-use and expires after action is taken. Why it matters: External partners can participate in an approval process without being given a platform account, maintaining security while removing friction.

F

Field (Documents) The third tier of the Documents document hierarchy, sitting below a workflow Instance. A Field typically represents a category of document within a process record — for example, "Signed Contract" or "Invoice". Why it matters: Separates different document types within the same process record, keeping the file structure predictable and organized.

File (Documents) The actual uploaded document — a PDF, Word file, spreadsheet, or image — stored at the bottom of the Documents hierarchy (Workspace → App → Page → Entity → Instance → Field → File). Why it matters: The physical document is always stored in context and can be found by navigating the hierarchy or searching by name.

Foreach Node (Workflows) A workflow node that repeats an enclosed set of steps for each item in a list — for example, sending a separate notification for each attachment in a submission. Why it matters: Processes lists automatically without manually duplicating nodes, keeping the workflow design clean.

Form Collector (App Builder, legacy integration) A compatibility integration that collects values from widgets on an App Builder page. New workflow forms are normally exposed from a Manual Start node and opened through Applications at /f/:token. Why it matters: Existing Enterprise App Builder pages can continue to submit structured data while new forms use the native workflow-form path.

G

Global Permission (Documents) An access grant that applies to all documents in Documents — either all existing files, all future files, or both — rather than to a single document or folder. Granted to a user or a role by an administrator. Why it matters: Onboards an entire team to all relevant documents in one action rather than setting permissions file by file.

H

Home Screen The first screen users see after signing in. It summarizes work that needs attention, workflows the user participates in, and recently opened items from Applications. Sections appear only when the user has the required access. Why it matters: Users can resume work and act on urgent items without first searching through modules.

I

If/Else Condition Node — see Condition Node

Instance (Documents / Workflows) In Documents, an Instance is the second tier of the document hierarchy — a specific occurrence of a process, such as a particular project or submission, sitting below an Entity and containing Fields and Files. In Workflows, an Instance (also called a workflow instance or run) is a single execution of a workflow — one specific case being processed through the defined steps. Why it matters: Keeps each process case separate and traceable, so documents and approvals from different cases are never mixed together.

J

JavaScript Object (JSObject) (App Builder, advanced) A reusable block of JavaScript attached to an App Builder page and callable from widget events such as button clicks or form submissions. Why it matters: Allows developers to write custom logic once and reuse it across the page, making apps easier to maintain and update.

K

Knowledge (Knowledge / AI Agents) The centrally managed repository of processed documents that AI assistants in AI Agents search when answering questions. Documents go through a multi-stage pipeline before they are "live" in the knowledge base. Why it matters: All AI answers are grounded in your organization's own documents rather than general internet content, making answers accurate and auditable.

L

Loop Node (Workflows) A special node that allows a backward connection between steps, creating a deliberate cycle — for example, returning a task to an earlier stage for correction before re-entering the approval chain. Why it matters: Models real-world revision cycles cleanly without creating accidental infinite loops in the design.

M

Manager Approval Screen (Workflows) The full-screen task page that an approver sees when they open an assigned task. It shows the submitted request data, an inline PDF viewer, dynamic action buttons, a comment box, file upload, and the conversation thread. Why it matters: Managers have everything needed to review and decide on a request in one screen — no switching between applications.

Merge Branches Node (Workflows) A workflow node that re-joins parallel branches that were previously split. The node can be configured to wait for ALL branches, ANY branch, or a COUNT of branches before the workflow continues. Why it matters: Controls exactly when a parallel process resynchronizes, giving workflow designers precise control over sequencing.

Merge Tag (Workflows / Communication) A placeholder in the format {{variable_name}} used in email subjects, bodies, or notification templates. At the moment the message is sent, each placeholder is automatically replaced with the actual value from the workflow data. Why it matters: Every automated message is personalized with real, current data — recipient names, amounts, dates, and any other workflow variable — without manual editing.

Microsoft SSO (Single Sign-On) A login method that lets users sign in to RAPTIX using their existing company Microsoft account, eliminating the need for a separate password. Administrators configure this in the sign-in settings. Why it matters: Users get instant access using credentials they already know, and IT retains full control over access through existing Microsoft tools including multi-factor authentication.

Multi-Level Approval (Workflows) A task configuration where a document or decision must pass through more than one approver in sequence — for example, team lead, then department head, then finance — before the workflow continues. Why it matters: Enforces organizational sign-off hierarchies automatically without needing manual tracking of who has reviewed what.

N

Node (Workflows) A single step on the workflow canvas — represented as a card with a type-specific icon and label. Nodes are connected by arrows (edges) that define the flow of the process. Types include Start, Task, Email, Condition, AI Agent, Pause, and End. Why it matters: Each node represents one atomic business action, making the overall process readable and maintainable as a visual diagram.

O

Applications The RAPTIX area for browsing workspaces, applications, pages, documents, and runnable workflow forms. App Builder is available for eligible applications and plans. Why it matters: It is the place to open the resources assigned to you and, where permitted, manage them.

AI Agents The AI assistant capability in RAPTIX. Users ask questions in natural language and receive cited answers drawn from the organization's own documents. Administrators configure named assistants for different teams or purposes. Why it matters: Employees get instant, accurate answers from company documents instead of searching through file systems or waiting for a colleague to respond.

Documents The document management capability in RAPTIX, organizing files in a structured hierarchy linked to process records. It includes versioning, audit logging, PDF annotation, permission management, and AI indexing. Why it matters: All documents live in context alongside the process they belong to, with full traceability of every action taken on every file.

Workflows The workflow and business process automation capability in RAPTIX. Users design processes on a visual canvas and the platform executes them — routing tasks, sending emails, making AI decisions, and tracking every action. Why it matters: Complex multi-step approval and automation processes run reliably without manual coordination, even when they span days, weeks, or months.

OneLogic Technology The company that operates RAPTIX. The product name shown in the application and throughout this guide is RAPTIX. Why it matters: Product instructions stay consistent while ownership and support information remain clear.

Knowledge The knowledge base and AI analytics capability in RAPTIX. Administrators upload or sync documents, run them through a multi-stage processing pipeline, configure access policies, and monitor AI usage through detailed analytics. Why it matters: Powers the AI answers in AI Agents with your organization's own content, ensuring accuracy and auditability.

P

Page (Applications / App Builder) A single screen inside an application. An Enterprise App Builder page can contain widgets, data queries, and business logic; a runnable workflow form is opened through its own /f/:token address. Why it matters: Each page serves a specific task — a form, a dashboard, an approval inbox — so users always land on exactly the right screen.

Pause / Delay Node (Workflows) A workflow node that suspends the process for a defined period before continuing — either a fixed duration (e.g., 3 days), a specific date and time, or a date value read from workflow data. Why it matters: Builds controlled waiting periods into automated processes — for example, holding an approval until after a contract start date — without any manual monitoring.

PDF Viewer (Documents / AI Agents) An in-browser panel that opens and displays PDF documents without downloading them. In Documents it supports annotation tools; in AI Agents it highlights the exact sentence cited in an AI answer. Why it matters: Users can review multi-page documents instantly in context, without installing a PDF reader or leaving the platform.

Pending Tasks (Workflows) The personal task inbox showing every workflow step that is currently assigned to the logged-in user and waiting for action. A badge on the top bar shows the count at all times. Why it matters: Users always know at a glance how much is waiting for them, without checking email or logging into separate systems.

Permission A named bundle of access rights that controls what a user can do across the platform: which Applications resources they can view or edit, which workflows they can see or trigger, which AI agents they can use, and which system capabilities they can access. Why it matters: One permission object covers all four areas — updating it once immediately affects every user who holds the associated role.

Pipeline (Knowledge) The five-stage processing sequence that converts a raw document into a searchable knowledge-base entry: Stage 1 parses text, Stage 2 chunks it, Stage 3 summarizes tables, Stage 4 enriches with AI-extracted entities, and Stage 5 embeds and indexes for search. Why it matters: Every document goes through a consistent, configurable quality process before it can be searched, ensuring accurate and complete AI answers.

Policy — see Access Policy

Preset (Knowledge) A saved, named collection of pipeline-stage settings that can be applied to any document with a single click. Presets ensure all documents of the same type are processed consistently. Why it matters: Configure the optimal settings once for each document type and apply them to hundreds of files without repeating the setup.

Processing Preset — see Preset

PWA (Progressive Web App) A feature that allows users to install RAPTIX as an app on their device — phone, tablet, or computer — and launch it from their home screen or taskbar like a native application. Why it matters: Users get instant one-tap access to the platform without opening a browser and typing an address.

R

RBAC (Role-Based Access Control) The RAPTIX security model in which each user is assigned one or more roles and each role carries a set of permissions. Changing a role's permissions updates access for users who hold that role. Why it matters: Access management stays simple as the organization grows — adding a new team member is as easy as assigning them the right role.

Reasoning Mode (AI Agents) An optional display in a webhook-type assistant where the AI's step-by-step thinking is shown as a secondary "Thinking…" stream before the final answer appears. Why it matters: Users can see how the assistant reached its conclusion, which builds trust and helps identify any flawed reasoning.

Reminder (Workflows) An automated email sent to a task assignee at configured intervals before a deadline, prompting them to act. Reminders stop automatically once the task is completed. Why it matters: Assignees are alerted proactively so deadlines are met without managers needing to follow up manually.

Reminder Scheduler Node (Workflows) A workflow node that monitors a date column in a dataset and automatically sends email reminders at configured offsets before each date — for example, 30 days before a contract expires. Why it matters: The platform monitors important dates continuously and sends alerts automatically, preventing missed renewals or deadlines across large datasets.

Role A named group that bundles together a set of permissions and can be assigned to one or more users. Built-in roles include Administrator, Manager, and User. Administrators can also create custom roles. Why it matters: Access is granted by role rather than individual, so adding a new team member automatically gives them the right set of capabilities.

Row-Level Approval (Workflows) An approval mode where the assignee records a separate decision (approve, reject, or hold) for each individual row in a dataset displayed in the task, rather than a single decision for the entire submission. Why it matters: Partial approvals become possible — accept some items and reject others in a single task screen, with a full record per row.

S

Schedule Trigger (Workflows) A workflow start node that launches the process automatically on a time-based schedule — for example, every Monday at 8 AM, on the first of each month, or one time only at a specific date and time. Why it matters: Recurring processes such as monthly reports or weekly reviews start automatically without anyone needing to remember to launch them.

Sign-in activity An administrator-visible record (the "Sign-in activity" tab in User Management) showing each user's login history, IP address, browser details, number of failed login attempts, and any account lock state. Why it matters: Administrators can detect suspicious activity — multiple failed logins from an unusual IP — and respond before an account is compromised.

Session (AI Agents) A single conversation with an AI assistant. Each session has a permanent, unique URL. Sessions can be renamed, color-coded, shared with colleagues, or deleted. Users can return to any past session and continue where they left off. Why it matters: No conversation is lost — every exchange is preserved with its own direct link so it can be revisited or shared.

SLA (Service Level Agreement) (Workflows) The combination of deadline, reminder, and escalation settings on a task node that together define the expected response time and the automated consequences of not meeting it. Why it matters: Response-time commitments are enforced automatically by the system rather than depending on individual discipline.

Smart Deploy (App Builder, Enterprise) An Enterprise integration configured from Flow Builder that wires an App Builder page to a workflow start or task. Native workflow forms do not require Smart Deploy. Why it matters: Existing data-driven pages can participate in RAPTIX workflows without duplicating workflow logic in the page.

Soft Delete / Trash A deletion pattern in which removing a document or template marks it as deleted and moves it to a Trash view, but does not permanently destroy it. Administrators can restore soft-deleted items. Why it matters: Accidental deletions are recoverable — nothing is permanently gone until an administrator explicitly clears the trash.

Source Card (AI Agents) A card displayed below an AI answer in AI Agents showing the document name, page number, relevance score, and a text excerpt for each citation used. Source cards link to the original document in the PDF viewer. Why it matters: Users can verify every claim in an AI answer by jumping directly to the original source document with one click.

Split Branches Node (Workflows) A workflow node that divides the process into two or more parallel branches that all execute simultaneously, allowing independent work to proceed at the same time. Why it matters: Notifying three departments or running three checks simultaneously takes as long as the slowest one, rather than the sum of all three.

SSO — see Microsoft SSO

Sub-Workflow (Workflows) A workflow that is designed to be started by another workflow rather than triggered directly by a user or schedule. Sub-workflows receive typed input data from the parent workflow and can return results. Why it matters: Complex processes can be broken into modular, reusable components — update the sub-workflow once and every parent that calls it benefits automatically.

System Permission One of 25+ named capabilities governing platform-level access — such as the ability to manage users, configure email, view the audit log, or access the administration panel. System permissions are one of the four tiers within a permission bundle. Why it matters: Granular system-level capabilities are assigned deliberately, so no user accidentally gains administrative power.

T

Task (Workflows) A workflow step assigned to a specific user or role, requiring a human decision or action before the workflow can continue. Tasks appear in the assignee's Pending Tasks inbox and can include document review, data entry, or approvals. Why it matters: Every step that needs a human decision is clearly assigned, tracked, and escalated if not completed on time.

Temperature (AI Agents / Knowledge) A setting that controls the balance between factual precision (low temperature) and creative variation (high temperature) in AI-generated answers. It can be configured per assistant and adjusted per session by the user. Why it matters: Users can tune the assistant for their current task — more precise when looking up specifications, more creative when brainstorming.

Three-Tier Permission Inheritance (Documents) The permission resolution model in Documents: global grants apply first, then folder grants, then per-document grants. The most permissive applicable rule wins. Why it matters: Administrators can grant broad access and then narrow it for specific sensitive documents without creating conflicting or confusing rules.

Trash — see Soft Delete / Trash

Trigger (Workflows) The event or condition that starts a workflow. Workflows supports five trigger types: Manual (button click), Webhook (external system call), Schedule (time-based), Sub-Workflow (called by another workflow), and Email (incoming email matching filter rules). Why it matters: Workflows can be started by the right event at the right time — no manual monitoring or handoff required.

V

Variable (Workflows) A named piece of data that is created, passed between nodes, and used throughout a workflow. Variables can hold text, numbers, dates, lists, or files — and can be referenced in conditions, emails, and AI prompts using the {{variable_name}} syntax. Why it matters: Data submitted at the start of a workflow is available to every step — approvers, emails, AI agents, and external systems all work from the same live values.

Variable Panel (Workflows) A slide-in panel in the visual designer that lists every workflow variable by the node that created it, along with its type and a one-click copy button for the {{variable_name}} placeholder. Why it matters: Designers never need to memorize field names — every available piece of data is visible and copyable from the panel.

Version / Version History (Workflows / Documents / Knowledge) A timestamped snapshot of a workflow design, document file, or processed markdown at a specific point in time. Each save (manual or automatic) creates a new version entry. Any past version can be restored. Why it matters: Changes are never permanent — any mistake can be undone by restoring a previous version, and a full change history is always available for review.

Visual Designer (Workflows) The drag-and-drop canvas used to build and edit workflow designs. Users drag nodes from the sidebar onto the canvas, connect them with arrows, and configure each node's settings in a side panel. Why it matters: Complex multi-step processes are designed visually with no code — the diagram is both the specification and the executable process.

W

Webhook (Workflows) A mechanism for connecting the platform to an external system using an HTTP request. An inbound webhook trigger starts a workflow when an external system sends a request; an outbound webhook node sends data to an external system mid-workflow. Why it matters: Workflows integrates with any external software — ERP, CRM, ticketing systems — without needing a dedicated connector.

Widget (App Builder) A pre-built App Builder component — such as a text input, dropdown, table, date picker, or file upload button — placed on a page to create an app interface. Why it matters: Apps are built by assembling ready-made components rather than writing interface code, so forms and dashboards can be created in minutes.

Workflow (Workflows) A defined, reusable process design — created in the visual designer — that specifies every step, decision point, assignment, and notification from start to finish. A workflow is the blueprint; when it runs, it creates a workflow instance. Why it matters: Business processes are standardized and automated — every case follows the same path, with consistent quality and full traceability.

Workflow Instance — see Instance

Workspace (Applications) The top-level organizational unit in Applications, grouping related apps together. Workspaces typically correspond to a department or business area. Why it matters: Apps are organized so teams can find the tools that belong to their area without navigating an unstructured catalogue.

Z

ZIP Download (Documents / Workflows) A function that packages multiple files or an entire folder — preserving the original folder structure — into a single compressed archive for download in one action. Why it matters: Users can retrieve all documents related to a project or workflow instance in one step rather than downloading files individually.

Last updated: 2026-07-16. For questions about platform terminology, refer to the relevant guide or contact your system administrator.