The SuperOffice crossmessaging capability is great for sending navigation commands (SoProtocol) to the web client, or issuing an openDocument command, from an iFrame. As we move forward towards version 12, that's not going to change. One of the primary goals for v12 to is to run completely on .NET 8 (or higher), eliminating all dependencies on anything running .NET Framework 4.8 code. The current cross messaging command ajaxMethod depends on legacy code in .NET Framework context, and that means all ajaxMethod commands will cease to function in v12.  Are you using it? If so, please reach out (sdk@superoffice.com) and let us know. We will help you figure out how to instrument the same functionality without the ajaxMethod command.  Best regards!

The partnersites in SOD are planned to be updated to Release 11.1 Monday 19.may in the morning. The version is still under development, so the sites will be updated when there are any changes. Version 11 is a major upgrade, but changes are technical and "under the hood". So API's, featuretoggles, functionality should all be the same. Version 11.1 can be sidegraded to version 10.5.5 if needed. Version 11.1 is planned released to the first customers 27.May. Featuretoggles turned on for the PartnerSites for 11.0 is the same as for 10.5.5: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, BoardView

Hello Everyone, We are excited to announce a new Developer portal release! You can find more information and details about the new release by navigating to this page . Feel free to share your feedback with us!  

Is there any way to simply get an attachment from the attachment db table and convert it to a CRM document that can be added to a sale, contact etc etc? Like, in a imaginary scenario I wish for a like createCRMDocumentEntityFromAttachmentId(1) method or function? Or just any other way to solve it without having to parse the document from the attachment body to a CRM Document. 

The partnersites in SOD are planned to be updated to Release 11.0 Friday 9.May in the morning. The version is still under development, so the sites will be updated when there are any changes. Version 11 is a major upgrade, but changes are technical and "under the hood". So API's, featuretoggles, functionality should all be the same. Version 11.0 can be sidegraded to version 10.5.5 if needed. It will only be released to a few partnersites in production. Version 11.1 is planned released to the first customers 27.May. Featuretoggles turned on for the PartnerSites for 11.0 is the same as for 10.5.5: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, BoardView

Hi! We have experienced 3 customers with custom screens where the scrollbar is missing after they got the new UX. Is this a bug?    We know how to fix it, but is this something that should be fixed in the system? We need to add this; <style>   #HtmlPage_rightDiv {     overflow: scroll !important;   } </style>

The partnersites in SOD are planned to be updated to Release 10.5.5 monday morning. The version is still under development, so the sites will be updated when there are any changes. Featuretoggles turned on for the PartnerSites for 10.5.5 are: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, BoardView

The partnersites in SOD are planned to be updated to Release 10.5.4 monday morning. The version is still under development, so the sites will be updated when there are any changes. Featuretoggles turned on for the PartnerSites for 10.5.4 are: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2 (This featuretoggles are removed from code and will be removed from the sites monday 24.march: QuoteSCIL)

Hello great community! I've got a question for you... Do you have any known onsite installations dependent on the CDD APIs we released in SuperOffice version 8.1, for database schema changes? Custom objects is certainly the contemporary way integrations should make database schema changes. We would like folks to move away from using CDD and start using Custom objects instead. So, if you are using CDD instrumentation for database schema changes, please do let us know. You can reply to this thread, or send us an email at sdk@superoffice.com. Best regards!   

Hello Partners, We're excited to announce that you now have the opportunity to request access to a new SuperOffice v11 tenant in our SOD environment. With the Request v11 Tenant form, you can either request to upgrade your existing tenant or start fresh with a blank tenant. We encourage you to take this opportunity to test your current applications and integrations on the new platform. Your insights are crucial to ensuring a smooth transition. Should you encounter any issues, please report them by emailing appdev@superoffice.com with the following details: The API used, what you observed, and what you expected. Step-by-step instructions to reproduce the issue. A code sample that demonstrates the problem. Thank you for helping us enhance the SuperOffice experience. We look forward to your feedback! Best regards!