Processes
Many AdmCloud operations (Excel migrations, mass recalculation of accounting entries, mass generation or printing of invoices and payroll, price or demand-plan calculations, production order generation, etc.) don't finish instantly while you wait on the screen. Instead of leaving you stuck, AdmCloud runs them in the background as a process and lets you keep working on something else. The Processes screen is where you can see, at any time, which processes have run, how they're progressing and whether they finished successfully or with errors.
What is it and what is it for?
Each row on this screen represents a long-running operation that was launched from somewhere else in AdmCloud: who started it, when, how many records it processes in total, how many it has processed so far and, once it's done, whether the result was successful or had errors. It lets you confirm that a migration, a recalculation or a bulk generation is actually running (or has already finished), without having to keep the original screen open and wait.
This screen is read-only: processes are not created from here. A process is created automatically when you (or another user in your company) run one of the system's bulk operations; this screen only lets you follow up on those processes and, for some types, request their cancellation.
Screens in this area
| Screen | What it does |
|---|---|
| List |
Shows processes in two variants, switchable without reloading the page:
|
| Details | A read-only view of a single process: name, total records, start, end, status, duration and error message (if any). It can only be opened for processes that support cancellation and are still in progress; this is also where you request the cancellation. |
How to use it
- Launch the bulk operation from its own screen. For example, a data migration, a price recalculation, a payroll generation or a bulk invoice printing. AdmCloud creates the process automatically; you don't need to do anything on this screen for it to start running.
- Follow its progress. Open Processes (the "Today's Processes" variant) and check the status column: while it's running you'll see the completion percentage, which refreshes on its own every 20 seconds. To force an immediate update, use the Refresh Progress button.
- Review the result when it finishes. If the process completed and produced a report or is tied to a specific screen, you'll see a link to Show Report in PDF Format or Go to Screen. If it also recorded rows with errors (very common in migrations), the View Records with Errors link appears so you can download an Excel file detailing which rows failed and why.
- Cancel a running process, if you need to. Only some process types support cancellation (see below), and only while they're in progress; for those, the process name is a link to its Details screen, where you'll find the Cancel Process button. Cancellation isn't instant: it marks a request, and the process checks for it periodically, so it may keep running for a few more moments after you ask to cancel it.
- Check the full history. Switch to the All Processes tab to see processes from previous days, with their end date and total duration.
Key fields
| Field | What it's for |
|---|---|
| Start Date | When the process started running. |
| Name | Identifies which operation it is (for example, "Item Migration" or "Price Recalculation"). It's only a link to the detail when the process supports cancellation and is in progress. |
| User | Who started the process. |
| Total Records | Total number of rows or items the process has to handle, when known in advance. |
| Executed | How many of those records have been processed so far. |
| Memory Consumption | Memory used by the process on the server. Only visible to technical/support users, not to regular users. |
| Status / Progress | A colored label with the current status (see the statuses section below), or the completion percentage while it's in progress. |
| End Date ("All Processes" only) | When the process finished (successfully or with an error). |
| Duration ("All Processes" only) | Total time the process took, or the elapsed time so far if it's still running. |
| Output Message | Free text the process leaves when it finishes; usually holds result details or, if it failed, the error's cause. |
Process statuses
- Queue: the process was created but hasn't processed any records yet.
- In Progress (%): the process is actively running; the percentage is calculated against the known total of records.
- Completed: the process finished without errors.
- Error: the process stopped due to an error; the details are usually in the Output Message.
- Expired: the process has been running for more than 24 hours without finishing. This usually means something got stuck; if you see an expired process, report it to support.
Availability, permissions and conditions
- Any logged-in user can view the Processes List; it requires no specific permission.
- Opening a process's Details and requesting its cancellation does require the "Configuration" permission of the System Administration module.
- Cancellation is only available for certain process types: price recalculation, demand-plan calculation, production order generation, payroll quote generation, interest invoice or note generation, and bulk printing of invoices, credit notes, cash receipts and payroll payment slips. All other processes (for example, migrations) cannot be canceled from here once started.
- The "Today's Processes" variant can show an extra notice with the date of the next automatic inventory cost recalculation, when one is pending.
Tips and common pitfalls
Did a migration finish but some records didn't load? Check whether the View Records with Errors link appears; the downloaded Excel file shows exactly which rows failed and why, so you can fix them and re-import.
No need to refresh the page by hand. The "Today's Processes" variant updates itself every 20 seconds; you can leave it open in one tab while you work in another.
Canceling a process doesn't stop it instantly. The system marks the cancellation request, but the process only stops once it checks for it on its next step, so it may take a few seconds to disappear or show as stopped.