►Q◄ Can I create an "Outgoing email" Notification at runtime

BenHayat

When I look at the steps to create an Email Notification in Aware, it seems like I have to provide a series of information to Aware's configuration to create the structure of that notification and then have a process to call/send that notification. This means I have to know all that during design time

Now my question is, is it possible for us to create a program in Aware that would ask user a series of questions at runtime and then our program would create that notification and then also ability to send it based on user's selection?

There are too many scenarios to cover at design time, so I want to provide user defined email.
Thanks!

kklosson

I think so, in that each parameter can be drawn from an attribute. So the From, To, and message params can be <<attributes>>. You have to store them somewhere and you have to send them to intelligent objects (as far as I know).

BenHayat

kklosson wrote
I think so, in that each parameter can be drawn from an attribute. So the From, To, and message params can be <<attributes>>. You have to store them somewhere and you have to send them to intelligent objects (as far as I know).

BUT, isn't the Notification Object a special form of Object that is created and used by Aware? How do we create this object at runtime and how do designate what type of notification is it.
So far, everything else that I thought about could be done at runtime, except Notification object.

kklosson

I see no reason to create it at runtime. It's basically just a shell that you can do with as you please. So make a notification and simply populate it with attributes as needed. If you want to create the notification at runtime, then you surely already have all of the params needed. Just pass them into the shell. Your process for this could include elaborate logic for the selection or population of the attributes needed.

BenHayat

kklosson wrote
I see no reason to create it at runtime. It's basically just a shell that you can do with as you please. So make a notification and simply populate it with attributes as needed. If you want to create the notification at runtime, then you surely already have all of the params needed. Just pass them into the shell. Your process for this could include elaborate logic for the selection or population of the attributes needed.

I think what you're saying makes sense.

tford

Ben,

KK's description is exactly right.

I use a number of different types of notifications.

1- First one is as simple as a 1 line process that sends a test email to SystemSettings (which I always define as an intelligent in my BSVs). This process allows me to easily test the outgoing email functionality of the BSV as well as the workings of any outgoing email server that the email is being sent through.

Process: SEND OutgoingEmail_Test TO SystemSettings

2- Most of my outgoing notifications do exactly as KK describes and pull selected info from existing BOs to populate the notification attributes before sending.

Tom