Hi Ajay,

The problem with Rich Text field is that it will include some HTML tags, even when you put some simple text in it. This makes it impossible to include these fields "as-is" in reports where HTML is not rendered like Excel reports, or even in a List Portlet. This has been a significant hurdle for us in our internal usage of PPM, as we can only use Rich Text field but for very large descriptions that will never be direclty included in portlets or reports - and for these large fields, the PPM field limit of 4000 characters can quickly become a problem, especially when one wants to copy/paste some screenshot in the field.

I don't have any solution to either of these problems today, but if we were to address them in a future release we could consider the following options:

1) Use an HTML parser to remove HTML tags and extract "pure" text content of Rich Text field. This text-only value would be saved in the "VISIBLE_PARAMETERX" column, while full HTML would be saved in the PARAMETERX . This way, you would leverage the text-ony version for reports and lists where rendering HTML is not an option.

2) Introduce a capability to remove 4000 chars limits for some of the request type parameters. We would likley add like 10 extra PARAMETERX fields per batch of type CLOB - but this would have massive impact on the whole demand management module, which we try to keep as stable as possible. Definitely not a change we'd want to rush in.

One example of where we successfully use Rich Text field is to store descriptions of Requests/Features in PPM that we later synchronize to Octane for execution - both tools use HTML for the description field and so far it's been working smoothly, synching in both directions.

Thank you Etienne, we will then refrain from using it as we will need to report on these fields via dashboards, portlets; but it would have been very handy to explore such features in the tool, makes it more user-friendly. 

Hi Ajay,

Quick update: PPM 24.1 (to be released later in January) will include the point 1) that I mentioned above, i.e. saving no-tags text content of Rich Text fields in the VISIBLE_PARAMETER column .

Hi Ajay,

Quick update again: PPM 24.2 (to be released later in April) will include the point 2), i.e. unlimited field size with CLOB storage of rich text html content. Finally it'll be possible to paste big screenshots and images direclty in PPM rich text fields!