Bo,
> Q: One thing that would REALLY help me sell Eventum is
> the ability
> to connect to an external DB for accessing customer
> usernames/id's etc.
This is already possible with the Customer API. All you need to do is
create a new Customer Backend (which is just a PHP script), and follow
the API to connect Eventum to a third-party CRM system.
See documentation on /path-to-eventum/docs/Customer_API.html.
> Q: It would be nice to be able to assign resolutions on a
> per project
> basis. It seems they are all global right now. My tech
> support list, for
> example, doesn't need "fixed", "not a bug", and etc., but
> would like to
> have "operator error", and such.
>
That's true. I'll add that to our TODO list. Thanks for the suggestion!
--Joao
| Thread |
|---|
| • custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Re: custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Re: custom fields, required fields, documentation | Bryan Alsdorf | 8 Jun |
| • Re: custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Status on Close? | Bo Gusman | 8 Jun |
| • Re: Status on Close? | Bryan Alsdorf | 8 Jun |
| • Re: custom fields, required fields, documentation | Bryan Alsdorf | 8 Jun |
| • Configuration Selection? | Bo Gusman | 8 Jun |
| • Integration with customer DB for names/addresses/customer ID | Bo Gusman | 9 Jun |
| • RE: Integration with customer DB for names/addresses/customer ID | Joao Prado Maia | 10 Jun |
| • Re: Configuration Selection? | Bryan Alsdorf | 13 Jun |
| • RE: custom fields, required fields, documentation | Joao Prado Maia | 8 Jun |
| • RE: custom fields, required fields, documentation | Joao Prado Maia | 8 Jun |