How to remove "Error Alert" from Workspace for Mandatory fields in workspace

[prasannakumard]

Hi Team,

We are working on workspace and created ui action and make some fields are mandatory. Everything is working fine. But, the difference between native view alert and workspace view alert:

Native view alert:

In Workspace view the alert showing like this: Here, we need to remove "Error Alert" from workspace. Please suggest me where I need to change this particular area. 

Or please let me know, is there any possibility to remove from UI action workspace view script.

Thanks & Regards,

Prasanna Kumar

@kavish @Ankur Bawiskar @swathisarang98 @Mark Roethof @Chuck Tomasi 

[Dr Atul G- LNG]

Why you want to remove ?

[prasannakumard]

Actually, in Service Operations Workspace, for Universal request show Mandatory alert like below:

So, our client want to replicate the same for Source to pay workspace. Please let me know where I need to update the same.

Thanks & Regards,

Prasanna Kumar

[Dr Atul G- LNG]

Hi @prasannakumard 

SO you want to remove the word error alert, I checked in UI policy and sys message but did not find, seems it something core code. Better log a Now support case. 

[Gustavo Olivei1]

Did you find the answer to that?

I am facing the a very similar situation but it is not related to removing the text but to add the link again.

Basically, on your first screen, you have 'Error Alert  + content + field_name_with_link' and following your requirement is to have 'Content + field_name'. In my context, I was using the Record Default page for CSM WS that loads the Error Alert, but when I upgraded to Xanadu the recommended record page is the CSM Record Default, and starting from that the "Alert" itself has automatically changed.

So my advice to you is to check if you are using the last/supported page. Probably when you do that you will face the "new" Alert without 'Error Alert'... That was what I got here.

However, I am still looking for how/where is possible to add the link/anchor to the field name. For UX perspective, there is value on that