SuperOffice CRM is seeking a Developer Advocate to join our Developer Experience (DX) team . In this role, you will be responsible for building and nurturing relationships with our developer community, and promoting our CRM platform through technical content creation and engagement activities. Do you like to write code , help others solve problems , and have an impact on SuperOffice APIs? Come apply for the position and make the SuperOffice developer community be an even better place. https://careers.superoffice.com/jobs/2512680-developer-advocate

In the worst-case scenario, an application may have hardcoded a tenant API URL as "https://online.superoffice.com/[Cust00000]/api/v1," which may currently be functional. However, we have consistently advised developers to use either the WebApi_Url or NetServer_Url, which are issued as claims in the OpenID Connect id_token. In light of upcoming infrastructure changes aimed at improving load balancing and performance, the API URLs for online tenants are becoming more dynamic. The plan is to remove the API URL claims from the id_token and now are recommending all applications use the state URL to retrieve a tenant's API URL. The state URL follows the format: https://[environment].superoffice.com/api/state/[Cust00000] Here, the "environment" parameter is set to either " sod ," " qaonline ," or " online ," representing development, stage, or production environment, respectively. The "Cust00000" parameter is the unique identifier for the tenant. How often should applications check the state URL for changes? API URLs will typically be invalided during the evening during maintenance, which is posted on status.superoffice.com, however it may also depend on how much traffic an API endpoint receives. For more information, please refer to the documentation available at: https://docs.superoffice.com/en/apps/tenant-status We plan to enable these changes in the SOD environment moving forward. This will allow you to test your applications' resiliency and ensure it continues to function and operate before pushing any required changes to production. We expect to roll out these changes to production by the end of June this year . Question and/or comments are welcome.

We're currently working on forcing apps to use the correct public endpoint for the API calls. This was implemented in SOD yesterday, and if you are now experiencing 401 response when trying to perform an authenticated API call  then make sure you are actually hitting the correct endpoint for this tenant. For example: If you have hard coded sod .superoffice.com/custxxx/api/v1/ and the web_api url returned in the ID Token is sod2 .superoffice.com/custxxx/api/v1/ you will likely see the HTTPS status code 307 redirect and have connectivity issues. The netserver_url and webapi_url claims are returned in the ID Token: https://docs.superoffice.com/authentication/online/index.html#id-token https://docs.superoffice.com/authentication/online/validate-security-tokens.html#superoffice-specific-claims The endpoint is also returned in the tenants status: https://docs.superoffice.com/apps/tenant-status/status-page.html  

Hi All, I hope this is the correct forum to post this, but is there any way of adding the department, to the search box in CS on a new ticket (not in the dialog on the right, but on the list on the left).  You used to be able edit the old lookup control on CS tickets, but can you edit the new control.  A customer of ours has a number of contacts that work across multiple companies, so they would like to see the department in the list to help them select the correct site address.   Many thanks, Trevor  

Hi, in my local on-prem version of SuperOffice, version 10.2.1 I noticed a new option in Settings and Maintenance called "Perform tasks after upgrade".   Clicking it gives this dialog And clicking OK gives this   What is this for?

The partnersites in SOD will be updated to Release 10.2.4 monday morning around 06.00.  The version is still under development, so the sites will be updated ever day when there are any changes, until the release is out.  

The PartnerSites in SOD will be updated to Release 10.2.3 monday morning around 06.00. The version is still under development, so the sites will be updated each morning when there are any changes, until the release is out. If there are any hotfixes, the PartnerSites will be updated to the new versions.

The PartnerSites in SOD will be updated to Release 10.2.2 tomorrow tuesday morning around 06.00. (And actually was updated today also...) The version is still under development, so the sites will be updated each morning when there are any changes, until the release is out. If there are any hotfixes, the PartnerSites will be updated to the new versions.

The PartnerSites in SOD will be updated to Release 10.2.1 tomorrow tuesday morning around 06.00. The version is still under development, so the sites will be updated each morning when there are any changes, until the releease is out. If there are any hotfixes, the PartnerSites will be updated to the new versions.

OK, so we just published the first v10.2.1 (1517) nuget packages, as well as updated the WebApi packages!  There are a few things to note about NetServer core. In addition to the services.RegisterWithNetServer ( shown in the example project ), you need to adapt to the following DI configuration changes. Session Mode Changes The config file setting for Session Mode has been removed.  This has been replaced with a session handling implementation to AddNetServerCore. services.AddNetServerCore<SuperOffice.Web.Security.HttpContextProvider>(options => { //... set options } The session mode is an implementation of ISoContextProvider public static IServiceCollection AddNetServerCore<TSessionMode>(this IServiceCollection services, Action<NetServerCoreOptionsBuilder> optionsAction = null) where TSessionMode : class, ISoContextProvider { //... } There are several default implementations of ISoContextProvider located in SoCore. ThreadContextProvider ContextContextProvider ProcessContextProvider  Another is HttpContextProvider, located in SuperOffice.DCFWeb. Services Mode Changes The Setting for Services Local or Remote NetServer mode has been removed from the Config.  This has been replaced with extension methods to IServiceCollection. For Local mode calling Services Implementation, use: services.AddDCFServicesImplementation(); services.AddServicesImplementation(); services.AddMessagingServicesImplementation(); For remote mode using proxies, use:  services.AddServicesProxies(); Logging Changes  Configuration of logging has been moved from NetServer to the application using NetServer.  SuperOffice NetServer now support logging in the appsettings.json file. { "Logging": { "LogLevel": { "Default": "Error", "Microsoft": "Error", "SuperOffice": "Warning" } } } It is configured using the AddLogging extension method. services.AddLogging(a => { a.AddConfiguration(configuration.GetSection("Logging")); }); That's about all for now. Checkout the API release notes for more api changes in this release!