Outgoing Email Account Object

kklosson

I am about to implement this but first, one question for the team. Obviously, we need to relate the email account object to an Account (in multi-tenant app). I sure don't want to make the Account "Owned By" the Email Account Object as that would delete the account when the email account object is deleted. Next best, I suppose, is to make it a peer object. Now when sending anything that will use the account, the process would look like this:

FIND EmailAccount where EmailAccount.Account = Account (Account is in context somehow)
Send Notification USING Account

Is that how everybody sees it?

weblike

kklosson wrote
I am about to implement this but first, one question for the team. Obviously, we need to relate the email account object to an Account (in multi-tenant app). I sure don't want to make the Account "Owned By" the Email Account Object as that would delete the account when the email account object is deleted. Next best, I suppose, is to make it a peer object. Now when sending anything that will use the account, the process would look like this:

FIND EmailAccount where EmailAccount.Account = Account (Account is in context somehow)
Send Notification USING Account

Is that how everybody sees it?

Hi Kingsley,
Why is the Account owned by email account? Is not supposed to be in other way? A person owns an email account..How that's i see it.

I'm using already the function and I have attached a sample bsv.

SMTP.bsv.zip

41.91kB

Login as admin
Create a user with "Users" role, than an email account for that user.
Login as that user
Create a customer
Start the process "SendEmail"

Of course it could be done nicer, but this is the fast-version(only functionality 🙂 ....

cheers,

kklosson

So you have it that the user (or account) owns the outgoing email account, right?

weblike

kklosson wrote
So you have it that the user (or account) owns the outgoing email account, right?

Yes, that's how i did it in sample bsv, but with only peer also i think should work.I don't see why should not work...

kklosson

Thanks. I'm glad I asked.

BenHayat

I'll be doing it soon as a 1-1 relationship with tenant being the master and Email account as subordinate, like George has done.

kklosson

Well here is some code that does not work. Actually, it works, but it is sending using the settings in SystemsSettings. The email account for the "Organization" is a Gmail account and in system settings, it is a commercial smtp for which I can see the logs. It's definitely going through the commercial smtp in SystemSettings. My Outgoing Email Account is called OrganizationEmailAccount which is owned by Organization. One OrganizationEmailAccount record exists.

If EXISTS OrganizationEmailAccount WHERE (OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization) Then
DISPLAY MESSAGE 'SMTP Found.'
FIND OrganizationEmailAccount WHERE OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization
SEND WelcomeCandidate TO Candidate USING OrganizationEmailAccount

The second issue is that if I change it to:
If NOT(EXISTS OrganizationEmailAccount WHERE (OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization) Then ...

I get the exact same result and the DISPLAY MESSAGE is never presented.

So the problem is two-fold: my IF EXISTS statement seems inert and my SEND USING command seems to be ignoring the USING attribute of the command. I suspect that the SEND USING is ignoring the USING because no such account is in context, Goes back to why is the EXISTS statement being totally disregarded here and the FIND must not be returning anything maybe?

Somebody throw me a line here.

BenHayat

kklosson wrote
Well here is some code that does not work. Actually, it works, but it is sending using the settings in SystemsSettings. The email account for the "Organization" is a Gmail account and in system settings, it is a commercial smtp for which I can see the logs. It's definitely going through the commercial smtp in SystemSettings. My Outgoing Email Account is called OrganizationEmailAccount which is owned by Organization. One OrganizationEmailAccount record exists.

If EXISTS OrganizationEmailAccount WHERE (OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization) Then
DISPLAY MESSAGE 'SMTP Found.'
FIND OrganizationEmailAccount WHERE OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization
SEND WelcomeCandidate TO Candidate USING OrganizationEmailAccount

The second issue is that if I change it to:
If NOT(EXISTS OrganizationEmailAccount WHERE (OrganizationEmailAccount.Organization=LoggedInInvestigator.Organization) Then ...

I get the exact same result and the DISPLAY MESSAGE is never presented.

So the problem is two-fold: my IF EXISTS statement seems inert and my SEND USING command seems to be ignoring the USING attribute of the command. I suspect that the SEND USING is ignoring the USING because no such account is in context, Goes back to why is the EXISTS statement being totally disregarded here and the FIND must not be returning anything maybe?

Somebody throw me a line here.

Has this been reported to Support?

kklosson

No. I'm not sure of the error, but I now have two instances where DISPLAY MESSAGE does not display when placed somewhere in the middle of a process stream. Seems to fire when it is the first thing. Still studying it all.

BenHayat

kklosson wrote
No. I'm not sure of the error, but I now have two instances where DISPLAY MESSAGE does not display when placed somewhere in the middle of a process stream. Seems to fire when it is the first thing. Still studying it all.

Thanks for the progress note...

kklosson

The error I was having is resolved with thanks to Ben Hayat. It turns out I had a DISPLAY MESSAGE ASYNC in the middle of my process. I have known that command to have some issues but in my case, it really screwed the processes up. Using that command only at the butt end of a process is probably a good practice.

BenHayat

kklosson wrote
The error I was having is resolved with thanks to Ben Hayat. It turns out I had a DISPLAY MESSAGE ASYNC in the middle of my process. I have known that command to have some issues but in my case, it really screwed the processes up. Using that command only at the butt end of a process is probably a good practice.

Glad to see you resolved it.

kklosson

Just for a recap, I have an OutgoingEmailAccount object owned by the Organization object, no multiple allowed. In addition to the Organization attribute/relationship, I added a disable (Yes/No) attribute. In the process for sending a notification, I first check to see if an OutgoingEmailAccount object exists and if it does, I use the SEND USING command. Otherwise, I just use SEND in an ELSE construct. I threw in a DISPLAY MESSAGE command for testing so the processes would tell me which server it was using and I verified it by looking at email server logs. I had considered another approach where I would run a process right after deployment that would populate an OutgoingEmailAccount object for each Organization and strictly use it until the customer changed the settings but this way, I will have my customers just create their own and they can use the disable feature as needed when they configure and test (I also created a Test Server process). There are many ways to skin this cat. This is simply what I did. It would have been painless except for the ASYNC thing which had me doubting everything I thought I knew.