nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reviewer Display Name

bturns

TS 6.7.2
Solaris 10

Hi,

I am using the following inline command in a workflow custom_instantiation.cfg

<inline command="Datasource:executeComponent:LiveSite Reviewers"/>

This is returning a drop down list of users. I believe this Datasource is a out-of -the-box component with TeamSite.

The drop down list (datasource) displays the "Name" field of all TS Users that are in the 'Reviewer' role for a particular branch.

The problem is that the name field is being pulled from the /etc/passwd file. Our Sysadmins typically do not put very informative information in the /etc/passwd file. Does anyone know how to customize teamsite so that it doesn't pull from the /etc/passwd to populate the "name' field for a given TeamSite user?

Thanks,

Brian

Find more posts tagged with

Comments

Adam Stoller

TS 6.7.2
Solaris 10

Hi,

I am using the following inline command in a workflow custom_instantiation.cfg

<inline command="Datasource:executeComponent:LiveSite Reviewers"/>

This is returning a drop down list of users. I believe this Datasource is a out-of -the-box component with TeamSite.

The drop down list (datasource) displays the "Name" field of all TS Users that are in the 'Reviewer' role for a particular branch.

The problem is that the name field is being pulled from the /etc/passwd file. Our Sysadmins typically do not put very informative information in the /etc/passwd file. Does anyone know how to customize teamsite so that it doesn't pull from the /etc/passwd to populate the "name' field for a given TeamSite user?

Thanks,

Brian

If you were going to customize the datastource to get the names from somewhere other than /etc/passwd - where would you be getting them from?

TeamSite should get the information from /etc/passwd or, if configured for it, LDAP. Assuming you would be using one of those two locations the choices are:

If you get one of those two things done, you should not need to muck around with the code for the datasource.

nipper

Your other option is to replace the datasource with an inline callout. I do that and choose from a DCR.

sample.csv

bturns

So, I'm curious if you know why there is a command line tool:

wzsdap1:/apps/iw-home/bin> ./iwuseradm set-display-name q693574 "Brian Turner"
ERROR:02445: Attribute is not modifiable
wzsdap1:/apps/iw-home/bin>

It seems like this attribute should be modifiable and shouldn't require pulling from LDAP or /etc/passwd.

Any thoughts?

bturns

Also, it sounds like you're saying the display name has to pull from LDAP or unix. Is this the case?

Brian

nipper

Also, it sounds like you're saying the display name has to pull from LDAP or unix. Is this the case?

Brian

If you are using a datasource, yes. If you have your own XML file and create the menu yourself, no.

Adam Stoller

So, I'm curious if you know why there is a command line tool:

wzsdap1:/apps/iw-home/bin> ./iwuseradm set-display-name q693574 "Brian Turner"
ERROR:02445: Attribute is not modifiable
wzsdap1:/apps/iw-home/bin>

It seems like this attribute should be modifiable and shouldn't require pulling from LDAP or /etc/passwd.

Any thoughts?

I believe that when they first introduce the concept of using "real names" in the UI, they considered allowing the "display-name" to be set-able, but then they switched to using the OS libraries to retrieve the display-name and just never removed the option from the CLT.

I think there may still be some cases where you can manually set the display name, but I cannot remember what they might be and its generally the wrong way to go.