Hi, As described here: Mailings: Handling of links when changing hostname (migration or onsite) , you can set a registry setting with allowed hostnames for the hash calculation of links in the mailings, so that they don't break after mgirating to Online (and you have put in a redirect at the old/OnSite domain). I have been trying different combinations of getting this to work, but no matter what I do, I get the an error with that the link is invalid: Example: Customer domain is 'superoffice.label.company.nl', working link in a mailing for the current onsite environment is: https://superoffice.label.company.nl/scripts/customer.fcgi?action=ejLink&key=2358:8915:2383:dc31c93739640ec674e393dae1ef0a275c945e7d&sai=1571556 New link in their Online environment would be: https://online2.superoffice.com/<tenant>/CS/scripts/customer.fcgi?action=ejLink&key=2358:8915:2383:dc31c93739640ec674e393dae1ef0a275c945e7d&sai=1571556 I filled in the registry setting 358 the following CRMScript: SearchEngine seRegUpdate; seRegUpdate.addData("registry.value", "superoffice.label.company.nl,online2.superoffice.com"); seRegUpdate.addCriteria("registry.reg_id", "OperatorEquals", "358"); seRegUpdate.update(); But accessing the link to the online environment still throws a link not valid error. How is this supposed to work?

I installed the lastes SuperOffice Onprem version 10.5.4, and everything went well. When I logged into the SoAdmin 'Settings and Maintenance' the screen looked like this. The menu is there, but no content in the panels on the rigth. When I go into the 'Developer tools' in Chrome, an error shows up, - here it is It seem like the problem is with the SCIL javescript. Does anyone know how to fix this problem. We tried removing the whole installation, and doing a reinstall, both on the new database and the existing one. Does anyone know, what this problem can be solved ?    

Hi forum   I was trying to programmatically generate a document. My document is generated an all, with the correct content, and the template variables substituted and all, so so far so good. But for some reason the file attached to the document entity does not have an extension. The template in question is a somail template. Is there something i'm missing? as far as i know, i'm not supposed to give the document a name manually, as it has to make sure a file with the same name does not already exist. Problem is right now, that SuperOffice does not open the document correctly (Since it has no idea how to handle it, due to the missing file extension) But when it is downloaded, and i add .eml at the end, the mail is able to open inside outlook with no issue. //Get a default document entity: /api/v1/Document/default const document = await fetchData(`/api/v1/Document/default`); // document.Person = {PersonId: activeRowValues.medlem.id}; document.DocumentTemplate = { DocumentTemplateId: activeRowValues.skabelon.id //.somail template }; document.Header = "Udpegning af medlem til udvalg"; //Post the document ///api/v1/Document const documentResponse = await fetchData(`/api/v1/Document`, document, 'POST'); //POST Document/{id}/Content const documentContent = await fetchData(`/api/v1/Document/${documentResponse.DocumentId}/Content`, {}, 'POST'); //Update the document entity with the data from the documentContent const documentResponse2 = await fetchData(`/api/v1/Document/${documentResponse.DocumentId}`, documentContent, 'PUT'); //POST /api/EMail/GetMailLinkOpenUrl?documentId=3146231 const emailLink = await fetchData(`/clientapi/EMail/GetMailLinkOpenUrl?documentId=${documentResponse2.DocumentId}`, {}, 'POST'); //Navigate to the document window.location.href = emailLink; //SuperOffice.ClientCrossMessaging.openDocument(documentResponse2.DocumentId); console.log("Document Response:", documentResponse2);

Good afternoon SuperOffice, I am having a problem with the Updated Dates when accessing these in the Saas enviroment. I have read the documentation here: https://docs.superoffice.com/en/api/netserver/web-services/so-timezone.html It states that the Created and Updated dates are always in UTC, and that the SO-TimeZone header is ignored: I have been testing this in postman, and the Updated Dates I am getting back from the API call are UTC + 2Hrs. Below is an example of me update this company, as you ca see I did this at 15:11:18 (BST):   UTC for this would be 14:11:18pm, but when I call the API, I get a date of 16:11:18   I have tried to add the TimeZone header anyway, but get the same result:   Please could you advise where I am going wrong? Cheers Rich          

When configuring the SO10Web to Authenticate via Active Directory by using the <ActiveDirectoryCredentialPlugin> settings in Web.Config the system is using LDAP for communicating with AD. I got a question from the IT-department of a customer that is planning to upgrade from SuperOffice 8 to 10 (not migrating to Online yet because of some other legacy systems) - if this connection is done by LDAPS (that is with SSL). What is required to force this authentication not to be done in "plain LDAP" but to use LDAPS?  And is there a possibility to use "Signed LDAP" authentication?  Are there any configuration possibilities for this in SuperOffice itself - or do SuperOffice rely on configurations done on the Windows Server that is running the IIS? 

When a user in a marketing mail selects the checkbox "Override consent and subscription / Overstyr samtykke og abonnement".  Is this value stored in the database somewhere ? 

I apologize if this is not the appropriate forum for this query. Following a recent update to the CRMScript tracing mechanism, the debugger no longer tracks the current line of execution. As a result, during step-by-step tracing, the user must manually locate the active line in the script, which is both cumbersome and time-consuming. Could this behavior be reverted or corrected so that the trace once again follows the currently executed line?