Project Workspace (Zurich) - gs.addInfoMessage() flashes and disappears after Create Work Order

[SAS21]

Hi,

I'm seeing some unexpected behavior in Project Workspace (Breadcrumb App Shell) on the Zurich release and wanted to check if anyone has experienced something similar.

Scenario

A Work Order is created from a Project Task using the Create Work Order related list UI Action.

During the creation process, server-side messages are added using gs.addInfoMessage().

For example:

gs.addInfoMessage("The selected project does not have a Default Dispatch Group.");

There is also an OOB message from WorkManagementInitiation: (Scriptinclude)

gs.addInfoMessage(gs.getMessage("Work Order created for {0}", previousItilTask.number));

 

Issue

In Project Workspace:

• The info messages briefly appear after the Work Order is created.
• They immediately disappear.
• If I navigate back to the originating Project Task, the same messages are displayed again.

This indicates that the messages are still available in the session but are not being rendered correctly immediately after the redirect.

Comparison

UI Behaviour - Info messages stay on native , also FSM/CSM work space - timeout after 5 sec

Investigation performed

• Verified the Business Rule executes correctly.
• Verified gs.addInfoMessage() is called.
• Reproduced the same behavior with the OOB "Work Order created for..." message.
• Tested gs.getSession().addInfoMessage().
• Compared Project Workspace with FSM Workspace.
• Verified notifications are enabled in chrome_header.
• Noticed FSM Workspace has an OOB alert_auto_dismiss_config UX Page Property, while Project Workspace does not. Creating a similar property for Project Workspace (Route = Record) did not change the behavior.

Question

Has anyone seen this behavior in Project Workspace (Breadcrumb App Shell)?

• Is this expected behavior for server-side messages after action.setRedirectURL()?
• Is there a Workspace-specific notification mechanism that should be used instead of gs.addInfoMessage()?
• Or is this a known issue in Zurich?

Any suggestions or similar experiences would be greatly appreciated.

Thanks!

[Abhishek Pal · Accepted solution]

Hi @SAS21 ,

Based on your testing, I would treat this as a Project Workspace / Breadcrumb App Shell navigation-rendering issue rather than a problem with gs.addInfoMessage().

The strongest indicator is that the same behavior occurs with the OOB WorkManagementInitiation message. I would not modify that Script Include.

In native UI, gs.addInfoMessage() is a server-side session message and normally survives the redirect until the next page renders it. Project Workspace is UI Builder based and uses client-side routing, so I would not rely on:

gs.addInfoMessage()
+
action.setRedirectURL()

for persistent Workspace notifications.

The fact that the message flashes, disappears, and then appears again when returning to the Project Task also suggests the session message still exists, while the Workspace route/page lifecycle is removing the rendered alert.

I would also not continue with alert_auto_dismiss_config for this issue. That configuration controls how long supported alerts remain visible after they are rendered. It will not fix an alert that disappears because the page/route context is being replaced.

For custom Workspace functionality, use the UI Builder alert mechanism after the server operation completes.

For example, from a UI Builder page/client script:

api.emit("NOW_UXF_PAGE#ADD_NOTIFICATIONS", {
items: [{
id: "work_order_created",
status: "info",
icon: "info-circle-outline",
content: "Work Order created successfully.",
action: {
type: "dismiss"
}
}]
});

Preferably, return the actual result/message from the server operation and then trigger the alert on the client rather than duplicating business logic.

Recommended approach:

1. Do not customize WorkManagementInitiation or other OOB SPM scripts.

2. Reproduce the problem using only the OOB Work Order creation and OOB message.

3. Capture the exact versions of:
- Zurich patch/hotfix
- Project Workspace
- Workspace App Shell
- UI Builder

4. Check for compatible Store updates for Project Workspace and Workspace App Shell.

5. If the OOB message still behaves this way, open a Now Support case and provide the OOB reproduction. Ask Support to confirm whether there is a PRB/fix for Project Workspace or the Breadcrumb App Shell.

6. For custom messages, use the Workspace/UI Builder alert mechanism instead of depending on server-side session messages across Workspace navigation.

Also, the Notifications option in chrome_header is a different mechanism from the transient alert generated by gs.addInfoMessage(), so enabling header notifications would not necessarily change this behavior.

I could not find a publicly documented Zurich PRB specifically matching this scenario, so I would not call it a confirmed known Zurich defect without confirmation from Now Support.

Since you can reproduce it with the OOB "Work Order created for..." message, I think a Support case is appropriate before implementing any Workspace customization.

Hope this helps!

If this response helped, please mark it as Helpful.
If it resolves your issue, please Accept it as Solution.

Kind Regards,
Abhishek Pal