Beginning of the year we did post our Roadmap and release plan. In accordnace with this we just did finalize and release the spring Release (2020.01.001) of SpiceCRM delivering the majority of the planned features.
With the new Release we made major changes to the various forms of the List VIew. The standard list now allows free resizing, more flexible handling of Filters, Multiple Column sorting, Geo Search and much more. Also the Kanban Board did get a major rework allowing easy drag and drop, hidden Buckets (for e.g. closed Opportunities as in teh Screenshot below). New Types of Vies (e.g. Maps based) did not yet make it into thsi releae but will follow soon in a release targeted for end of April.
Another big effort has been completed in its first phase which is the port of our well known reporting engine from the backend UI on to the new Frontend. This now allows easy creation of reports in an intuitive UI for the end user with all the capabilities we built over the last years into our reporting Engine. It also marks a further milestone in the port of the complete legacy sugar based backend to our new UI.
We already did publish a short youtube Video on the fast and easy way to generate reports and analyse all the data that resides in your CRM system. The video can be found on Youtube following this link.
There is of course a lot of further things that happend. We added new Features supporting agile project management following the SCRUM Methodology, took further steps to complete the quote to order to invoice process, further enhanced the service processes and much more.
find below the complete Release Notes.
The Release in Details
1000328: Reports Designer
1000354: FTS sort aggregate bucket values by _key
1000382: Sort Hook for get_linked_beans
Sometimes list shall be sorted by a non-db field. This is now possible with new method Link2::processSortHook() .
sort_array parameter now accepts additional key 'sorthook' containing an array with sortfield and optionally sortdirection.
1000375: Bug Fix: Duplicate Output Template
Output Templates module has the field "module_name" in its vardefs definition, which defines the module where the Output Template can be used.
This field is an already existing variable in sugar bean which is used to tell which bean should be cloned, but when the field "module_name" is set in OutputTemplate, it overrides the variable in sugar bean, which leads to a cloning failure.
In sugar bean, The variable "module_dir" is used instead of "module_name".
this fix should not have any side effects, as long as all extended beans has the variable "module_dir" set.
1000366: SalesDocs refactoring
1000365: Move ProjectActivityDashlet Component to modellist.service standard
1000359: New front-end module for SpiceAttachments
1000333: Improved release process
Additional variables in back-end for ChangeRequests and Release modules are needed. Additional UI configs to be retrieved with "deployment" package.
1000358: New field to manage files from a bean
- should look like "parent" field
- it should be possible to upload and remove files from a bean
1000343: FTS enrich bean data for indexing
- It should be possible to create new actionsets
- Existing actionsets should be able to be copied
- The configuration of the items should be dynamically visible and editable
- The view should be based on the familiar Fieldset Manager