forum.infosoft.no

blog.infosoft.no

Another round of deprecations | Developers corner

https://blog.infosoft.no/blog/2016/09/19/another-round-of-deprecations?share=email

Another round of deprecations. It is time for another round of removing deprecated/legacy web service methods from the API. This time around we are going to primarily remove methods related to creating customers and subscriptions, as well as removing the legacy creditcard/payment API. We have a long list of methods that have popped up over the years for creating new subscribers with various parameters, all of which was finally replaced with a common shared routine as described on the documentation site.

blog.infosoft.no

Family or Shared Subscriptions | Developers corner

https://blog.infosoft.no/blog/2015/07/24/family-subscriptons?share=email

Family or Shared Subscriptions. The use of this functionality requires some integration from the web client, and the endpoint required to do so are exposed as SubscriptionUser.svc. The technical documentation on how these services work can be found on the API Documentation site, and in the comming months we will be adding a guide/description of the various details the service exposes. This entry was posted in Development. JobScheduler v1 and EmailListeners are being removed. Another round of deprecations.

blog.infosoft.no

Change of behaviour for version 3.6 | Developers corner

https://blog.infosoft.no/blog/2015/10/15/change-of-behaviour-for-version-3-6?share=email

Change of behaviour for version 3.6. The web service method GetAllDeliveryAddressesByDates. The expected behavior (based on the input parameters) would be to retrieve all delivery addresses for the given subscription (CustomerNumber and Title) for the given date range. However the actual behavior from at least v3.3 and onward to the latest version 3.5.1 is to retrieve all the customers addresses, regardless of title, in the given date range. The change of behaviour will be noted in changelog number 11745.

blog.infosoft.no

INFO-Web support webservices to be removed | Developers corner

https://blog.infosoft.no/blog/2016/03/14/info-web-support-webservices-to-be-removed?share=email

INFO-Web support webservices to be removed. As you might have noticed INFO-Web, the old self-service web client, is being discontinued. There is a “modern” replacement called INFO-Cweb which everyone with an INFO-Web license should have received an upgrade offer for. As a result of INFO-Web being replaced, a series of compatibility webservice methods are no longer needed, as there are other and better ways to achieve the same results. The following methods have their behaviour changed:. The methods will ...

blog.infosoft.no

Integrations | Developers corner

https://blog.infosoft.no/blog/category/development/integration

Another round of deprecations. It is time for another round of removing deprecated/legacy web service methods from the API. This time around we are going to primarily remove methods related to creating customers and subscriptions, as well as removing the legacy creditcard/payment API. We have a long list of methods that have popped up over the years for creating new subscribers with various parameters, all of which was finally replaced with a common shared routine as described on the documentation site.

blog.infosoft.no

.NET Framwork Upgrade | Developers corner

https://blog.infosoft.no/blog/2016/02/09/net-framwork-upgrade?share=email

Starting with version 3.7 (to be released in the beginning of Q4 2016), the Infosystems suite will require .NET Framework 4.6.1 to run. Refer to https:/ msdn.microsoft.com/en-us/library/8z6watww(v=vs.110).aspx. For details on what that means in terms of systems requirements. Note especially that Windows Server 2008 is no longer officially supported (reports says it actually works, but you are on your own if you choose this path). Windows Server 2008 R2 is still supported. C TADM51 731 exams.

blog.infosoft.no

Fixing stuff | Developers corner

https://blog.infosoft.no/blog/2015/03/24/fixing-stuff?share=email

As you might have noticed the last couple of posts have been related to stability issues, and small changes instead of huge new features. This one is no exception – this is going to be a post about what we are working on in the developer group. Based on this information we are now focusing our error fixing on the type of errors that occurs the most or affects the most users. So what kinds of errors are being fixed? Thats a bit hard to answer but we’ll give you some examples. Another example is when somet...

blog.infosoft.no

Developers corner | Infosoft development info | Page 2

https://blog.infosoft.no/page/2

Working with concurrency issues. With version 3.3 we did a major internal overhaul of the web service codebase, partly to simplify the API, but primarily to let us work with the concurrency issues in a structured way. Concrete examples of errors that no longer happens are the Frequency/Product errors from the GetSubscriptionElements (Webservice method) and constraint errors when running multiple daily maintenance jobs in the new job scheduler. This entry was posted in Development. Site – you will n...

blog.infosoft.no

Configuration changes and reducing startup time | Developers corner

https://blog.infosoft.no/blog/2015/08/28/configuration-changes-and-reducing-startup-time?share=email

Configuration changes and reducing startup time. As some of you might know the configuration system in InfoSystems suite is quite flexible, and by now it has a lot of configurations. A little over 1000 configuration options in total, some are more relevant than others by now. The system as it is currently, is basically an evolution of the system that existed in the old VB6 suite of application (now dubbed. 8211; meaning the design is roughly 20 years old! Title based configuration values. Depending on th...

blog.infosoft.no

In pursuit of “better” software | Developers corner

https://blog.infosoft.no/blog/2016/03/23/in-pursuit-of-better-software?share=email

In pursuit of “better” software. This post is not about features of the application or new shiny things, but rather a description of what we are doing internally to provide you with better/more robust software. The term “better” is of course subjective, but at least then software with fewer errors in it! Errors in the wild. As mentioned a few times earlier. We hope that this initiative will take care of some of the more difficult and annoying problems that you as users experience. There is a backlog, but...