[Vtigercrm-developers] Vtiger 6 - UIType 10 - Additional filters

[Joe Bordes]

Just FYI and if it helps, we are planning on doing the same thing we 
have been doing for years now: create our modules and extensions to be 
as little invasive to base code as possible, benefiting from all the new 
enhancements as we learn, but if we need to modify the code we will do 
so, mostly informing about it on the trac so it can get better. We will 
distribute our extensions with a patch if necessary and create internal 
branches for our clients which we will keep alive as we go forward.

One last comment, we have a large client base which has no need to move 
up to 6.0, they are very happy with their customization and prefer to 
spend their money on new features they require than having us update. 
Which means that we are going to keep supporting 5.4 for a long time. 
This is what we have dubbed internally as vtLTS (from ubuntu and others) 
=  vtiger CRM Long Time Support.


On 28/01/14 11:01, Richard Hills wrote:
> Thank you Salim. This is exactly what I needed.
>
> Now if only I could override this from within my own module, I am 
> assuming this is not possible so will need to make a decision shortly 
> between either creating a custom vtiger branch (as we did with 5.4) or 
> to simply create our own custom entity modules to use in place of the 
> default modules.
>
> What are other developers out there doing in terms of managing this 
> new version?
>
> Currently we are working towards porting core code hacks through to 
> installable packages, however this is reliant upon us being able to 
> achieve the level of customisation we require within the existing 
> framework, is there any information out there regarding what work is 
> being done to make the system more flexible?
>
> Also, this may have been covered before but what sort of release 
> schedule can we expect from the vtiger team? Knowing this would 
> greatly help me with my decision as to how to tackle upcoming work 
> moving our existing vtiger modifications into the new version.
>
> Sorry for subject break there. Would love to hear some feedback from 
> the rest of you on this list.
>
>
>
> On 28/01/14 18:04, Salim wrote:
>> Please have look on this function/getQueryByModuleField/in module model, You may have to add that if you are using custom module. That what i have done to customize PoupList in Some Module
>>
>>
>> http://trac.vtiger.com/cgi-bin/trac.cgi/browser/vtigercrm/branches/6.0.0//modules/Accounts/models/Module.php#L47
>>
>>
>> On 28 January 2014 05:10, Richard Hills <richard at tw.co.nz 
>> <mailto:richard at tw.co.nz>> wrote:
>>
>>     Thanks Joe
>>
>>     I can indeed render the correct popup list by navigating to the
>>     url with the additional parameters
>>     "search_key=ticketstatus&search_value=open". However this does
>>     not stop the user from using the search box again to reset the
>>     filter (this is not a problem for my implementation however I am
>>     sure it will be for some).
>>
>>     This also does not help with the current Ajax call being made by
>>     uitype 10's which I would prefer users to be making use of over
>>     the popup.
>>
>>     I have had a quick look at the code now and see models/Record.php
>>     function getSearchResult where I was able to add some
>>     customisation (a specific query which sits within a specific
>>     module if statement) to get the functionality I required. However
>>     I believe that there needs to be a better way of doing this.
>>
>>     I would love some feedback from the vtiger team as to wether this
>>     can or can not be achieved within the module framework at this
>>     stage. If not then I will settle for this core hack at least
>>     until I find another reason I require the change and spend the
>>     time looking for an ongoing extensible solution.
>>
>>     Thanks
>>
>>
>>
>>
>>     On 24/01/14 11:49, Joe Bordes wrote:
>>>     If you can get around the spanish, this is how we did it in 5.x:
>>>
>>>     http://crmevolutivo.com/doku.php/es:advancedsearch
>>>
>>>     In case that helps.
>>>     Joe
>>>     TSolucio
>>>
>>>
>>>     El 23/01/14 23:43, Richard Hills escribió:
>>>>     Thanks Jonathan
>>>>
>>>>     I see a getListQuery in the assets module still so it seems
>>>>     likely this is still the correct method.
>>>>
>>>>     I will give it a go and confirm.
>>>>
>>>>
>>>>     On 24/01/14 11:33, Jonathan Sardo wrote:
>>>>>     Hello,
>>>>>
>>>>>     I don't know exactly with Vtiger 6, but with Vtiger 5.4 you
>>>>>     have to edit the function getListQuery() in your file
>>>>>     /modules/ModuleName/ModuleName.php
>>>>>     There you can look at URL parameters ($_REQUEST) to know the
>>>>>     source module (eg. Filter records with status 'closed' only if
>>>>>     the source module is Project) and you can custom the SQL query
>>>>>     as you want.
>>>>>
>>>>>     Regards,
>>>>>
>>>>>     Jonathan SARDO
>>>>>     Images intégrées 5
>>>>>     Tél. 06 99 45 50 47
>>>>>
>>>>>
>>>>>     2014/1/23 Richard Hills <richard at tw.co.nz
>>>>>     <mailto:richard at tw.co.nz>>
>>>>>
>>>>>         I have a custom module using a uitype 10 relation field.
>>>>>
>>>>>         I want to restrict this fields view of the ticket module
>>>>>         so that it will only show tickets with a certain status
>>>>>         (as example).
>>>>>
>>>>>         Can anyone tell me the method with which this can be handled?
>>>>>
>>>>>         Thanks
>>>>>
>>>>>
>>>>>         -- 
>>>>>

-- 
Un saludo
Joe
TSolucio

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140128/67898aa5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4223 bytes
Desc: not available
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140128/67898aa5/attachment.png>