Greetings,

The EmailAddress column in the PR_EmployeePIIWrk table is populated with the value from the EmailAddress column in the PR_Employee  table.  There is no checking done to see if the EmailAddress column from PR_Employee is blank or look for a value in another table. For the most part, the PII Wrk tables are simple data dumps of the PII values from the corresponding maintenance table.

Is there a reason why the email address can not be entered in the employee record?

Thank you,

Kent

Greetings,

The EmailAddress column in the PR_EmployeePIIWrk table is populated with the value from the EmailAddress column in the PR_Employee  table.  There is no checking done to see if the EmailAddress column from PR_Employee is blank or look for a value in another table. For the most part, the PII Wrk tables are simple data dumps of the PII values from the corresponding maintenance table.

Is there a reason why the email address can not be entered in the employee record?

Thank you,

Kent

I don't know but where is the address from the PR_EmployeeDocuments stored, then?  The field is blank, in DFDM, yet I clearly see an entry on the screen.

EncryptedVals 

That is stored in the PR_EmployeeDocuments table but is also encrypted and there is no PII Wrk table for this table so the value will not be available to a Crystal Report.

If they can enter the email in Employee Maintenance, it will be available in PR_EmployeePIIWrk,

Thank you,

Kent

Interesting.  OK, I'll pass that along.

Kent,

Big picture, as PII encryption seems to be expanding to more places (ex. GL_Bank...) all tables with encrypted PII should have a PIIWrk table available.

Another thought is the ability to encrypt UDF's, which are a critical part of many of our customer's system configurations / business processes, but may also include PII, risking compliance for data stored in custom fields.

Kevin,

I do expect that we will provide more PII Wrk tables in future releases.  In the currently available releases, the following PII Wrk tables are available:

GL_BankPIIWrk

GL_CheckMicrPIIWrk

PR_EmployeePIIWrk

For UDFs, we did add the ability to mask the data in UDFs for the UI only (not encrypted in the table). The suggestion to fully encrypt UDFs would make a good entry on the Sage 100 Ideas Site if you would like to post it there.

Thank you,
Kent

Thanks Kent (I know about the display masking, which is a nice new feature). 

Idea added.

https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/40988