story: ext. plugin results value resolvers and use ext. plugins in bb - #830
story: ext. plugin results value resolvers and use ext. plugins in bb#830mbritense wants to merge 9 commits into
Conversation
|
Important Review skippedToo many files! This PR contains 159 files, which is 59 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (159)
You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…into story/771-plugin-value-resolvers
|
There seems to be no runtime validation or binding of the returned values. I ran the test plugin and tried to bind the title to a case property. the title was missing from the plugin invocation result. So there a question here: Do we always need to return all result fields as described in the manifest, or are they optional? And a bug: The title is in this case actually returned (though might be null) in the result, but not received on the valtimo side. I think returning a null value can be valid and should not be confused for "no value returned". |
|
Please check the external plugin module integration tests. |
|
When exporting and importing a case using an external plugin it will sometimes ask to match the plugin configuration, but sometimes it's missing. I configured a case, exported it. Now when importing using a new name i always get to choose the plugin, see bottom row bezwaar_1.0.1_2026-07-23_11-25.case.zip Then i exported that config and imported that again using a new name and i don't get to choose it.
|
|
"Deleting a configuration referenced only by a BB link is still allowed." Should this be allowed? The configuration is used regardless. |




Closes generiekzaakafhandelcomponent/gzac-issues#771 and generiekzaakafhandelcomponent/gzac-issues#768
Reviewer test guide
#771 — Action result write-back
outputsin its manifest (e.g.case-summary) to a service task → the wizard shows an extra Output mapping step (Next on the config step, Save on the mapping step). An action withoutoutputsgets no extra step (Save directly).resultvalues land on the case/BB document (pv:targets become process variables). A plugin returningnullfor a mapped key is skipped with a warning instead of failing the process.v-select/ value-path-selector screens (e.g. BB mappings step) for regressions.External plugins in building blocks
BUILDING_BLOCKreference (no configuration id).pluginId@versionmatches by default, other versions behind a warning. Run the case → the action executes via the mapped configuration.Import/export parity
EXTERNAL_PLUGINcase tab, re-import: the PLUGINS step shows external rows with a configuration chooser (version-mismatch warning). After import the links point at the chosen configuration and the case tab still works.Fixes worth spot-checking