If a background task is hooked up to a row action, I would not expect any messages/errors from the LB to show (not even in the bell), correct? And if that is the case, are there other options worth exploring to get some kind of notification to appear?
Not correct. Any background task (job) that produces messages shows them in the bell and reflects the severity of the message(s).
@kendra.b is there a way to make the notification more user friendly when it is coming from a background task? For example for this one we just want the user to know a document successfully printed, we don’t want the logic block info. Is there any way to customize the notification?
Are those 3 Success: ... messages thrown by the logic block or one of it’s children? If so, I would consider wrappering this LB and having the wrapper not adopt all messages. The wrapper would loop the message list and if conditions were satisfactory, create a single message instead.
There is a backlog idea for making the title of the message more user friendly. I will tag this discussion to it.
Here is another scenario where I am not sure about expectations or how to achieve what we want:
Setup:
- Row action on application calls background LB.
- This LB calls another LB that inserts a record into a separate table.
- This table has workflow on it and auto-transitions the record. On this transition, there is a post-run LB that throws messages related to whether a process finishes successfully.
In this use-case, ideally we want the notifications from that LB on the workflow transition to somehow show in the bell icon. Right now, we are not seeing those so wondering if there is a way to make that happen?
As far as I’m aware this isn’t possible today, but there is an idea in the Nextworld backlog that I’m tagging with this discussion.
@ian.p if I make the logic in the workflow a background logic that is called on a post run it still will not have the desired effect? As in, is there any to set the logic up in a certain way that notifications still work?
On workflows, you can use the Action column to send a notification. First create a Notification Definition and then attach it to the associated transition on the Workflow Definition. Would this satisfy the requirement? You’d have less flexilibity on what notification was thrown and you could throw only 1 per transition.
I will attempt that and see if it meets the UX requirements. Thank you!
@ian.p tested this option and it did not seem to work. In lifecycle F282553_implementation–let me know if you think I did something wrong or I should schedule a meeting/write a ticket.