About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Thank you again for submitting this RFE!
This request has been delivered in the June 21, 2023 OpenPages 9.0 release.
Please refer to: https://www.ibm.com/docs/en/opw/9.0.0?topic=900-workflow-enhancements-in
Thank you again for submitting this RFE!
This request is a candidate for a future generally available (GA) release. IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. IBM will update this request to reflect any changes.
This functionality would be particularly useful when complex validations are used in workflows. Right now, the error message when a complex validation fails is very cryptic. There is a rejected APAR for this (APAR: PH31778 WORKFLOW ADVANCED LOGIC VALIDATION ERROR MESSAGES ARE CONFUSING), and adding the ability to customize the error message when a complex validation fails would be extremely useful.
John - Crystal have created a custom class to output a configurable error message and have sold this to a couple of clients. We effectively turn the validation into an operation that displays a message if the condition is met and stops the workflow from proceeding.
This works really well but would not be required if a validation operation could output a custom message instead of what it does today.
I'd suggest that this is a much higher priority for Brewin. We have actually implemented a custom java class to provide the ability to configure meaningful error messages to users and have implemented this at a number of clients. Without this, error messages are extremely confusing.
Thank you again for submitting this RFE!
This request will not be delivered within the release currently under development, but the theme is aligned with our multi-year strategy. IBM is soliciting RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.
This is a big problem for Brewin Dolphin too. The messages are even worse if there are multiple associated objects, as it repeats for as many objects as you have (even when they are not in any error condition). It is pretty much indecipherable. We have had to instead implement a custom java action as an operation that outputs a configurable (via parameter) error message using an Operation with a When clause to detect the error.
A possible solution to this is do NOT repeat the errors for every row associated and provide an option for a user-defined error message to be provided if that validation fails.
Thank you for submitting this RFE!
The IBM team is evaluating this RFE. A decision or request for more information will be provided within 90 days.