We develop quite a few workflows that serve a basic need: forms to document assets. Those are quite repetitive tasks, with the same pattern: One workflow to create, one workflow to manage Load the characteristics values into memory Present the user with forms to update information Save the input data back to the database Best practices for workflow development What are the best ways to write code for loading and saving characteristics? Here’s what I like, personally. Loading characteristics into...

groovy-lib and workflow best practices | Developers

groovy-lib and workflow best practices | Developers | Collibra Community