SuperOffice CRM Professionals

Hi Tony, Thanks for this, I have often used "soprotocol:main[refresh=true]" as it seems to refresh the entity that you have open (the top half at least), without redirecting you to another entity. But I have now tried this SOProtocol command below, and it kind of works. sale[refresh=true].main.saleactivityarchive (I think it is correct, I got the format from this page ).   When I run this script now (from the Sale Task menu), if I am already on the Activites tab of the sale, then it now does correctly refresh and I can see the newly added document, however if I am on another tab, I.E. Quote or Stakeholder, it takes me to the Activities tab, but does not refresh it.  I still have to manually refresh, to see the new document.   Is my above SOProtocol statement now correct, or am I missing something that would explain why it does not refresh when run, whist on a different sale tab?   Many thanks,   Trevor

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 .

Hi, I have created a script that generates a quote order confirmation from a sale with a quote.  The customer needs to produce a number of different documents from the quote lines when the quote is sold, but out of the box, only one order confirmation document can be created at the point the Place Order button is pressed (by selecting the "Send order confirmation via e-mail" option). I have created other order confirmation documents in SuperOffice for things such as Works Orders, and then use "quoteAgent.GetOrderConfirmation(quoteVersionId, confirmationTemplateId)" to get a Base64 string of the document, and create a document in SuperOffice based on this Base64 string. It all works well, the script runs on the Task Menu and shows a form with a list of all available Order Confirmation templates, and then creates a document based on the selected template. The one issue though is that SuperOffice does not seem to create a unique filename for each of the documents generated via the CRM script, so if the same document template is generated twice for the same quote (filename is based on the template type and quote number), they both get the same filename, and both documents in SuperOffice are linked to the same physical file.  This also means that when one of these documents is deleted in SuperOffice, you get an error opening the other document, as the physical file linked to this document is now deleted. I have worked around the issue by adding a datetime stamp at the end of each filename, so that it is always unique, but this is not ideal, as when the user uses the "Send as email" option for this document, the file is attached using the messy filename (instead of the better solution which the legacy Outlook Mail Link does, of generating a new clean filename based on the document subject). If you use the doc.SetName or doc.SetHeader, some tidying of the filename is performed, I.E. if I set the filename to "Works Order Sheet - Quote 10084 v2.pdf", it will set the filename to "works-order-sheet-quote-10084-v2.pdf", but you would think that if this filename was already in use in that SO_Arc folder, that it would rename it to something like "works-order-sheet-quote-10084-v2[2].pdf". I have looked to build a search engine to see if the filename is already in use and then increment a number at the end of the filename, but only if the original filename has been used before.  However the text stored in the name field is sometimes with spaces, sometime with dashes, but either way the actual filename created is always with the dashes, so this is inconsistent. Is there any simple way with the Document Agent, to specify a desired filename for a document, and have SuperOffice automatically adjust this, to keep the basic format of your filename, but ensure the filename of the file created in unique to that SO_Arc folder. Many thanks, Trevor

As has been announced previously, version 11 was the last to release an Onsite version from the same code base as Online. Starting with 12.0 the feature development is Online-only. The Onsite version will be essentially frozen, with occasional security fixes, and continue with minor version numbers (11.14 and onwards). Consistent with this, we do not plan to publish 12.x versions of our SDK packages. This includes the following:  - SuperOffice.ContinuousDatabase  - SuperOffice.NetServer.Core  - SuperOffice.NetServer.Services  - SuperOffice.Crm.Web  - SuperOffice.QuoteConnector  - SuperOffice.Crm.Online.IntegrationServices  - SuperOffice.License We will continue to publish:  - SuperOffice.WebApi  - SuperOffice.WebApi.Authorization  - SuperOffice.WebApi.Authorization.AccessToken  - SuperOffice.WebApi.Authorization.SystemUserTicket A reminder - version 12 is the last version to accept incoming WCF calls to the API. Anyone who still uses WCF should migrate to WebApi as soon as possible.

Thanks!