and more in a single search tool across platforms. Read the announcement here. |
10/18/2023 04:42 AM
We have configured 2 dynamic attributes configured on User Update form. Attributes are configured in Admin > Global Configuration > Identity Lifecycle.
Both attributes will be of "Single Select from SQL Query" type.
Issue - When we initially open the user update form, no value is populated in the 2nd attribute. Also, when a different user is selected in the 1st attribute, value does not get updated in 2nd attribute.
FYI:
1st Attribute Configuration:
Attribute Name | updateCWNewManager |
Request Type | User |
Attribute Label | New Manager |
Attribute Group | 2-Update Contingent Worker |
Order Index | 10 |
Attribute Type | Single Select from SQL Query |
Values | select CASE WHEN ISNULL(u.DEPARTMENTNAME) THEN concat(u.lastname,", ",u.firstname," (",u.username,")") ELSE concat(u.lastname,", ",u.firstname," (",u.username,")"," - ",u.DEPARTMENTNAME) END AS ID from users u where u.statuskey=1 and u.employeetype='Employee' |
Default Values | select CASE WHEN ISNULL(u.DEPARTMENTNAME) THEN concat(u.lastname,", ",u.firstname," (",u.username,")") ELSE concat(u.lastname,", ",u.firstname," (",u.username,")"," - ",u.DEPARTMENTNAME) END AS ID from users u where u.userkey=${requestor} |
What action to perform when Parent attribute changes? | Refresh |
2nd Attribute Configuration:
Attribute Name | updateCWNewManagerKey |
Request Type | User |
Attribute Label | Manager Key (For Admin Purpose) |
Attribute Group | 2-Update Contingent Worker |
Order Index | 12 |
Attribute Type | Single Select from SQL Query |
Default Values | select u.userkey as ID from users u where u.username=(select trim(SUBSTRING_INDEX(SUBSTRING_INDEX(${updateCWNewManager},'(',-1),')',1))) |
User Column | manager |
Parent Attribute | updateCWNewManager |
What action to perform when Parent attribute changes? | Mapping |
Requesting your inputs on how to fix this issue.
Thanks,
Kunal
10/18/2023 04:57 AM
@kunal_saxena , what is the behavior if you use a customproperty instead of manager as the user column. If its same then "if the value to be populated in the dynamic attribute and the value stored in the respective user column is not same then no value is show in the dynamic attribute".
10/18/2023 06:02 AM
Hi @nimitdave , Thanks for the quick response.
I set the User Column for 2nd attribute to customproperty15. Then, the attribute started working as expected, i.e., value is populated when we initially access the form. Also, when a different user is selected in the 1st attribute, the corresponding userkey gets updated in the 2nd attribute.
However, we want to update the manager using this form. Therefore, setting the User Column to a custom property would not meet the requirements.
10/18/2023 07:57 AM
@kunal_saxena , ok so now you try with user column as owner and have the query in 2nd attribute to fetch the username of user selected in 1st attribute. Setting an owner will also update manager of the user.
10/19/2023 12:34 AM
@nimitdave , I tried the steps suggested by you. Still the issue persists. On form load, the value in 2nd attribute is not getting populated. Also, changing the value in 1st attribute does not update the value in 2nd.