ION Notification node / ION Pulse Notification

I’ve been playing around with some IPAs to discover their functionality and I’m trying out the ION Notification node.

I’ve successfully created a notification according to the log, but nothing seems to come through anywhere that I can find. Is there additional setup required to use this node?

This is what my log is showing in the IPA:
Activity name:IONNotification3600 id:1 started @ 04/06/2023 02:22:06.541 PM
ION Notification IONNotification3600: Executing ION Notification activity node
ION Notification has been sent Successfully
IONNotification3600_errorCode = 0
IONNotification3600_informationCode = 0
IONNotification3600_returnMessage = ION Notification has been sent Successfully
IONNotification3600_outputData =
Activity name:IONNotification3600 id:1 completed @ 04/06/2023 02:22:06.560 PM

Before asking here, I tried setting up a few things:

I added the user I’m testing with to Process Server Administrator -> Configuration -> User Configuration -> users. This user has received no notifications.
I added a Pulse Notification receiver in Process Server Administrator -> Administration -> Channels Administrator -> ION Channels. This receiver is active and scanning every minute but has never received a message.

I’ve looked in ION Desk and have seen no documents come through OneView.

I can’t seem to find any real documentation on using this node other than very basic descriptions of what it is.

Is anyone using this successfully or can anyone point me to any setup documentation?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

Rebecca Derr

Just an update, I did find out what the issue was. As it turns out these notifications go to users assigned to tasks that are set up in Process Server Administrator -> Configuration -> User Configuration.
So I ended up creating a 'Test Task' and assigning my user to it. Then I set the IPA's ION Notification node recipient to 'Test Task'.

I did not need to touch the channels administrator as I had posted about initially.

This sent a notification to me in Infor. To get an email sent to me I had to take one more step: ION Desk->Configuration->ION Service->Properties->Activities Engine-> Check box 'Send Email'

These processes can be seen within ION Desk -> Monitors & Workflows -> Activities. If, like me, you weren't actually sending any alerts or notifications because your task/user isn't set up correctly, you won't see any activities here even though your IPA log shows 'ION Notification has been sent Successfully"

[edit] Turns out I didn't need a task or a user in PfiUserProfile. I tried without either and just sending the notification to my user id and it worked. The user id I was testing with before was our service account. Going to look at the diffs between my user and it now.

All comments

Rebecca Derr

I did not need to touch the channels administrator as I had posted about initially.

This sent a notification to me in Infor. To get an email sent to me I had to take one more step: ION Desk->Configuration->ION Service->Properties->Activities Engine-> Check box 'Send Email'

jhedahl

What you are talking about is called the ION common inbox, and Infor Development does not support the interchangeability between Landmark in-basket and ION Inbox. You need to either disable ION Inbox and only use Landmark in-basket, or fully enable ION Inbox and not use Landmark in-basket. You can do a partial enable of ION Inbox where tasks will queue up, but clicking on those tasks won't sync back to Landmark. This is described in the below link under the "BOTH" bullet. Unfortunately, using BOTH causes confusion because people now have two places to respond to the same task, but only one actually works.

Here is a link that describes the common inbox.
https://docs.infor.com/lmrk/2023.x/en-us/lmrkolh/default.html?helpcontent=lpaag_cl/sob1549860617280.html

Let me know if you have a different experience. It would be great for people to use either place to respond to tasks!

Rebecca Derr

The notifications I'm creating aren't real tasks in that they don't really need to sync back to landmark, they are mostly stuff like 'PO xxx was short shipped'.

However, the documentation you shared lets me know we might see some issues when we move to v2 portal if we want to show notifications/tasks/alerts in the common inbox and have them be functional, not to mention the confusion that can be cased with the 'BOTH' option.

Thank you!

Copyright © 2025 Infor. All rights reserved.