Product updates, news & miscellanea from your fellow Apollo developers.
This blog has moved! Head to the Building Apollo blog »
Some of our users probably noticed that over the last few weeks Apollo's changelog changed a lot less than usual. If you thought that we were slacking off development, think again: we worked really hard to upgrade Apollo so that it used the latest version of Dojo. Here the what happened.
One of the most requested features as far as Apollo's CRM was the possibility to manage contact tags within Apollo.
One typical scenario is having a contact with a mispelled tag: Apollo's auto-completion basically means that that spelling mistake was given as an option to the users every time.
Implementing tag management was trickier than one can imagine. One of the big issues is about visibility of contacts. For example, you might have Contact X with tags A, B, C and Contact Y with tags C, D and E. Assume you only have access to contact X. If you change tag A, it's all fine.
When you work on your car, sometimes you do things that really show: a paint job, shiny new handles, etc: everybody will see them. Some other times, you might add some fancy indicator to the dashboard: every user will notice them. Finally, sometimes you need to work on the engine itself: nothing changes from the outside, and the car is still the same car as ever. However, the engine is happier and will run for longer.
Well, over the last 2 weeks we have been working on Apollo's engine. We are working on the major update of one of the main Javascript libraries we use.
In this blog, I continue my journey in the less-known features of Apollo.
When you reply by email, Apollo does its very best to eliminate any trailing sentences from your email client.
When we designed Apollo, we decided that we could create some really good notification emails without using HTML. There are, no doubts, several advantages when you use text-only emails: spam filters never seem to bother you; there is never a formatting problem (and believe me, different email clients can render things very differently); finally, they are easier to generate.
The only problem, is that they look "plain". Very "plain".
Sometimes you need to create tasks "on the fly", without worrying about logging into Apollo, select the right project, and so on.
So, we added the possibility of adding tasks by email in Apollo. That's right: you can now create tasks by simply writing a new email to the right email address.
You can create both personal tasks, and project tasks.
Writeboards are one of the most exciting features in Apollo this year. As you probably guessed, we use Apollo internally to coordinate Apollo's development and tasks. Writeboards were one of those features that was meant to be developed "slowly", without hurry, as they were quite involved in terms of UI and development.
AS soon as they were available as betas, something predictable but not-so-unexpected happened: we started using them; and no, they weren't polished, tested and fully functional.
Apollo helps you manage your project and contacts, all in one. It's powerful, and highly configurable. Do you want to use Apollo at its very fullest? Then read on.
When you are invited to Apollo and then join, you are assigned an "Applicom account". You can use this account to log into any Apollo workspace you have access to.
We are working hard on improving Apollo more and more. We will make some big announcements in the coming weeks. However, we realise that our users are feature-thirsty, and also work on smaller improvements that will tend to make your life easier -- and more fun. Let's see what they are.
Create a project from a template, without adding entries in the activity
A lot of people have very active workspaces. When a project is created using a template, the activity log gets suddenly filled up with a lot of entries.
Hello there,
When we designed Apollo, we always saw the CRM part as a section where CRM users would write notes about their customers and would assign tasks mostly to themselves, with things to do.
However, Apollo is all about cooperation, and we soon discovered that CRM users wanted to work together, assign contact tasks to each other, and talk about those tasks to each other.
This is why we made it possible to subscribe other CRM users to contact tasks:
I am sure this small addi
