Page 2 of 2

Re: Automatic Counter

PostPosted:Tue Dec 06, 2011 6:00 pm
by jllort
1- You should use metadata to store account number if you want to use search engine ( that could solve some part of the problem ) in other side you need to expand columns with it ( it's in my rodmap and I'll doing ... but I'm still waiting for GWT reaction if they decide to change the actual table for some one with column resize feature, now not exists in GWT trunk this kind of feature and it's a great limitation ).
2- No there's no extension to solve in this way. But I've got in mind like I said before add this feature ( mapped columns with metadata values ), that will be some kind of configuration in profiles or similar. Really my actual problem is on GWT table implementation, and I've decided to be 2-3 months in stand by, waiting for it.

Re: Automatic Counter

PostPosted:Wed May 09, 2012 4:45 pm
by dzikus
johnorange wrote: B. May I suggest you move this thread to the Board index ‹ OpenKM Developers ‹ Customization & Improvements. It is more related to that section. Also, I noticed there are other people interested in the matter.
Hello, is there any document describing what You did? I read all thread but scripting is stoping me.

Best regards.

Re: Automatic Counter

PostPosted:Sat May 12, 2012 6:22 am
by jllort
The code is about metadata that will be used on GWT ( frontend ) to be shown in a new document properties tab. For creating a new tab take a look at http://wiki.openkm.com/index.php/Frontend_extensions ( TabDocumentExtension ).

If you want this value searchble from search engine, then I suggest other option, work with metadata, generate new number ( value ) with database metadata but store value in property group too ( then will be searchable ).