"Save" UI action no longer showing in workspace when generating knowledge articles with Now Assist

Snowman15
Giga Guru

2 hours ago

Hi,

When we used to generate knowledge articles with Now Assist feature in workspace, we had a "save" UI action to save the article, that button is no longer there for some reason. Does anyone know how to add it back? 

Thanks

 

Snowman15_0-1769623507422.png

 

0 Helpfuls
  • 96 Views
1 REPLY 1

Itallo Brandão
Tera Guru

an hour ago

Hi @Snowman15 ,

Technical Analysis: In the modern Configurable Workspace (which Now Assist uses), buttons are primarily controlled by Declarative Actions (Action Assignments), not just the classic UI Actions. If the "Save" button has disappeared specifically during the "Create New" flow, it is likely that the Action Assignment condition is failing for the specific state the record is in (e.g., isNewRecord()) or for the specific View that Now Assist loads.

Here is how to troubleshoot and bring it back:

Step 1: Check Declarative Actions (Most Likely Cause) Workspace buttons are defined in the table sys_declarative_action_assignment.

  1. Navigate to All > Workspace Experience > Actions & Components > Action Assignments.

  2. Filter the list:

    • Action label: Save

    • Table: kb_knowledge (or global if you don't find a specific one).

    • Implemented as: UXF Client Action (usually).

  3. Open the record.

  4. Check the Conditions: Look at the Record Conditions tab.

    • Does it have Active = true?

    • Does it have a condition like !current.isNewRecord()? If Now Assist presents the article as a "New" record (unsaved), and the condition forbids new records, the button will hide.

  5. Check View Exclusion: Look at the Action Exclusion tab related list. Ensure the view Now Assist is using (often default or a specific 'draft' view) is not listed there.

Step 2: Check the Classic UI Action (Fallback) If your workspace is still relying on classic bindings:

  1. Navigate to System Definition > UI Actions.

  2. Search for Name: Save, Table: kb_knowledge.

  3. Open the "Save" action (there might be multiple, look for the one with Form button checked).

  4. Ensure the "Workspace Form Button" checkbox is selected.

  5. Crucial: Check the Condition field. If the script relies on fields that Now Assist hasn't populated yet (e.g., current.canWrite() or specific workflow states), it might be evaluating to false.

Step 3: Is it in the Overflow Menu? Sometimes, if the screen width changes or other buttons take priority (like "Generate with AI"), the "Save" button gets pushed into the Context Menu (the three dots ... next to the button area). Check if it is hiding in there.

Summary: The issue is almost certainly in the Action Assignment conditions for the kb_knowledge table not matching the state of the generated draft.

Best regards,
Brandão.

0 Helpfuls