User Interface in BPM - Message Type Info

Mike Arceri · 2025-07-02T17:33:01+00:00

There was an error rendering this rich post.

I am able to create tasks in a BPM using the user interface, but I am not able to show a basic ui form to display a message. The Message Type of Info seems to be the way to do it, but no form is displayed. The BPM is being called from an entity rule. Thanks.

Find more posts tagged with

BPM

AppWorks Platform

Comments

AppWorks Tips

@Mike Arceri Read about the concept you want in this blog post:

https://appworks-tips.com/2020/09/18/066_the_trick_of_using_an_entity_task_layout_in_your_bpm/

Don't use a "User interface", but an entity layout.
Also, don't forget to subscribe to the monthly newsletter to inform yourself about the OPA platform! 😉

//Antal

Mike Arceri

Thanks, but this is not what I am trying to do. An entity layout wired up to a new task is straightforward. Even if I do an entity layout and form (Info option), I still only have the entity fields to display, and I can do that on the already existing layout the user is looking at. The xform at least has an assignable field that can be set from the BPM.

I want to simply tell the user they are using an invalid account number. The message notification "works" but instead of showing the xform, it throws a message into the inbox, and it will open the xform from there. Obviously this is not interactive. I don't think AppWorks has the necessary plumbing to show a pop up form.

I have tried the show warning or information in a rule, but this bpm is being called from a new UI rule, which has proven to be difficult in that it doesn't perform the multiple actions in any particular order, and a functional rule (sequential) only allows error messages, which actually cancel the BPM. . .

I am resorting to using an entity field to show a message, which is not great but is in the category of the possible.

AppWorks Tips

Ok, now I get the question! Sounds like you want to have this approach:

The entity has an account number field in a normal entity form/layout
When an invalid number is filled in (that's a business Rule!), you want an info message triggered via a BPM (and not via the Rule!)

That would indeed be a AppUI rule with multiple actions sequentially executed in this order with a global rule condition of "true" or "1==1":

Action 1: Start a BPM (short-lived because of one transaction!) when your account number is invalid; The BPM does in updateEntity request with the ItemId and a trigger-flag kind of property
Action 2: Show the information message, checking the trigger-flag-property you set in the BPM.

The trick here is the short-lived BPM updating the entity for your follow-up action. The BPM can just complete with any user task or abort.

Hope that helps, //Antal