Groovy coding conventions and practices

   Exchange Pre-configured Maestro services.  |   Platform Developer |  All versions   This feature is related to v5.1 and higher.

The Groovy coding conventions and practices referenced below are intended to promote consistency and reliability in the services built for the Temenos Journey Manager platform. It is recommended that anyone developing TJM services, for whatever purpose, review and adhere to these guidelines.

Any TPac being proposed for inclusion in the Journey Exchange program will be assessed according to its compliance with these guidelines before being accepted into the program.

• Use defined type declarations in favor of dynamic types
• Naming conventions for Groovy services
• Write null-safe Groovy code
• Groovy error handling and reporting
• Log third-party service calls
• Encapsulate common code in shared groovy classes
• Manage external service timeouts