• OKM 4.1 PropertyGroups issue

  • OpenKM has many interesting features, but requires some configuration process to show its full potential.
OpenKM has many interesting features, but requires some configuration process to show its full potential.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
 #5653  by baiki
 
Dear community,

My OKM4.1 installation is mixing up the PropertyGroups entries once I hit "update". The sort order seems to have a problem. Have a look:
Screenshot-1.png
Screenshot-1.png (19.04 KiB) Viewed 2331 times
Screenshot-2.png
Screenshot-2.png (14.88 KiB) Viewed 2331 times
Screenshot-3.png
Screenshot-3.png (14.58 KiB) Viewed 2331 times
Here my related files:
PropertyGroups.xml
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE property-groups PUBLIC "-//OpenKM//DTD Property Groups 1.0//EN"
                                 "http://192.168.10.100:8080/OpenKM/dtd/property-groups-1.0.dtd">
<property-groups>

  <property-group label="NAO" name="okg:nao2">
    <input label="NAO_file_number" name="okp:nao2.filenumber" value="NAO-JKO-00334078" />
    <textarea label="NAO_reference" name="okp:nao2.reference" value=""/>
    <textarea label="NAO_reference2" name="okp:nao2.reference2" value=""/>
    <input label="NAO_file_number2" name="okp:nao2.filenumber2" value="N2222224078" />
    <input label="NAO_file_number3" name="okp:nao2.filenumber3" value="N23333334078" />
    <select label="NAO_language" name="okp:nao2.language" type="simple">
      <option label="English" value="English" />
      <option label="Wollof" value="Wollof" />
      <option label="Binary" value="Binary" selected="true" />
    </select>
  </property-group>

</property-groups>
And here my PropertyGroupsBaiki.cnd:
Code: Select all
<okm = 'http://www.openkm.org/1.0'>
<okg = 'http://www.openkm.org/group/1.0'>
<okp = 'http://www.openkm.org/group/property/1.0'>

[okg:nao2] mixin
- okp:nao2.filenumber (string) = '' autocreated
- okp:nao2.reference (string) = '' autocreated
- okp:nao2.reference2 (string) = '' autocreated
- okp:nao2.filenumber2 (string) = '' autocreated
- okp:nao2.filenumber3 (string) = '' autocreated
- okp:nao2.language (string) = '' autocreated
Pre-defined values for fields won't work in my example as well. What did I do wrong?

Cheers,
Baiki
 #5654  by baiki
 
With other field types, same problem:
Screenshodddt.png
Screenshodddt.png (12.19 KiB) Viewed 2329 times
 #5672  by jllort
 
In version 4.1 we've founded there's some bug, reason why default values are not setting by default when you add the metadata.

Tomorrow I'll try your metadata files configuration, to see how after change, the values are bad ordered ( diferent than modification field values )

About Us

OpenKM is part of the management software. A management software is a program that facilitates the accomplishment of administrative tasks. OpenKM is a document management system that allows you to manage business content and workflow in a more efficient way. Document managers guarantee data protection by establishing information security for business content.