Hi team We've just set up an application that uses the Send E-Mail Smart Service. Our Health Check Report has this to say: "SAL Approve Installation (0002edb5-ade8-8000-43ed-7f0000014e7a) Node: ""Send To user"" references a smart service that is no longer recommended for use (Send E-Mail). Please remap this node in the process model to use the latest version." I can find nothing in Appian documentation saying Send E-Mail is no longer recommended for use I can find no details in Appian documentation of any Smart Service that might replace this I can't seem to find a thread in this Community that addresses this issue Can anyone assist me to resolve this?Thanks and blessings Stephen

Question

Health Check Report - Smart Service no longer recommended for use (Send E-Mail)

Forum|Forum|1 year ago
May 29, 2025
4 replies
0 views

Hi team

We've just set up an application that uses the Send E-Mail Smart Service.

Our Health Check Report has this to say:

"SAL Approve Installation (0002edb5-ade8-8000-43ed-7f0000014e7a)
Node: ""Send To user"" references a smart service that is no longer recommended for use (Send E-Mail).

Please remap this node in the process model to use the latest version."

I can find nothing in Appian documentation saying Send E-Mail is no longer recommended for use
I can find no details in Appian documentation of any Smart Service that might replace this
I can't seem to find a thread in this Community that addresses this issue

Can anyone assist me to resolve this?
Thanks and blessings

Stephen

mathieud0001

I don't remember Appian pushing any updates to that node. I would personally log a ticket with Appian Support.

Otherwise, if you want to try to resolve it, it's just a question of replacing the old node with a new version of the node by dragging it in the process modeler.

mikes0011

Brainy

I don't remember Appian pushing any updates to that node.

It's been several years but didn't the addition of the "sender display name" (etc) necessitate an iteration of the node version? I don't scrutinize my health check results closely enough to notice whether older copies of this node are now causing an alert like this, but I guess it would be possible.