I created a post-processing BPM directive which is intended to produce a warning message on login in MES and it is acting like the setting is “error”. I want to notify the person logging in that they forgot to logout the previous day if when they first login they are still active and the clockin date is yesterday. The message encourages them to inform mgmt to correct time and to clockout. By setting it as “informational” or “warning” it SHOULD process forward and open the MES buttons (Clock Out being the most important) but it doesn’t and nothing opens up just as you would expect with a “error” setting. Is this a bug, “as intended” or am I spinning around in the ozone? Any help, hints, tips or suggestions is much appreciated. I’m sure I’m not the first person to try to address issues with failure to clock out (lol).
The message box will not matter what setting you use, (error or information). That setting is only for how the box looks. It shouldn’t stop the processing. Only the Exception widget should stop the processing.
An if it is a Post Process BPM, all the processing has already happened.
My experience has been that if you set that to “error” it will stop further processing and if set to warning or informational it will pop the message and continue processing. Mind you that’s not in MES. And if it shouldn’t stop processing then I should be seeing the buttons activate as I do when the BPM isn’t triggered which isn’t the case.
True but then I would expect to see the buttons open up for use but nothing happens - the buttons remain grayed out. It’s a pretty simple BPM to try to duplicate.
That’s an exception widget, not a message widget.
As @Banderson said, the Exception widget will always throw an exception.
Try using a “Show Message” widget.
Ok, nominate me for the next Darwin Award prize. Yeah, that’s the fix. Knew it had to be “user malfunction”. THANKS!