Infor SyteLineFree referencePDF, Excel, Word exportInfor SyteLineAll Infor SyteLine (CloudSuite Industrial) tools

SyteLine Admin Forms and Utilities Reference

SyteLine 9 and CSI 10 spread administration across client forms and Windows utilities on the servers. This reference lists the ones admins and developers use most, grouped by area, with what you do in each and where to open it.

Download:
NameTypeAreaWhat you do thereHow to open
Configuration Manager
Utility
Configuration
Create and edit configurations: application database, Runtime (Client) forms database, Objects metadata database, and configuration groups
Windows program on the utility server
Service Configuration Manager
Utility
Configuration
Set up the framework services on a server, including the accounts and settings they run with
Windows program on the utility server
LogMonitor
Utility
Configuration
Watch framework and IDO runtime log messages live while you reproduce a problem
Windows program on the server
InforDBCL
Utility
Configuration
Database command line utility for database tasks run outside the forms
Command line on the server
FormSync
Utility
Customization
Compare and merge forms, global objects and strings between forms databases, for example after an upgrade
Windows program on the utility server
App Metadata Transport
Utility
Customization
Export and import IDO and application metadata between environments
Windows program on the utility server
IDO Custom Assemblies
Form
Customization
Import compiled IDO extension class assemblies (DLLs) into the objects metadata
Open by form name
Background Task Definitions
Form
Background tasks
Define tasks that run on the server: reports, stored procedures, executables
Open by form name
Active Background Tasks
Form
Background tasks
See tasks queued or running now and cancel a stuck one (form ActiveBGTasks)
Open by form name
Background Task History
Form
Background tasks
See finished tasks with status, messages and run times (form BGTaskHistory)
Open by form name
Event Handlers
Form
Events
Define handlers that run actions when an IDO or application event fires
Open by form name
Event Handler Status
Form
Events
Check the state of handlers that ran for an event
Open by form name
Event Status
Form
Events
Check events that were raised and whether they finished, failed or wait
Open by form name
Event Global Constants
Form
Events
Maintain constants that event handlers and workflows read
Open by form name
Replication Rules
Form
Replication and BODs
Define which categories replicate to which site or to ION
Open by form name
Replication Management
Form
Replication and BODs
Run Regenerate Replication Triggers after changing rules
Open by form name
Replication Document Outbox
Form
Replication and BODs
See outbound BODs and replication documents waiting or failed
Open by form name
Replication Document Inbox
Form
Replication and BODs
See inbound BODs and replication documents and their errors
Open by form name
Replication Tool
Form
Replication and BODs
Run replication for selected objects, for example an initial load
Open by form name
Report Options
Form
Reporting
Set default options for a report, such as output format and print settings
Open by form name
Document Types
Form
Reporting
Maintain the document types used to classify attached documents
Open by form name
Users
Form
Security
Create users, set passwords, sites and group membership
Open by form name
Groups
Form
Security
Maintain authorization groups and their members
Open by form name
Object Authorizations for Groups
Form
Security
Grant or deny read, edit, insert, delete and execute on forms and IDOs per group
Open by form name
License Management
Form
Security
Apply licence documents and assign licence modules to users
Open by form name

Applies to SyteLine 9.x and CSI 10.x on-prem with the Mongoose framework. Forms open by name from the form search in the client; utilities are Windows programs installed on the utility or application server, so you need server access to run them. Form captions can differ slightly by release and language, so search on a key word such as Replication or Background if an exact name does not match. Your group needs authorization on each form.

Get an admin runbook for your site

Send us your server layout and we will turn this list into a site-specific SyteLine admin runbook with checks for tasks, events and replication.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Search by area to see one job end to end, such as every Replication and BODs entry when an integration stops, or every Background tasks entry when a report never arrives. The Type column tells you whether you need the client or the server: forms open from the form search in the client, utilities run on the server. Export the list to Excel and add the server names and the people allowed to use each utility in your site, and you have the core of an admin runbook. Keep the Security rows next to your quarterly access review.

Where things live

Configuration Manager holds the configurations users pick at login. Each configuration points to an application database and, on separate tabs, to the Runtime (Client) forms database and the Objects metadata database; configuration groups control which configurations a client can see. Background tasks run on the server: a report or procedure launched from a form is queued, shows in Active Background Tasks while it waits or runs, and lands in Background Task History with its status and messages. Events run through event handlers; Event Status and Event Handler Status show whether a fired event finished. Replication and BOD traffic is visible in the Replication Document Outbox and Inbox.

Worked example: a report never printed

A user runs a report and nothing arrives. Open Background Task History and filter on the user and today. If the task shows an error, the message there usually names the cause, such as a missing parameter or a database error. If it is not in history, check Active Background Tasks: a task that sits queued points at the service that processes tasks on the utility server, so check that it is running and use LogMonitor while you resubmit. If the task completed but output went to the wrong place, check the report's Report Options and the printer chosen on the report form.

Gotchas

Changing replication rules does nothing until you regenerate replication triggers in Replication Management. Importing an assembly on IDO Custom Assemblies is not enough on its own: the IDO must also name the custom assembly and extension class in its metadata. FormSync and App Metadata Transport move customizations between environments, so run them against test first and back up the forms and objects databases. Object Authorizations for Groups grants rights per form and per IDO, and a user can open a form yet fail on save if the underlying IDO is not authorized.

Frequently Asked Questions

How do I run a report in SyteLine?

Open the report form by name from the form search, fill the selection ranges, then use Preview or Print. The request runs as a background task on the server. Watch it in Active Background Tasks and check the result and any error message in Background Task History.

Where do I see printers in SyteLine?

Reports print from the server that processes background tasks, so the printers available are the Windows printers installed there. The printer and output options are chosen on the report form and can be defaulted per report in Report Options. If a printer is missing, it usually has to be added on that server.

How do I bookmark a form in SyteLine?

Drag the form into My Folders in the client Explorer, where each user keeps personal shortcuts that open with one click. Admins can place shared shortcuts in Public Folders for a whole team. If a form does not appear in search, check that the user's group has authorization for it.

Where is the SyteLine 10 manual for administrators?

Infor publishes the CSI and Mongoose administration, replication and IDO development guides on docs.infor.com. This page is a quick map of forms and utilities; use the guides for full procedures and the release-specific details of each form.

If your support team wants to ask SyteLine why a background task failed or which events are stuck, in plain English on your own servers, we can set that up read-only.

ArchRay builder
Design the on-prem AI stack for Infor SyteLine: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP