This is funky.
And functional.
And cool!

Much of the SugarCRM software development work we do involves things that we know intimately and doesn't present too much in the way of technical challenges. But recently, when we had two concurrent projects both seeking to use a Portal to manage time in the SugarCRM Calendars, it was new, we hadn't done it before and it presented us with an interesting set of challenges. Some of the challenges were frustrating (The current SugarCRM REST API is too buggy and we had to deprecate to an earlier version to make some of the core solution functionality work) but most were good, strong engineering challenges that our people thrive on.

So now we have two calendar/Portal solutions:

1. For booking Engineers (or other personnel resources). Where Portal users can look at the engineering availability in a defined postcode (zipcode) radius and book an engineer for a home visit. This updates the Calendar in SugarCRM, notifies both parties (customer and engineer)by email, can take payments, triggers workflow, sends reminders by Text message and does all sorts of other funky stuff in SugarCRM. And the customer only sees a simple and friendly website as the user-interface. All the heavy lifting is done by SugarCRM.

2. The second solution is slightly different as the Portal enables Associates to update their availability via the Portal, to be informed of any new requirements that they are being booked for, to manage their diaries and to update Notes in client records. This enables third party Associates to be managed and integrated into frictionless processes seamlesslessly. A SugarCRM user can create a meeting/appointment/requirement for an Associate and an Associates relationship is managed entirely through the Portal. This eliminates the need for licences and training.

We'd be delighted to demonstrate either of these solutions to interested parties.