We have installed some upgrades including the followings:
- Paypal payment system – we had some performance issues.
- Task template names have been sorted in alphabetical order (everywhere).
- Task template delete bug fixed – sometimes you couldn’t delete one or more task templates (Thanks to Robert Andrescik)
- Custom field empty filter bug fixed – 0 results shown when a CF filter was set to empty (Special thanks to Florent Cailly, Asim Qureshi, Mick Page)
- Much more longer authentication ticket lifetime – you won’t be logged out when you leave your web browser open for hours
We would like to thank you for the feedback, they were very very helpful.
Few months ago we had to eliminate the
Parties Parties.ListPartiesByTags(IEnumerable<int> tagIDs, int pagingOffset = 0) method from our SDK, because Highrise API didn’t support the underlying REST call anymore. We were very happy when we realized that Highrise can filter contacts by multiple tags (see: http://help.37signals.com/highrise/questions/57-how-do-i-search-by-multiple-tags), so we were hoping we could enable again the involved method.
When you look at the URI in the browser when you searching by multiple tags, you may see something similar: https://somedomain.highrisehq.com/tags/1963039,1973268,1969549,1984865,1690134,1963033
And not a rocket science to get the xml representation of this call: https://somedomain.highrisehq.com/tags/1963039,1973268,1969549,1984865,1690134,1963033.xml
The only problem is Highrise limits the number of combined tags… boom. Only the first 5 parameters matters and the followings will be ignored. Of course we will create another ListPartiesByTags() upon this behavior.
We are proud to say that WLH supports contact search by unlimited number of tags.
Sometimes a Highrise account has thousands of contacts and the duplicate analyzer must check all to find similar emails and names. So this process may need a few minutes. We had a case when 18.000 users were in a Highrise account and more than 6 minutes needed to show the result (there was about 1000 duplicates). As you know every web-based systems have request timeout, WLH had 1,5 mins. It wasn’t enough in the previous example, so we increased it up to 10 minutes.
And we know it’s very time consuming to eliminate all the duplicates one bye one (in Highrise) . And sometimes you have to execute the same search again and again – for example when you close your web-browser. So we help your work to store the duplicate search results after the asynchronous process completed. Than you can reload them any time.
(Search result attached to the user who executed the query, so it’s secure.)
Thanks to Nick Wolf
As you know, our next step is RECURRING TASKS, many of you asked for it, so let’s do it.
Being a complicated issue, we introduce our concept first and would like to encourage anyone to comment at this stage.
It is planned to work the same way as task templates already available in WLH. You start by creating a task in WLH, then you set the recurrence type and a stop date. When finished, your set of recurring tasks appear in Highrise. Simple as that:
It will look like this:
We have created a weekly recurring task that ends on 1st of June – it’s 9 tasks in a row. Now you have to be aware of few important factors. If using incorrectly, you may create a bunch of unwanted tasks. We definitely would like to avoid a situation when you have to delete a series of tasks manually, one-by-one. So we have added the ability to batch delete these tasks, in case you wish to.
As you can see, we try to think one step ahead. Please help us on these 2 issues:
- At this moment recurring tasks is only designed to create tasks for ourselves. Would you like to create recurring tasks for your clients and customers?
- Should task templates and recurring tasks be implemented as one step or leave them separately?