Extended Field Label Not Saving in Local/Global Configuration

Products

• CA Service Management - Asset Portfolio Management

Issue/Introduction

Client has extended the payment object in a Global Configuration and then created a Local Configuration.

Requirement is to be able to rename the extension label name which has the format (ClassName) Object/Attribute to a Shorter Name on the Payment header row. The extended field labels and order in the Global or Location Configurations will not save.

Environment

IT Asset Manager 17.3 and 17.4

Cause

Product design limitation

Resolution

Client created a List extension based on new object on Legal Document object and using the same extension on the Payment object.

Their requirement is to be able to rename the extension label name which has the format (ClassName) Object/Attribute to a Shorter Name on the Payment header row.

This is however restricted by design.

The reason - the long name of the attribute gives a fair understanding of which class the attribute belongs to when it is being used as a foreign key on a different object.