How to fix data loss issues with the use of RTE (Rich Text Editor)

User Experience Knowledge Share
,
1

Hi,

Customer reported to me an issue with RTE (Rich Text Editor) when row reordering. In this post, I will share how to fix it.

1. Issue

  1. On a section rule, place a Table and configure Rich Text Editor control for your preferred column.

Table.png
Table.png1522×461 37.6 KB

  1. Enable row editing and make rows always editable.

Rows always editable.png
Rows always editable.png806×259 15.9 KB

  1. Populate data on RTE field from screen.

Order screen.png
Order screen.png1521×831 73.3 KB

  1. Drag and drop any rows for reordering. When you drop it, data gets cleared.

Data Flush.png
Data Flush.png1459×537 37.9 KB

Actually data still remains on clipboard - if you refresh a section, data will appear. However, end users are confused with data loss for sure.

2. Resolution

Switch RTE type from defaulted “Classic” to “Lightweight”, shown as below.

Rich Text Editor.png
Rich Text Editor.png806×554 35.8 KB

Now let’s test it. Drag and drop won’t clear data any more and it stays on field properly.

Problem fixed.png
Problem fixed.png1459×535 63.6 KB

  • Classic Rich Text Editor: This is the default RTE type when you use RTE control. Classic RTE is rendered in an iframe and by default supports both the CKEditor plugins and the Pega RTE plugins. Classic RTE is heavy-weighted because it uses a separate iframe within the parent window to render.

  • Lightweight Rich Text Editor: This is also known as the Inline Editor, and it can help to control memory leaks because the RTE is rendered in

    rather than