Structured technical and operational writing about architecture, integrations, banking systems, SaaS, operations and knowledge transfer.
Temenos Transact R22 is best learned as an application platform with defined banking applications, records, versions, enquiries, APIs, hooks, services, and a TAFJ runtime—not as a collection of isolated routines. Developers become effective faster when they f…
Read articleOFS provides a structured way for external or internal processes to invoke Transact application operations and receive a response. The important engineering work is not string concatenation; it is selecting the correct application/version, identity, field con…
Read articleMaintainable Temenos customization respects the owning application lifecycle and keeps bank-specific policy isolated from generated/vendor code. The safest change is the smallest documented extension that expresses one rule, has clear inputs, produces determi…
Read articleA reliable Temenos Java change needs a repeatable path from source in Design Studio to compiled/package artifacts, environment configuration, TAFJ runtime loading, and transaction verification. Problems appear when teams treat a successful local compile as pr…
Read articleExternal applications should integrate with Temenos through controlled, documented service boundaries rather than learning internal record structures. The bank-owned integration layer can expose stable business APIs, map to the appropriate Temenos interface,…
Read article