pepdwill Honored Contributor.
Honored Contributor.
66 views

Enhancement Request - Make Table Components more usable/flexible

The following flag determines the style of table component used in PPM.  It is a global setting.

 

TABLE_COMP_USE_LEGACY

 

Depending on the request type and specific usage - there are times when the legacy Table Component style makes more sense (i.e., to leverage the form layout features).

 

It would be great if this were changed from being a global setting to something that can be variable; either set at the request level, or set within each TC validation.

 

0 Likes
3 Replies
mike_se Contributor.
Contributor.

Re: Enhancement Request - Make Table Components more usable/flexible

Hi,

 

Could you give the example that prompted you to ask for the feature?

 

Helps to put a real world spin on it when R&D decides if it is a valid Enhancement Requeset.

 

Thanks,

Mike

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Enhancement Request - Make Table Components more usable/flexible

Hi,

 

 

I second Mike's request. The main reason why we introduced the parameter when the new Table Component was added to the product was to make sure that users had a short-term fallback solution if their customizations were not compatible with the new Table Component; We didn't thought that the old Table Component could be preferable to the new one in any aspect.

 

So any detailed description about what you're missing from the old TC is welcomed.

 

FYI, the old TC is still there for customizations backward compatibility reasons, but it will be removed from the application at some point in the future (no idea when exactly though). So obviously I can't say we have any plan to implement this ER. However, input to improve the new Table Component is valuable.

 

Thanks,

Etienne.

0 Likes
pepdwill Honored Contributor.
Honored Contributor.

Re: Enhancement Request - Make Table Components more usable/flexible

One example would be whenever there are long text fields in the TC, editing the text via the inline format can get ugly amd especially difficult for users to navigate.  Also, if there are many fields defined in the TC, being able to arrange those fields and display them logically on a separate form is usually a better option.

 

For this reason I would vote for not removing the legacy style but to expand on it... it would be a useful feature - but only if it weren't a global setting.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.