|
|||
|
|||
I recently took the CommitCRM plunge. While I've been very happy and in gathering a lot of the information CommitCRM can track I've noticed things like lapsed renewals which make CommitCRM worth it by itself, I have also noticed several shortcomings. Some of these may be on the dev team's radar or there may be workarounds (which I'd love to hear about) but I wanted to list them here so they can be considered for future releases:
General
Activity Templates
Tickets
Assets
Calendar Sync
GFI MAX RMM Integration
If anyone has any workarounds to anything on my list or suggestions for my usage, please feel free to chime in. |
|
|||
|
|||
Thank you for posting this and for suggesting different items like the password manager, formatting, asset related items and more. Please find a few notes related to GFI MAX, the other items will be considered.
Quote:
Quote:
|
|
|||
|
|||
I appreciate your ear (or eyes rather). I did not know I could link multiple GFI assets to a single CommitCRM asset so that definitely helps.
I also agree that linking multiple assets could be difficult. However, I think perhaps the smallest step (and most beneficial) would be a way to check off all the GFI assets you want to create new CommitCRM assets for and then auto create them in CommitCRM instead of one-by-one creating new assets for each GFI asset. I envision clicking a batch create new assets button, and a pop-up form that has drop downs for vendors for each of the checked items. Most of the time (for me at least), my assets originate in GFI first and would not be in CommitCRM yet (new GFI assets are usually new managed services customers being brought online - things I wouldn't have inventoried, entered or seen). My problem is less with matching multiple GFI/CommitCRM assets at the same time - more with entering new GFI assets that don't exist. Thanks again for the advice and considering my list though! |