Just posting some ideas, related to numerous issues I ended up having while attempting integrations:
#1: Make it easier to find out which platform we are on. Almost all the online documentation was for the v2 API, and when I finally implemented it, the only clue that I was on the wrong track was that it responded that the company could not be found in the database!
#2: Make sure older documentation says somewhere that there is a new version of the API
#3: Document some of the weirder parts in particular. For example, when you are filtering on a report, in order to filter on a date range, you have to add the date filter three times: once blank, once for the start range, once for the end range. Nobody is going to guess this :)
#4: Have the ability to talk to the API using WCF (Add Service Reference instead of the resoundingly deprecated Add Web Reference). WCF has been around ever since .NET 4.0, and the 2.x web service calls from C# that Replicon supports natively are deeply hidden in a "compatibility" section. It seems like WCF should be able to talk to it, but that it may require either a special example (for the pre-authentication support, for example) or some tweak in the Replicon API security to make it happier to talk to WCF.
That's... all I had for now :)
-- Ritchie Annand
#1: Make it easier to find out which platform we are on. Almost all the online documentation was for the v2 API, and when I finally implemented it, the only clue that I was on the wrong track was that it responded that the company could not be found in the database!
#2: Make sure older documentation says somewhere that there is a new version of the API
#3: Document some of the weirder parts in particular. For example, when you are filtering on a report, in order to filter on a date range, you have to add the date filter three times: once blank, once for the start range, once for the end range. Nobody is going to guess this :)
#4: Have the ability to talk to the API using WCF (Add Service Reference instead of the resoundingly deprecated Add Web Reference). WCF has been around ever since .NET 4.0, and the 2.x web service calls from C# that Replicon supports natively are deeply hidden in a "compatibility" section. It seems like WCF should be able to talk to it, but that it may require either a special example (for the pre-authentication support, for example) or some tweak in the Replicon API security to make it happier to talk to WCF.
That's... all I had for now :)
-- Ritchie Annand
Posted 4 years ago
Avinash Iyer, Official Rep
