Hidden property on HR AddDocument eFile Plugin

[7joeblack8]

Hi,

i premit i'm using Alfresco.

i got a strange problem..i tried the eFile, Add Document PlugIn and it works well.

I define the parent object class, and when i got to choose the folder tree types it shows me all the available keywords.
But when, i'm trying to input all the keywords in the "save" menù (just before the uploading), one of the properties is hidden.

I saw in the Inspecting page of Chrome that this is available in html, but the Element Style has a "display: none". disabling that the "even" row (it could be "odd"…it depends obviously)..the row appears!

anybody could please answer?

i'm getting crazy!

thanks 

[deko]

Hi Black.Jack,

which property is set hidden? Is it a special system property or a custom property defined in your custom data model?

[7joeblack8]

hi depf…

is an extention of the content…as this:

<types>
        <type name="test001:companytest">
            <title>Company Test</title>
            <description>Company Test</description>
            <parent>cm:content</parent>
         <properties>
            <property name="test001:note">
               <title>Note</title>
               <type>d:text</type>
            </property>
            <property name="test001:batch_id">
               <title>Batch ID</title>
               <type>d:text</type>
            </property>
         </properties>         
      </type>   ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

the batch id is visible…the "note" does not….


is note a special property?

[deko]

I can´t imagine why test001:note should be rendered hidden. Have you tried to shift the position in the model, so that Batch ID is the first defined property? Anyway, this should not influence the rendering mechanism.

Do you have fieldcontrols activated in owboostrap.xml? This is a mechanism which could influence the rendering of a property field.

[7joeblack8]

no depf the bootstrap is fine,,,,

i managed to work out declaring every value in a fresh new Edit Property List of the ow record function.

The interesting point is that the famous field is accepted only this way:

"D:test001:content.test001:note"

and it's showed in the upload menu as a great yellow "Post It" box…not as usual field.
Maybe the style of the note isn't accepted or recognized in the rendering for an extended note field?

Now i got another issue: declaring the values, i can't get to show the non-common fields… if i click on a class, in the upload tree choose menu, OWD tells me that a particular property is not of this class (it's of another class…).

  any hint?

[7joeblack8]

One of my staff changed the model without telling me nothing, the plugin works perfectly, sorry depf for disturbing you.

I got only a question: how could i sort the fields in the upload inputing?

If i try an Edit Property List it will oblige me to avoid the particulal properties…

[deko]

You can try <PreferedPropertyOrder>