Hi All, For one of our process we need to save person's firstname

You may want to create an employee database table that you update nightly from LDAP. We use Windows Active Directory for normal security/access in our company for most things but we also have access to an HR generated employee table. Unfortunately, this table generally only provides us with current/active employees. This can be problematic if someone leaves the company or is on leave but has references in Appian that require matching their tasks, data records, etc. with their HR info. Once the user drops off our feed you would have orphaned data in Appian.

Our solution (and one I saw with a non Appian app at a previous employer) was for us to have our own employee table. On a nightly basis we query the HR based table and merge the differences in with our own employee table. New records in HR are inserted, changes in HR are updated in our table. In a not-perfect way, we first set all employee records in our table to terminated, then we insert/update the records with fresh HR data, which effectively makes all active employees active again with current data. When someone leaves the company their data becomes dated in our table but is retain for future use when Appian users need to show names, job titles, etc. for past employees based on their network id. i.e. our employee table will grow over time since we never delete old employees from it, just mark them as inactive and add new employees. Luckily our turnover rate isn't tremendously high...this wouldn't necessarily work well for a million person employer with a high hire/fire/quit rate.

You may want to create an employee database table that you update nightly from LDAP. We use Windows Active Directory for normal security/access in our company for most things but we also have access to an HR generated employee table. Unfortunately, this table generally only provides us with current/active employees. This can be problematic if someone leaves the company or is on leave but has references in Appian that require matching their tasks, data records, etc. with their HR info. Once the user drops off our feed you would have orphaned data in Appian.

Our solution (and one I saw with a non Appian app at a previous employer) was for us to have our own employee table. On a nightly basis we query the HR based table and merge the differences in with our own employee table. New records in HR are inserted, changes in HR are updated in our table. In a not-perfect way, we first set all employee records in our table to terminated, then we insert/update the records with fresh HR data, which effectively makes all active employees active again with current data. When someone leaves the company their data becomes dated in our table but is retain for future use when Appian users need to show names, job titles, etc. for past employees based on their network id. i.e. our employee table will grow over time since we never delete old employees from it, just mark them as inactive and add new employees. Luckily our turnover rate isn't tremendously high...this wouldn't necessarily work well for a million person employer with a high hire/fire/quit rate.