You are viewing limited content. For full access, please sign in.

Question

Question

Developer tools in Chrome showing unrelated form notifications

asked on February 14, 2024

I am on Version 11.0.2307.40556 of Forms.  I'm working on a new form and have the Developer Tools open in Chrome to show some console.logs while working through some jquery.  I notice that there are other things in the console window other than what I'm working on.  I see my relevant messages from my code.  But I also see notifications about other separate forms.

Included in the screenshot are a few console.logs that the javascript generated.  Also included are several notifications from other forms processes.  

I can click on the Task.New link and get way too much detail about this task.

There are other types of tasks that show up including when a task is assigned. 

Clicking the link will actually show me the code where these came from.  It is nothing I've written.  It is a notification function with a console.log in it that is, presumably, outputting this information.  But why do notifications from other Laserfiche processes show up in the Developer tools section of unrelated forms?  

We are newly updated from 10.4 to 11, and maybe this is a new feature???  I suspect not.  Has anyone else seen this?  

 

 

 

 

0 0

Answer

APPROVED ANSWER
replied on February 15, 2024

That is correct. When you first go to Forms, it also opens a websocket connection to the Forms Notification Service. The Forms Notification Service then sends task notification updates for anything in your Inbox in the background. The Notification Service is completely detached from whatever you're working on and has no awareness of what you're doing within Forms. It's just passing along the information necessary to update Inbox tasks as they become available.

2 0

Replies

replied on February 14, 2024

Yeah, I've seen it too, at least for several versions.  I always figured it was a built-in part of the routing and notification functionalities being able to update your Forms inbox without requiring a refresh.

2 0
APPROVED ANSWER
replied on February 15, 2024

That is correct. When you first go to Forms, it also opens a websocket connection to the Forms Notification Service. The Forms Notification Service then sends task notification updates for anything in your Inbox in the background. The Notification Service is completely detached from whatever you're working on and has no awareness of what you're doing within Forms. It's just passing along the information necessary to update Inbox tasks as they become available.

2 0
replied on February 15, 2024

Makes sense. I do similar things with SignalR in a few of my applications.

1 0
replied on February 15, 2024

Samuel, thanks for verifying Matthew's suspicions.  When I saw this the first time I briefly went into admin-panic, wondering 'who else can see this', 'what all info is it passing along'.  

I never saw this in version10.  Is it a new thing or maybe my predecessor configured it somehow so that it wouldn't show?

Thanks...

0 0
replied on February 15, 2024 Show version history

Not a new thing. Mostly likely wasn't configured (correctly) earlier and got set up when you upgraded to Forms 11. The Forms Notification Service requires a certificate binding on port 8181 and it's pretty common for updating that binding to get missed when certs get renewed. The 443 one is in your face with browser UI certificate errors but the 8181 you'd only see if you opened DevTools.

2 0
replied on February 15, 2024

The Forms Notification Service has an authentication handshake based on your authenticated Forms session so you're only sent updates for your own tasks. It's not a broadcast.

If you open DevTools' Network tab before logging into Forms, then log in, you'll see the Notification Service auth token generation, handshake, and websocket (SignalR) session initiation happen.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.