I'm looking into possible uses for Sugar Portal, but can't seem to find a definitive answer on what all I can do with it. Can I choose certain modules to use or is it confined to a select list?
Hi Adam Adkins
It is possible to publish on Sugar Portal other built in modules and custom modules as well. It requires some ugrade safe coding.
We have done it before, let me know if we can contribute to your project somehow.
Can you give an example of the other modules you've done this with? I think we'd be thinking (maybe) contacts and opportunities.
We improved the Portal in order to behave as a PRM (Partner Relationship Management), that means, we published into Portal Opportunities, Leads and Activities. We also published into Portal home page a feature which render a set of Reports Dashlets just like you can customize in your home page. These Dashlets can be defined by SugarCRM Users in the profile of the Contact which authenticates on Portal, that means, different Contacts may have a different set of Dashlets into your Portal home page.
Yeah, that sounds fairly close to what we might be envisioning. What kind of manhours did this take? Just curious.
The initial implementation toke around 200 hours. Now, that we have a working, installable and upgrade safe solution, we can deploy it much faster!
Feel free to contact me if you are interested on our services.
Standard modules available are Cases, Bugs and Knowledgebase as well as a Profile section which links to the logged in user's contact details. Communication is carried out using the Notes module (not Email). We are completing our implementation at the moment.
Area that really needs improvement is providing the logged in user the ability to create filters and customise views.
You will need to use Workflow and/or Advanced Workflow to notify customers/users of updates as they occur and for follow ups when action has not occurred. Most likely need a Workflow to handle Portal Registrations as well. There is a limitation in Advanced Workflow of not being able to notify recipients (as distinct from users which works fine). This means you need to use Workflow to notify recipients until Advanced Workflow is improved in that regard.
Thanks for the headsup. We're still kind of working through exactly what we'd want, as I'm sure you can imagine.
Is there a way to automatically assign the lead its username and password without going in and manually entering it? Can you do that through workflow as well?
When a person goes to the Portal Login screen and "applies" to become a portal user a Lead is created in Sugar with a specific Lead Source. We use Advanced Workflow to notify the person who is responsible for actioning the request. (We will probably end up using a Self Service Process for a small team to look after this in the future). As we need to validate that the application is valid and authorised, we do not automate after that, we convert the Lead (quite often the Contact exists and that all works fine). We haven't looked at whether we could have an additional workflow (or an add on to the existing workflow) to also set Portal Active, create a User Name and a Password. I expect that setting Portal Active and creating a user name should be fairly straight forward, but creating the password might be more difficult as it involves a password and confirm password process.
Sorry that I haven't given a complete response as we have not tested that aspect.
Retrieving data ...