Technisch Latest content Contact forms Forums Blogs Resources

soprotocol misbehaves in SuperOffice 11.3

lock
push_pin
done
Beantwortet
10
7

Hi, 

after Online upgraded from SuperOffice 11.2 to 11.3 we see that URL's used to open a new ticket and set a person selected, no longer works.

This feature is documented at the top here: https://docs.superoffice.com/en/ui/soprotocol/howto/requests.html

When navigating to https://online2.superoffice.com/CustXXXXX/default.aspx?ticket.new?person_id=123, it redirects to https://online2.superoffice.com/CustXXXXX/default.aspx?ticket.new.minicontact?ticket_id=0&selection_id=456, and no person is set on the ticket.

Seems like something has happened to soprotocol in 11.3. Is there a new way of doing this now, or is it broken?

Frode Lillerud
9. Sept. 2025 | 06:57 AM

Alle Antworten (7)

We are also noticing multiple issues with soprotocol with the 11.3 release and have send multiple reports to bug@superoffice.com, some but not all issues:

- selecting a row in a custom archive created through screen designer reloads the page due to the soprotocol calculation

- creating or opening appointments using soprotocol externally (so by default.aspx?soprotocol) throws errors from the CalculateCurrents endpoint 

- refreshing the screen, like sale.main[refresh] does not work anymore and shows a 'create a new sale' screen

David Hollegien
9. Sept. 2025 | 11:14 AM
Hi,

Regarding creating or opening appointments using soprotocol. What does the soprotocol look like and does this happen every time?
Jørund Myhre
22 h, 23 m vor | 06:43 AM
Hi Jorund, it happens every time. Please see SOS ID 3574093

Samples;

New appointment:

https://online3.superoffice.com/CustXXXXXX/default.aspx?appointment[new=true]?appointment_id=0&appointment_type=1&contact_id=0&person_id=0&calendarassociate_id=9&doby=2025.09.09%2006:00&endDate=2025-09-09%2012:00

And opening an existing appointment would be this url:

https://online3.superoffice.com/CustXXXXXX/default.aspx?appointment.main?appointment_id=211928
David Hollegien
22 h, 11 m vor | 06:55 AM

I am experiencing problems with the SoProtocol for opening the document dialog. A customer has a CS-script which is shown as a pane on the tickets in "old service" - and this uses window.open javascript to redirect to SuperOffice to open the new document dialog with a selected template on the customer. This worked on friday before 11.3. 

The URL we are using are: https://online3.superoffice.com/Cust99999/default.aspx?document.main%5bnew=true&mode=edit%5d?document_id=0&contact_id=17302&person_id=14803&doctmpl_id=174

I have tried to make a plain html/javascript and including this in the minicard in SuperOffice. When I am using SoProtocol with just 'document.main..." the dialog is shown correctly. The problem seems to be that the parameters are "cleaned" when we are passing these parameters to the full url (default.aspx)? 

I really hope there is a possibility for a quick fix to patch up the current release for this... 

Atle Bjerck
9. Sept. 2025 | 04:09 PM
Hi Atle,

I did a quick test on an 11.2 release and couldn’t see that "doctmpl_id" is working to select the document template. It looks like you need to use "&documenttemplate_id=174" instead.
From what I can tell, "doctmpl_id" has not been supported previously, but the other parameters look good.
Bjørn Olav Ringstad
20 h, 8 m vor | 08:58 AM
Thanks for your reply Bjørn Olav. My understanding is that this is not a problem with the parameters (I think that would have just resulted that we would not get the correct template selected), but that there is a serious issue with SoProtocol-parameters in this SuperOffice version...

The result is the same when changing the URL parameter from doctmpl_id to documenttemplate_id - everything is "swallowed" and cleaned from the URL when pasting this in a browser (or calling from a script). It worked fine before 11.3 - so the doctmpl_id have been working.

I have now tested that if I make a html/js-page and use SuperOffice.ClientCrossMessaging only forwarding the parameters (after default.aspx) - the command works. The customers problem is that this is done from a pane inside the old service screens - where ClientCrossMessaging don't work.

I have testet that both doctmpl_id and documenttemplate_id works the same way when I am using ClientCrossMessaging...
I will be glad to do a session with you to show you details about this if you would like that.
Atle Bjerck
16 h, 25 m vor | 12:41 PM
Our experience is as well that the appointment soprotocol we execute works correctly with ClientCrossMessaging but not through default.aspx
David Hollegien
16 h, 21 m vor | 12:44 PM
An issue with using soprotocol in the URL has been found and will be fixed for 11.4 (pending hot fix for 11.3).
Jørund Myhre
16 h, 12 m vor | 12:54 PM
Please consider a hotfix for this. This issue completely breaks usage of SuperOffice for some customers.
David Hollegien
16 h, 10 m vor | 12:55 PM
Just to clarify, I tested this in version 11.2 and noticed that the parameter "doctmpl_id" doesn’t seem to have any effect. Instead, "documenttemplate_id" works as expected.

For example:

Using "documenttemplate_id=4" or "documenttemplate_id=5" correctly opens a new document with the corresponding template.

Using "doctmpl_id=4" or "doctmpl_id=5" instead just falls back to the top history item in the template list.

This is the behavior I observed in the 11.2 release, prior to the later issues.
Bjørn Olav Ringstad
15 h, 20 m vor | 01:45 PM

We also experience the same issue with soprotocol on projects. 

Refreshing the screen, like project.main[refresh=true] does not work and shows a 'create a new project' screen

CN
Camilla Nysterud
21 h, 27 m vor | 07:39 AM
Issue has been addressed for v11.4
Jørund Myhre
16 h, 11 m vor | 12:54 PM

Hi

Opening existing documents in the document dialog does not work either. For example, this used to work:

https://online.superoffice.com/CustXXXXX/default.aspx?document.main?document_id=12345

Espen Steen
20 h, 10 m vor | 08:56 AM

Hey,

We at InfoBridge are also having issues with SOProtocol. In Activity Folders we're using  "document[dialog=stop].main?document_id={id}" for example. This one doesn't work anymore in the latest release.

Kevin Jager
16 h, 16 m vor | 12:50 PM

Thank you for sharing your detailed feedback and examples regarding the issues with soprotocol after the 11.3 release. I'm now fully aware of the situation and will make sure this is followed up internally.

Pierre Van Mever
16 h, 14 m vor | 12:52 PM

Hello!

We have a fix for this issue in SOD, and therefore would like you to test this issue on at least one of your SOD tenants.

Please send us an email to appdev@superoffice.com and instruct us which SOD tenant you would like us to upgrade for your testing and verification.

Best regards.

 

 

Tony Yates
15 h, 52 m vor | 01:14 PM

Antwort hinzufügen