Hi everyone!  On Friday, we updated a number of customer databases where web panels contained  hard‑coded URLs pointing to specific tenant paths (such as https://online3.superoffice.com/cust12345/CS/scripts/blogic.fcgi?_sf=0&action=doScript&includeId=somethingSpecial). These have now been replaced with the recommended Service template variables like  <csbl> ?_sf=0&action=doScript&includeId=somethingSpecial Why this matters SuperOffice Online tenants can be moved between different locations/hosts over time. For example, a customer might be relocated from: online2.superoffice.com/Cust12345 → app.superoffice.com/Cust12345 If URLs are hardcoded, those links may break when the tenant moves. By using the supported variables such as:  <csbl> ?_sf=0&action=doScript&includeId=OurOwnScript URLs are generated dynamically , ensuring your customizations continue to work even if we reorganize or relocate the customer environment. More info on supported variables: https://docs.superoffice.com/en/document/templates/variables/for-service.html Do you need to do anything? No action required. The update has already been applied. If you're adding new web panels later, please make sure to use the variables.

Hello, Why is the "1760-01-01 00:00:00.000" DeletedDate value used for contact (company) instead of "NULL" when a new contact is created? In this article - Soft delete | SuperOffice Docs - it is mentioned that they are the same, but what is the difference between them? What consequences would there be if one changes this value to "NULL"?

As mentioned in the Partner Tech update on December 18th , we want to share an early heads‑up regarding an upcoming change to how database integration with SuperOffice is handled.  A full announcement with additional details will be published in January, but here is an early warning so you can start preparing. 🔄 From Database Mirroring Service → Replication Service The current Mirroring Service is based on SOAP/WCF. SuperOffice calls out to the customer. The customer must develop an application that receives events. It uses a custom authentication scheme. This will now be replaced by a new Replication Service . 🌐 What’s new? A standardized product executed by the customer. Outbound communication from the customer’s environment — no need to expose any endpoints to the internet. No custom authentication — uses modern, standardized mechanisms. More robust, easier to operate, and better suited for future operational models.   🏢 Support in different operational environments For customers running in the Visma data center : ➝ Both the Database Mirroring Service and the new Replication Service are supported. For customers running in the new operation environment : ➝ Only the new Replication Service is supported.

The partnersites in SOD will be updated to Release 11.10 Friday 06.february at 06.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.10 is planned released to the first customers 17.february. Featuretoggles turned on for the PartnerSites for 11.10: NewServiceRequest, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CopilotEnrichment(depends on HugoAI*, is now part of feature lab "AI Labs"), CustomObjectsv1, CustomObjectsV2, CustomObjectsV4, AnalyticsAmp, ReplyTools, BizCardScanner, RequestRelation, FormStyle (This featuretoggles are new and will be added to the sites after first upgrade: RequestRelation, FormStyle) (This featuretoggles are removed from code and will be removed from the sites after first upgrade: EnableDirectMicrosoftTeamsLinks )

The partnersites in SOD will be updated to Release 11.9 Monday 19.january at 06.00. The version is still under development, so the sites will be updated when there are any changes. Version 11.8 is planned released to the first customers 27.january. Featuretoggles turned on for the PartnerSites for 11.9: NewServiceRequest, HugoAiGpt, HugoAiIframe, HugoAIChat, HugoAISummarize, CopilotEnrichment(depends on HugoAI*, is now part of feature lab "AI Labs"), CustomObjectsv1, CustomObjectsV2, CustomObjectsV4, AnalyticsAmp, ReplyTools, EnableDirectMicrosoftTeamsLinks, BizCardScanner, FormStyle (This featuretoggles are new and will be added to the sites after first upgrade: FormStyle) (This featuretoggles are removed from code and will be removed from the sites after first upgrade: DashboardV3, BoardViewCompany)

  In close cooperation with our Product & Engineering department and our CTPO Thomas Rødseth as our host, we’re launching the SuperOffice Partner Tech Update — a 45-minute session dedicated to developers, tech consultants and integration specialists. This webinar will run in addition to our monthly Global Partner Update and gives you direct insights from our engineers. Topics this time: SuperOffice focus areas with technical impact Domain change → app.superoffice.com Updated Mirroring Service AI integrations (Start Page + early look at MCP) Who should join? Anyone working with integrations, customizations, or App Store development. Sign up today Here is the link.

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

Hello everyone, Starting with version 11.8, datetime fields in ticket archives now include timezone support. When calling the ticket archive OData endpoints (/api/v1/Archive) with the following header: SO-Timezone: UTC,includeTZOffset the behavior will be: UTC dates → returned as UTC; the browser will automatically convert them to the computer’s local time. Non-UTC dates → converted to the user-defined timezone. If timezones are disabled → non-UTC dates are returned as stored in the database, while UTC dates remain in UTC. ⚠️ Note: Custom datetime fields are not converted. The ArchiveComponent now automatically includes this header by default.

Starting with version 11.6, which is currently being rolled out to production, we will automatically disable webhooks where scripts repeatedly fail. This behavior has always applied to standard webhooks (HTTP), and now we are introducing the same mechanism for CRMScript-based webhooks. To help you monitor and respond to errors, we strongly recommend enabling error email notifications. For CRMScript webhooks, you can configure this using: webhook.SetErrorsEmail("username@domain.com"); and to check current webhooks errorsEmail: webhooks[i].GetErrorsEmail(); You can find more on configuring error notifications on docs.superoffice.com   Please review your webhook configurations and take advantage of this functionality to avoid disruptions.