Hello Archer Gurus,
We have run across an issue that it seems like has been brought up in a number of other discussion posts, but I can't quite find the answer that I'm looking for.
Business Case: I'd like to always display an additional attribute about my users after their name, I don't want my end users to have to hover or click to open a user profile in order to get this information.
Attempted Technical Solution: We have currently appended all our users' emails to the middle name field enclosed in parenthesis in an attempt to display this information to our end users at all times.
Problem: When a user logs in via SSO (SAML - Okta), SSO wipes out the email address from the Middle Name field on the user record. A quick solution to this is turning off the option to update the user's profile when they log in via SSO, however then we put ourselves into the situation of having out of date user profiles, last names, etc. when those do change.
I'm aware of the "Attribute Display" functionality within the ACP, but my impression was that it is only used for displaying an attribute upon hover over within a user lookup (record perm or otherwise). Someone please correct me if that's a false assumption.
Has anyone run into this same problem, or have any ideas for how to solve the problem so that we can still have profile updates enabled via SSO, but also keep an email displayed after our users' names?
When doing Self-Provisioning, is it possible to provision email to middle name?
2 other options would be to:
1. Run SQL script more frequently to fill in middle name or per some trigger.
2. Use Custom Object to get email of a user and show near by.
Something similar was provided by Archer Scripts folks, I believe in Exchange.
@DavidPetty - using a contacts xref is certainly an option, but I'd really love to be able to use an actual Record Permission field to accomplish this.
@Ilya_Khen - I don't believe that's an option in the ACP for SAML SSO. I appreciate the other two ideas as well, I was really trying to see if anyone has figured out a way to do this without custom coding or scripts.
@DavidPetty True. I guess what I'm hung up on is trying to get it all in one field, rather than two different fields and having to couple a record perm field with a calc xref every time we deploy any record perm field.
Problem with calculated CR may also come when RP has 2-3 names in there instead of 1 in case you need to return back to another text field for some manipulations. Will be fine in case of just displaying.
I think this is probably the right direction long term David. I haven't heard back from our internal SSO contact but I think this is the direction we'll likely go. Short-term we've turned off update profiles in SSO.