Bitta Commission guide
Job queues, monitoring, and diagnostics
The job queue entries Bitta Commission uses, run schedules and run operations setup, the run log, telemetry, integrity sweeps and how to collect sanitized support diagnostics.
status: verified applies-to: 1.1.2.0rev: 1
Bitta Commission does most of its background work through standard Business Central job queue entries: scanning posted documents, releasing eligibility, running scheduled calculations, evaluating deadlines and refreshing the license. This page lists those jobs, explains how to monitor them with the run log and the operations tiles, and shows how to collect diagnostics for support.
Before you start
- Creating or changing job queue entries requires the Bitta Commission Setup Administrator permission set and the standard Business Central permissions for Job Queue Entries.
- The app creates the scanner and deadline entries On Hold. They do not run until you review the schedule and set them to Ready in Job Queue Entries.
- The job queue runs under the user who set the entry to Ready. Make sure that user has the commission permission sets the job needs.
Job queue entries the app uses
| Job queue entry description | Created by | Schedule |
|---|---|---|
| Bitta Commission native sales scanner, native cash scanner, native cost scanner, pending eligibility release | Prepare Native Scanner Jobs on Bitta Commission Setup | Recurring, every Native Scan Interval (Minutes) (15 when blank). Created On Hold. |
| Bitta Commission service, project, resource time, purchase, controlled G/L and recurring and subscription capture scanners | Register Scanner Jobs on Commission Source Capture Setup | Recurring, same interval. Created On Hold. |
| Bitta Commission deferred commission amortization, payout and liability forecast refresh, anomaly scan, commission aging evaluation | Register Scanner Jobs on Commission Source Capture Setup | Recurring, same interval. Created On Hold. |
| Bitta Commission scheduled incremental run (one per schedule) | Enable on Commission Run Schedules | Daily at the schedule's time. Enqueued Ready. Disable removes the entry. |
| Bitta Commission batch run resume | Create Resume Job on Commission Run Operations Setup | Every Resume Interval (Minutes). Enqueued Ready. Continues unfinished batch runs and applies run log retention. |
| Bitta Commission workflow deadlines (approval and dispute SLA) | Create deadline job on Commission Workflow Setup | Hourly. Created On Hold. |
| Refresh Bitta Commission license | Automatically after a direct license activation | Daily. Created Ready. Deactivate License removes it. |
After preparing the native jobs, choose Validate Native Scanner Readiness on Bitta Commission Setup. It checks that exactly one governed sales, cash and cost scanner job exists with the current setup and a safe status. See Business Central sales sources.
TIP
The jobs are designed to be rerun. Scanners keep cursors, and release and calculation steps are keyed so that a retried run does not count the same document twice.
Scheduled calculation runs
Commission Run Schedules starts incremental batch runs for open periods at a set time of day.
- Open Commission Run Schedules and add a schedule with a code, description, calendar (blank for every calendar), plan, optional plan version (zero uses the latest published or active version at run time), optional participant filter and time of day.
- Decide whether the schedule may run a full baseline batch for a period with no baseline yet, and whether it includes reopened periods whose reopen chose the scheduled incremental delta policy.
- Choose Enable to create the job queue entry, or Run Now to start immediately.
- Check the last run, the last batch run it started and its result on the same line. Batch Runs opens the batch runs of the schedule.
See Calculation runs and schedules.
Run operations setup
| Field on Commission Run Operations Setup | What it does |
|---|---|
| Max Facts Per Invocation | How many source facts a batch run processes before it suspends and resumes later. The ceiling is 10,000. |
| Max Duration (Seconds) | How long one invocation may run before it suspends. Zero means no limit. |
| Resume Interval (Minutes) | How often the resume job continues unfinished batch runs. |
| Reconciliation Tolerance | The amount difference tolerated when batch control totals are reconciled to child runs. |
| Default Trace Level | Errors, Summary (per invocation) or Detail (per source fact). |
| Log Retention (Days) | How long run log entries are kept. Zero keeps every entry. |
| Error Exception SLA (Hours), Warning Exception SLA (Hours) | When exceptions of each severity must be resolved. The due time is stamped on the exception, which is flagged overdue afterwards. |
Monitor runs and exceptions
- Commission Run Log lists entries written by batch and trial runs: time, level, event, message, source fact, count, duration, and the calculation, batch or trial run. Apply Retention removes entries older than the configured retention.
- The Commission Operations tiles on the role center count running and failed calculation runs, open exceptions, quarantined staging rows, failed exports, overdue approvals, SLA breaches and open disputes. See Role centers and reports.
- Commission Exceptions is the worklist for anything that stopped processing. See Exceptions and data quality.
- For job failures, open Job Queue Entries and the standard Job Queue Log Entries for the entry.
Telemetry
When a batch calculation run invocation finishes, the app sends one telemetry event, BAACOMM-RUN-0001 "Commission batch run invocation finished", to the publisher's Application Insights resource. It carries the operation code, mode, result code, duration in milliseconds and a count band, classified as system metadata. It contains no amounts, customer content or participant identifiers. Release 1.1 emits no other telemetry events.
Integrity sweep and business continuity
Commission Business Continuity records your backup and restore expectations and runs the read-only integrity sweep that samples entry hashes across every commission ledger. Run a sweep after any restore and before a period close you want to rely on. Record Restore Test records a restore test together with a verifying sweep. See Audit and security.
Collect support diagnostics
- Open Commission Support Diagnostics. The page collects its facts when it opens. Choose Collect to refresh them.
- Review the lines by Section Code:
| Section | What it contains |
|---|---|
| VERSION | App version and ID, data version, installed version, data schema version, last upgrade codeunit and upgrade completion time. |
| ENVIRONMENT | SaaS or on-premises, sandbox or production, a hash of the company ID, client type. |
| SETUP, FEATURES, IMPLEMENTATION | A hash of Commission Setup, each module and whether it is on, implementation path and stages, migration mode. |
| POLICY | Counts of country policies and signed agreements, in bands. |
| JOBQUEUE | Each commission job queue entry and its state. |
| ERRORS | Open exception codes and their counts, in bands. |
| LICENSE | The entitlement state. |
| INTEGRITY | The last upgrade verification, the last integrity sweep and encryption status. |
- Lines with a Severity Code of WARNING or BLOCKING need attention.
- Choose Export Package to download a text file for Bitta Apps support. The export is recorded in the audit trail.
The package contains no participant names, amounts, document numbers or activation codes. Upgrade Verifications opens Commission Upgrade Verifications, and Business Continuity opens the continuity page.
NOTE
Never send your license activation code to support. The diagnostics package and license diagnostic codes are enough to investigate a license problem.
Related pages
Support diagnostics collect sanitized facts to share with Bitta Apps.