Auto-populate an email distribution list

[alekhyavadnala]

How to fetch the auto populate an email distribution list

[rushikeshvartak]

can you elaborate requirements 

[alekhyavadnala]

We need a group to be automatically populated. The group needs to be populated with people with an active status. People who’s employee type is payroll and the person manages a payroll employee or a contingent worker. People who manage a volunteer or offsite person should NOT be included.

[This post has been edited by a Moderator to remove sensitive information.]

[rushikeshvartak]

You can create user update rule and assign the group https://docs.saviyntcloud.com/bundle/EIC-Admin-v24x/page/Content/Chapter05-Policies/Creating-User-Up...

[stalluri]

@alekhyavadnala 

You can use the user update rule and technical rules and assign the group and also remove the group if condition fail.

[alekhyavadnala]

Thanks Sam and Rushi for sharing your inputs, however I am not finding the way out to accommodate below query in either Technical rule or user update rule. Can you please guide

select username , u.userkey from users u where employeetype ='Payroll' and statuskey =1
and u.userkey in ( select m.manager from users m where m.employeetype in( 'Payroll' ,'Contractor') andm.employeetype not in ('Volunteer','Offsite') and m.manager = u.userkey and m.statuskey =1)

Best Regards,
Alekhya

[rushikeshvartak]

a.employeeType = 'Payroll' and a.statuskey =1 and a.id in ( select m.manager from Users m where m.employeeType in ( 'Payroll' ,'Contractor') and m.employeeType not in ('Volunteer','Offsite') and m.manager = a.id and m.statuskey =1)

[stalluri]

@alekhyavadnala 
You can use the below query shared by Rushikesh.

When referring Advance config. users table is exposed as users a

Condition
Advanced Config ON
Advanced Query	Select Advanced Config as ON to write a complex query as the condition for User Update Rule to be triggered. The user attributes specified in the Advanced Config query are case-sensitive. The supported user attributes to be used in the Advanced Config are as follows: username,firstname,preferedFirstName,lastname,middlename,street,city,comments,statuskey,startdate,enddate,manager,password,location,jobCode,jobDescription,employeeType, systemUserName,departmentNumber,title,state,companyname,costcenter,departmentname,employeeclass,entity,jobcodedesc,locationdesc,locationnumber,siteid,orgunitid,region,regioncode, owner,employeeid,lastsyncdate,createdate,email,phonenumber,job_function,country,displayname,locale,customproperty1-65 If you are using the 'isupdated' condition in the Advanced Config query, notice the syntax used before and after the '<attributevalue>isupdated' condition. You must use have a prefix ## before <attributevalue>isupdated and suffix ## characters after the <attributevalue>isupdated for the rule to correctly pickup the isupdated condition. For example, ##a.customproperty5 isupdated##. Example query: a.firstname like '%Andrew%' AND (a.customproperty1 is null OR a.customproperty1 in ('emp', 'emp1')) AND (##a.customproperty5 isupdated##)