Hi, we are making use of customField properties for user profiles. We are storin

GouthamKrishna over 10 years ago

Hi, we are making use of customField properties for user profiles. We are storing employee id in customField1 using 'update profile advanced' smart service and our logic to assign tasks is based on this field. However, we observed that customFiled properties are being erased whenever a user updates his/her profiles (for example, changing mail id). When this happens it means that the particular user can’t be assigned to his tasks because the expression to get task assignees won’t return that user object. Any resolutions?...

Discussion posts and replies are publicly visible

Top Replies

Eduardo Fuentes over 9 years ago +1
Appian Employee

Customizing the People tab is not a Cloud Compliant request. You can still use the custom fields but they will have to be updated via Process Model using the custom plug-in called "Update User Profile…

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

You will have to expose those fields in the user interface under the People tab so they don't get blanked out when there's an update.

This is achieved by editing <APPIAN_HOME>/runtime_ear|ear/suite.ear/web.war/personalization/userdetail.jsp. You will expose these fields in the same manner as the normal fields. The custom fields are named field01 - field10. You should use this for the property and value tags of your input.

Example:

<asi:input label="Site Location" type="text" property="field03" disabled="${!useraction_2}" value="${result.field03}" useTextBundle="false"/>

The most important part is the "value" attribute since this will guarantee the fields are re-saved when the profile is updated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

You will have to expose those fields in the user interface under the People tab so they don't get blanked out when there's an update.

This is achieved by editing <APPIAN_HOME>/runtime_ear|ear/suite.ear/web.war/personalization/userdetail.jsp. You will expose these fields in the same manner as the normal fields. The custom fields are named field01 - field10. You should use this for the property and value tags of your input.

Example:

<asi:input label="Site Location" type="text" property="field03" disabled="${!useraction_2}" value="${result.field03}" useTextBundle="false"/>

The most important part is the "value" attribute since this will guarantee the fields are re-saved when the profile is updated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data