Know the moment it happens, without polling.

The problem

Finance & Operations ships a business events framework, but its catalog covers a fraction of the moments integrations care about, mostly at the document-posting layer. A production order starting, a transfer order shipping, a customer going on credit hold, a quality inspection failing: none of them has a native event. So integration teams poll tables on a timer, build brittle batch jobs, or bolt change tracking onto entities that were never designed for it. Polling reacts minutes or hours late, misses changes between runs, and loads the production database with questions nobody asked.

How Lattice answers it

Lattice adds 80 business events at the process level, each capturing a specific operational moment as it happens and sending an enriched, integration-ready payload to the endpoint you choose.

They are built exactly the way Microsoft builds its own: they appear in the standard business events catalog, you activate the ones you want and point them at an endpoint, and they behave like first-party events in monitoring, retry and governance. No developer is involved, and an event you have not activated costs nothing.

Events fire from the business process that causes the change rather than from a raw table write, so a canceled or partial posting does not raise a false signal. Delivery happens after the transaction commits: a delivery failure never blocks or rolls back the business action. Payloads carry readable status names next to their codes, and amounts with their currencies, so downstream systems use them as they arrive.

Some events go further than a document moment. A scheduled scan raises an event for any workflow that has stalled or failed. Integration failures that land in the dead-letter queue raise one too. Batch job events can be filtered so you hear only about the jobs you care about. And your own X++ code can raise an ad-hoc event through the same pipe.

Getting started is just as considered. The event catalog explorer downloads a sample payload for any event so consumers can be built before anything fires. A coverage report compares what you have activated against the standard catalog. And resync jobs publish an event for every existing customer, item or external item, so a downstream system can take its initial load through the same channel it will use every day.