Email client in Risk workspace not working as expected

Monique Scheffe
Tera Contributor

We have configured an email_client on the Risk Workspace for sending email from a Risk Response task.

For the appropriate tables the email_client is added  and the Compose email action is available in the more actions menu on the Risk Workspace as expected.

However, when selecting the Compose email action the draft email is not rendered in the correct way.

 

Expected something like this:

 

MoniqueScheffe_1-1678438291199.png

But this is actually shown

 

MoniqueScheffe_0-1678438127367.png

 

 

On the community I found a similar issue and the solution for it, only this is on the Agent Workspace, but the problem is exactly the same.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0823289

 

It is not possible to add similar settings for the Risk Workspace, as we can only select the Agent workspace.

Risk Workspace is not in the list of active workspaces (is this protected??) 

 

In the default view on the risk task the send email function is working correct. Also the created quick message is working as expected.

 

Does anyone have a suggestion on how we can make this work?

8 REPLIES 8

Used this to fix same issue in custom configurable workspace.
- Open workspace in ui builder, navigate to Record page and create a email draft page variant.
ui1.png
- Set the conditions for this variant to be table=sys_email_draft in the variant condition text area.
- Open the variant settings from the Menu ->Developer->Open Variant. This will open a form containing all the variant information.
- Set the Page definition here to Compose Email(a macroponent provided). Save the Record.
ui2.png

This workaround worked for me perfectly.

I created directly by UX Screen Table(sys_ux_screen) in the Application that I have the problem and changed the Parent Macroponent to "Workspace App Shell"

Thanks, a lot

Tom Sienkiewicz
Mega Sage

Hi Monique,

 

did you mange to get the legacy HTML editor to work in your Workspace? I would be curious to know as I am running into a similar problem with a custom Workspace.

 

I wonder if this is an intentional limitation to use a "new" email composer without HTML capability but it would be pretty unusable, so I hope this is a "bug".

 

I tested with a Workspace created in UI Builder and also with one created from Workspace Builder, in both cases the new composer is being used and there is no way to add the "sys_aw_master_config" record for it. I could probably hack my way into adding it but I'm worried this might break some other configuration...

Many thanks,

Tom

Ankita_Sharma_
Tera Contributor

Hi @Monique Scheffe 

Is this issue solved for you, even I'm facing same issue in Audit Workspace. 

Kindly let me know if any possible workaround you come across.

 

Thanks 

Ankita