The partnersites in SOD will be updated to Release 11.5 Friday 3.october at 06.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.5 is planned released to the first customers 13.october. Featuretoggles turned on for the PartnerSites for 11.5: NewServiceRequest, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, CustomObjectsV4, AnalyticsAmp, BoardView, BoardViewProject, BoardViewRequests, ReplyTools, EnableDirectMicrosoftTeamsLinks, BizCardScanner, LeadManagement (This featuretoggles are new and will be added to the sites with first upgrade: LeadManagement, CustomObjectsV4) (This featuretoggles are removed from code and will be removed from the sites after first upgrade: LiveRequestUI)

The partnersites in SOD will be updated to Release 11.5 Friday 3.october at 06.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.5 is planned released to the first customers 13.october. Featuretoggles turned on for the PartnerSites for 11.5: NewServiceRequest, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, CustomObjectsV4, AnalyticsAmp, BoardView, BoardViewProject, BoardViewRequests, ReplyTools, EnableDirectMicrosoftTeamsLinks, BizCardScanner, LeadManagement (This featuretoggles are new and will be added to the sites with first upgrade: LeadManagement, CustomObjectsV4) (This featuretoggles are removed from code and will be removed from the sites after first upgrade: LiveRequestUI)

The partnersites in SOD was updated to Release 11.4 Monday 15.september at 18.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.4 is planned released to the first customers 22.september. Featuretoggles turned on for the PartnerSites for 11.3: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, AnalyticsAmp, BoardView, BoardViewProject, BoardViewRequests, ReplyTools, EnableDirectMicrosoftTeamsLinks,  (This featuretoggles are new and will be added to the sites after first upgrade: BizCardScanner)

The partnersites in SOD was updated to Release 11.4 Monsay 15.september at 18.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.4 is planned released to the first customers 22.september. Featuretoggles turned on for the PartnerSites for 11.4: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, AnalyticsAmp, BoardView, BoardViewProject, BoardViewRequests, ReplyTools, EnableDirectMicrosoftTeamsLinks,  (This featuretoggles are new and will be added to the sites after first upgrade: BizCardScanner)

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! Developer Portal Team

We want to inform you about a breaking change in SuperOffice NetServer Scripting that was introduced in version 10.5.4 with the release of the new Appointment Dialog . What changed Prior to v10.5.4, when saving new appointments, the SuperOffice web client used  AppointmentAgent.Save method, which would raise the following NetServer scripting event:   static void BeforeSave( AppointmentEntity appointmentEntity, RecurrenceUpdateMode updateMode, Boolean sendEmailToParticipants, EMailConnectionInfo smtpEMailConnectionInfo, EMailConnectionInfo imapEMailConnectionInfo, CancellationToken cancellationToken, ref object eventState ); Starting with v10.5.4 , and the new Appointment dialog, the web client now uses  AppointmentAgent.SaveWithCustomInvitation : static void BeforeSaveWithCustomInvitation( AppointmentEntity appointmentEntity, RecurrenceUpdateMode updateMode, Boolean sendEmailToParticipants, EMailConnectionInfo smtpEMailConnectionInfo, EMailConnectionInfo imapEMailConnectionInfo, String emailBody, String subject, String templateLanguage, CancellationToken cancellationToken, ref object eventState ); Why this matters This change can have cascading consequences for any onsite customizations that rely on the NetServer scripting event engine for automation. If your scripts are tied to the previous AppointmentAgent.Save method, they may no longer trigger or behave as expected. What you need to do If your automation depends on AppointmentAgent.Save , you may need to update your scripts to handle AppointmentAgent.SaveWithCustomInvitation accordingly. Our apologies We regret not announcing this change sooner. We understand that late communication can cause avoidable disruptions, and we will strive to be more diligent in communicating such impactful changes ahead of time in the future. If you are unsure whether this affects your environment, we recommend reviewing any custom scripts related to appointment creation and testing them against the new dialog in v10.5.4 and later. Version 11 Breaking Changes While on the subject, we announced (Apr. 2024) major breaking changes coming in v11 . With regards to NetServer scripting events all event names have changed. All event names will have the Async suffice. Therefore, all existing event handlers will require updates accordingly. Best regards      

Hello Reasently we upgraded our environment into 10.5.4 and started to use new service instead of the separated UI. It is possible to configure service screen in a way we like when you open ticket completely, but if you look at the ticket from the selection list in preview, there are only some of the fields to view and some of them are drop downs for modification. Is there a possibilty to modify this preview window? In our case we would like to see different fields in different order. Thanks Regards Ingar

The partnersites in SOD are planned to be updated to Release 11.3 Friday 15.august in the morning. The version is still under development, so the sites will be updated when there are any changes. Version 11.3 is planned released to the first customers 25.august. Featuretoggles turned on for the PartnerSites for 11.3: NewServiceRequest, LiveRequestUI, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CustomObjectsv1, CustomObjectsV2, AnalyticsAmp, BoardView, BoardViewProject, BoardViewRequests, ReplyTools, EnableDirectMicrosoftTeamsLinks

In the upcoming  SuperOffice v11.3 release , we are introducing a new security property for CRMScripts that lets you define which HTTP verbs are allowed  when executing a script via specific endpoints. This property applies only  when a script is executed via: ` blogic.fcgi?action=doScript ` ` customer.fcgi?action=safeParse ` or ` customer.fcgi?action=printBin ` Scripts run in triggers, scheduled tasks, or other internal contexts are not  affected by this setting. What you can do with it Block  all verbs to prevent a script from being run through the above endpoints. Allow only specific verbs  (e.g., GET, POST, PUT) when creating custom API endpoints. This gives you finer control over script execution and improves overall security. Default behavior For  existing scripts : All verbs will be enabled by default in v11.3. When creating scripts through the  CRMScript Agent : If the new property is omitted from the payload (as will be the case for most existing integrations), all verbs will be enabled by default. When creating a script via the GUI : All verbs will be disabled by default , letting you explicitly choose which ones to allow.  

As part of our ongoing efforts to streamline and optimize the SuperOffice CRM database, we are considering the removal of legacy elements associated with the discontinued Audience publishing functionality. This includes tables and features such as Publish, Task.defaultPublishType, DocTmpl.defaultPublishType, and associated references in projects and associate diaries. Since Audience is no longer an active product or supported capability, these elements are no longer maintained by SuperOffice. However, before proceeding, we want to ensure this change does not negatively impact any of our partners or integrations. Have you or your organization re-purposed or built custom functionality that relies on the Publish table or related properties? If so, we would greatly appreciate your input. Understanding how—if at all—these legacy elements are being used today will help us make an informed decision and provide proper guidance moving forward. Thank you for your continued collaboration!