Skip to main content

Changelog

Changes to Lattice that affect customers. Each release ships one package per supported Finance and Operations version; the Builds line under each release names them.

[Unreleased]​

Added​

  • Integration operations: 30 services with 182 inbound operations in 13 module-aligned service groups, covering sales and purchase orders, returns, free text and vendor invoices, expense reports, inventory journals, production, general ledger and payment journals, fixed assets, project journals and workflow. Every operation runs the same validation as the user interface, is idempotent on its request id, and returns one response shape.
  • Posting existing journals: general ledger, inventory, project, production and trade agreement journals that already exist in Finance and Operations, for example from a data management import, can be posted by journal number. The caller needs the Lattice permission that posting that kind of journal directly requires, including the permission for each intercompany, fixed asset or project line.
  • General ledger and payments: general journal lines can post to customer, vendor and bank accounts, so customer invoices, vendor adjustments and bank transfers can be posted through a general journal. Vendor payments by check can be generated and posted, and reversing a check payment creates a check reversal journal for review.
  • Fixed assets: besides acquisition, depreciation and disposal, operations post other fixed asset transactions, transfer an asset to another location or dimension, split an asset, and reverse a fixed asset transaction. Reversal is a high-risk operation with its own privilege.
  • Batch, asynchronous and preview processing: most posting operations have a batch counterpart for many documents in one call, any operation can be submitted asynchronously and polled by tracking id, and preview mode returns the projected result of a posting without writing anything.
  • Operations tooling: the Service test console, per-operation interaction logging, daily call statistics, and a dead-letter queue where a failed request can be corrected and resubmitted from the Integration operations console. The Service call log shows, for each failed call, the error messages the caller was given, on the page and in the LatticeServiceCallLogs entity. The maintenance jobs (dead-letter retry, idempotency and business event reconciliation, workflow alerts, statistics rollup, log and file ingestion cleanup, sales price effectivity events) run by themselves as background processes under System administration > Setup > Process automations, so there are no batch jobs to schedule.
  • Data entities: 149 data entities for OData and data management (103 writable, 46 read-only), including customer and vendor contact entities keyed by account number, document attachments by business key, high-performance read feeds, cross-reference keys for other systems' ids, and 15 set-based import entities for large journal imports, customer invoice journals among them.
  • Business events: 81 business events across 16 modules, in the standard business events catalog, with enriched payloads and a correlation envelope. Delivery never blocks or rolls back the business transaction.
  • File ingestion: scheduled pickup of JSON, XML and delimited files from Azure Blob storage, Azure file shares and SFTP, with transforms, parallel processing, duplicate detection, and archive and error folders, monitored from the File ingestion operations workspace.
  • Recurring integrations: the Recurring integration health page shows every recurring data job with a health state and the reasons for it: a batch job that stopped or is missing, no enabled client application, messages waiting too long or stuck in processing, failed messages and executions with row errors, a sender that has gone quiet, and field mapping errors in the job's data project. The job's details page goes from a message to its execution and the staging rows that failed, and opens the standard pages in context. Thresholds are set per job, three tiles in the Integration operations workspace show the jobs that need attention, and a business event reports a job whose health changes. The LatticeRecurringJobHealths and LatticeRecurringJobMessages entities give the same information to monitoring tools.
  • Data management configuration: a configuration specification carries each entity line's field mapping as the generated default mapping, as changes from it or as an explicit list, and can be compared with an environment without changing it. Field mappings can be checked for unmapped key and mandatory fields, mappings to fields that no longer exist and new entity fields, and refreshed without losing custom mappings. Default values, value conversions and transforms in a mapping are compared but not applied.
  • Pricing and order guardrails: effective sales-price inquiry, sales trade agreement creation and posting, and an optional inbound-order policy (price-tolerance hold, auto-confirmation, edit lock after confirmation).
  • API documentation: Postman collections and OpenAPI specifications generated for the services and entities, and contextual help on every Lattice page.