Emojis Able To Be Entered In View Names But Causing Issues When Edited/Removed
search cancel

Emojis Able To Be Entered In View Names But Causing Issues When Edited/Removed

book

Article ID: 375797

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The following use cases are causing issues/errors.

Use Case 1

When attempting to remove emojis, it is giving an error.

The following Oracle query is used to check views containing emojis:

SELECT * FROM odf_ui_views
WHERE REGEXP_LIKE(name, UNISTR('[\FFFF-\DBFF\DFFF]'))
ORDER BY created_date DESC;

When trying to remove the emojis, the UI shows error that duplicate cannot be created because the view already exists.

Use Case 2
When removing emoji from the beginning, it errors out when trying to create a new view.

Use Case 3

When searching for certain emojis from Administration > VIEWS Workspace, it does not filter for certain emojis

Use Case 4

When putting text between < and > , it displays non-readable encoded form.

 

Resolution

 Emojis are not supported in any Clarity field.

The text within the < > in data entry fields are not allowed in order to prevent XSS issues.

The emojis will need to be removed via the UI.

Starting In version 16.2.2, Modern > Administration > Views can be accessed and remove emojis in bulk, should any exist.