We have an orchestration executing as a long running transaction
managing an invoice process. The transaction is really long since it's
not complete before the customer has paid the full amount. That could
be from 5 days to over 3 months. Each invoice has customer information,
such as the invoice adress. This adress information can change during
the process and the invoice need to be updated with the new adress
while the invoice still is in the process.

My question is how should we design and technically make that possible?

Prior to today, this application was build as a client server
application on top of SQL Server. That gave us access to the
centralized data and we could easily update the adress information.
Now, the data is decentralized and spread out on process instances.

[ Post a follow-up to this message ]