Search the Community
Showing results for tags 'amalgamation'.
Found 1 result
We have a number of different progressive captures which ask very specific questions along with appropriate logic linked to them, which will not necessarily a one to one direct match directly summary and description. At the moment we have to implement logic in the the BPM which branches based on the progressive capture used to then formulate and build the the summary and description (as well as other fields and custom fields) based on the progressive capture responses. This makes the BPM quiet complex when attempting to use a generic/smaller number of BPM's. Can we raise an enhancement request to have amalgamation node, a bit akin to the BPM 'Update Request' node which can be run at the end of the Progressive Capture to populate the necessary fields in the new request. The added advantage is that if for some reason the BPM fails to trigger the main standard fields are populated. Cheers Martyn