ESS Address Change notification to HR on Windows platform

You can easily add a trigger onto the table and then write a report against it. Smart Notes or whatever.

CREATE TRIGGER [xxAuditUpdateEMPLOYEE] ON [dbo].[EMPLOYEE]
FOR UPDATE
AS
BEGIN
SET NOCOUNT ON

INSERT INTO XXEMPADDR
(
R_ACTION
,COMPANY
,EMPLOYEE
,FIRST_NAME
,LAST_NAME
,ADDR1
,ADDR2
,CITY
,STATE
,ZIP
,MODIFIED_DATE
,MODIFIED_TIME
)
SELECT
delta.R_ACTION
,delta.COMPANY
,delta.EMPLOYEE
,delta.FIRST_NAME
,delta.LAST_NAME
,delta.ADDR1
,delta.ADDR2
,delta.CITY
,delta.STATE
,delta.ZIP
,getdate()
,dbo.XX_LAWSON_TIME(getdate())
FROM
(
SELECT 'AFTER' AS R_ACTION, i.* FROM inserted i
UNION ALL
SELECT 'BEFORE' AS R_ACTION, d.* FROM deleted d
) delta
, inserted i
, deleted d
WHERE i.COMPANY = d.COMPANY
AND i.EMPLOYEE = d.EMPLOYEE
AND i.COMPANY = delta.COMPANY
AND i.EMPLOYEE = delta.EMPLOYEE
AND (i.ADDR1 <> d.ADDR1 OR i.ADDR2 <> d.ADDR2 OR i.CITY <> d.CITY OR i.ZIP <> d.ZIP OR i.STATE <> d.STATE)


SET NOCOUNT OFF

If the employee changing their address creates a record in pa52, you could create a processflow that will send the email, based on that action. I am not sure if the ESS functions create a pa52 record or not.

It does a direct call to HR11 to update. I am having a similair issue with custom code I am developing for a Windows client, apparently the EMAIL object doesn't work seamlessly in Windows.

You could create a email notification processflow and trigger it in empaddress. When you customize ESS though you have to track the changes because patches can wipe them out, it is not as simple as upgrades for 4GL. The problem with Database triggers is they have to be reapplied during upgrades.

If I find a better resolution for my issue I will pass it on.

I did a bunch of work on this a few years ago, and I remember the problem is due to browser security (i.e., you don't want a rogue website to start sending emails from your browser via JavaScript). So, you can't rely on the user interaction that is required when using the email object from JavaScript.

Naturally, I can't remember who I did this for, nor what the solution was...

I do remember that the solution was to send the email from the server; I don't remember if I used an HR11 user exit or had a server-side script that was called from the ESS page...