Epicor Kinetic Certification (Kinetic Tools Management) key terms

The Epicor Kinetic area that covers configuring, running, and monitoring the administrative and development utilities that support a Kinetic environment, including system tools, conversions, and diagnostic programs.

A browser-based administrative interface used to review and manage a Kinetic environment, including app server settings, sessions, and system health information, without requiring the older desktop-only administration tools.

The server-side runtime that hosts the Epicor application logic and processes client requests in a Kinetic deployment. It sits between the web server and the database and is a common target for tools configuration.

A Kinetic tool that lists running and completed background tasks, showing their status, submitter, and any error messages so administrators can track long-running processes and scheduled work.

A background service that polls for submitted tasks and executes them on the app server. Multiple agents can be configured, and each processes tasks assigned to its designated agent schedule or agent ID.

Work submitted to run asynchronously on a task agent rather than in the user's foreground session. Examples include reports, conversions, and large updates that would otherwise block the client.

A background task configured to run at a future time or on a recurring schedule, such as nightly reports. Schedules are defined in the task submission settings and managed through the System Monitor.

A named set of time windows that determines when a task agent is allowed to process tasks. Submitting a task to a schedule restricts execution to those windows, helping balance server load.

A Kinetic tool for reviewing and running data conversion programs that transform or update existing records, typically after an upgrade or when applying a fix that requires a one-time data change.

A defined routine, often identified by a numeric conversion ID, that modifies data in a controlled way. Conversions are run through the Conversion Workbench and can be previewed before being applied.

A conversion execution mode that reports what the program would change without committing the changes to the database. It lets administrators validate impact and timing before a real run.

The process of moving a Kinetic environment to a newer release, including schema changes and required conversions. Tools Management covers the utilities used to prepare, execute, and verify an upgrade.

The persistent data store behind the app server, typically SQL Server in Kinetic deployments. Tools Management includes utilities for checking connectivity, running scripts, and monitoring database health.

The defined structure of database tables, columns, and relationships. Schema changes accompany upgrades and require conversions or scripts to align existing data with the new structure.

The metadata that describes Kinetic tables and fields, including labels, data types, and relationships. Tools such as the Data Dictionary Viewer let administrators inspect how fields map to database columns.

A user-defined attribute attached to a Kinetic record or field to store additional information without changing the base schema. Extended properties are configured through dedicated maintenance tools.

A customizable field added to a Kinetic form or table so a company can capture data specific to its processes. UDFs are created and maintained through the tools that manage field customization.

A layer of changes applied to a Kinetic form, such as added fields, changed layouts, or behavior adjustments. Customizations are created in the customization tools and deployed per user or company.

A stored set of customization changes that can be applied to a base Kinetic form. Layers can be combined and ordered, and administrators manage which layers are active for which users.

The act of publishing configuration or customization changes so they take effect for users. In Tools Management, deployment steps may include recycling the app server or refreshing client caches.

Restarting an application pool or app server process to clear cached state and load updated configuration. Recycling is a common step after deploying changes in a Kinetic environment.

The administrative function of viewing and terminating active user sessions in a Kinetic environment. It is used to free licenses, resolve locked sessions, or force users to reconnect after maintenance.

The process of assigning and monitoring Kinetic user and module licenses. Tools expose license usage so administrators can see consumed seats and reclaim them when sessions end or are terminated.

A file or viewer that records app server activity, errors, and diagnostic messages. Administrators use server logs to troubleshoot failed tasks, conversions, and connectivity problems.

A diagnostic capture of the calls and queries a session makes while a user performs actions. Traces help pinpoint the source of errors or performance issues in Kinetic tools and business logic.

Tools and practices for measuring how long Kinetic operations take and identifying bottlenecks. They include timing logs, traces, and database query analysis used to tune the environment.

A utility that lets administrators run ad hoc SQL statements against the Kinetic database for investigation or reporting. Access is typically restricted because direct writes can bypass business logic.

A scheduled service that runs periodic maintenance and background processing for the environment. It is distinct from user task agents and is configured during environment setup.

Configuration that defines the SMTP server and sender details Kinetic uses to send notifications, reports, and system messages. Incorrect settings are a common cause of missing task alerts.

A notification generated by Kinetic when a defined condition occurs, such as a task failure or a threshold being reached. Alerts are delivered through configured channels like email.

Settings that define behavior for a specific company within a Kinetic database, including defaults used by tools and background processing. Multiple companies can coexist in one environment.

Settings that define behavior for a specific site within a company, such as scheduling and processing defaults. Site-level settings can override or refine company-level configuration.

A defined group of tasks or reports that can be submitted together as one background job. Process sets simplify recurring multi-step work and are managed through the tools that schedule tasks.

A definition of how a report is rendered, including the output format and the layout used. Report styles are maintained in the reporting tools and selected when a report is submitted.

A definition that specifies which tables and fields a report draws from and how they are joined. It controls the data set available to a report style and its output.

A user-built query that combines Kinetic data for analysis and reporting. BAQs are created in the query tools and can be used as data sources for dashboards and reports.

A configurable view that presents queries, charts, and trackers in one screen. Dashboards are assembled with design tools and deployed to users as part of the environment configuration.

The tool for controlling which programs and dashboards appear in the Kinetic navigation menu and who can access them. It governs the user-facing entry points to deployed tools.

The set of user, group, and access settings that determine what a person can view or change in Kinetic. Security settings gate access to administrative tools and sensitive data.