What is share-config-custom.xml?

It is the override file that customizes the Alfresco Share UI. The most common use is configuring forms — which properties appear on the create, edit, and view forms for a given content type or aspect, plus their labels and input controls.

Which evaluator should I use?

Use model-type to control both the create and edit/view forms for a type, node-type to target existing nodes of a type, and aspect to add fields when a particular aspect is present. model-type is the most common starting point for a custom type.

What is the difference between field-visibility and appearance?

field-visibility (the tags) decides WHICH fields appear on the form. appearance (the tags) controls HOW each visible field looks — its label, its set/grouping, and its input control template. A field must be shown in field-visibility before its appearance applies.

Where do control templates come from?

Share ships FTL control templates under /org/alfresco/components/form/controls/ — textfield.ftl, textarea.ftl, checkbox.ftl, date.ftl, selectone.ftl, and more. Leave the control blank to use the default control for the property's data type.

Where do I deploy this file?

In a Share AMP/JAR module, share-config-custom.xml goes under src/main/resources/alfresco/web-extension/. Restart Share (or the Tomcat hosting it) for the form changes to take effect.

Wasim's Site

Alfresco Share Form Config Generator

Generate share-config-custom.xml form configuration. Pick a type or aspect, choose visible fields, labels, and control templates, and export the XML.

Form Target

Evaluator

Condition (type / aspect)

Add Field

Field ID

Label (optional)

Control Template (optional)

Set (optional)

Fields (1)

cm:name

"Name"

Generated share-config-custom.xml

<alfresco-config>
  <config evaluator="node-type" condition="my:document">
    <forms>
      <form>
        <field-visibility>
          <show id="cm:name" />
        </field-visibility>
        <appearance>
          <field id="cm:name" label="Name" />
        </appearance>
      </form>
    </forms>
  </config>
</alfresco-config>

Configuring Alfresco Share Forms

Once you've defined a custom content model, Alfresco Share won't automatically show your new properties on its forms — you have to tell it which fields to render and how. That's the job of share-config-custom.xml. Writing the nested config → forms → form → field-visibility / appearance structure by hand is fiddly; this generator produces a valid block from a simple field list.

Pairs With the Content Model Generator

Define your types and properties with the Alfresco Content Model XML Generator, then use the property ids here to surface them on the Share create and edit forms.

How to Use This Generator

Pick the evaluator and condition: e.g. model-type with condition my:document.
Add fields: enter each property id (such as my:invoiceNumber), and optionally a label, a control template, and a set name for grouping.
Copy or download: drop the result into web-extension/share-config-custom.xml and restart Share.

Frequently Asked Questions

What is share-config-custom.xml?: It is the override file that customizes the Alfresco Share UI. The most common use is configuring forms — which properties appear on the create, edit, and view forms for a given content type or aspect, plus their labels and input controls.
Which evaluator should I use?: Use model-type to control both the create and edit/view forms for a type, node-type to target existing nodes of a type, and aspect to add fields when a particular aspect is present. model-type is the most common starting point for a custom type.
What is the difference between field-visibility and appearance?: field-visibility (the <show> tags) decides WHICH fields appear on the form. appearance (the <field> tags) controls HOW each visible field looks — its label, its set/grouping, and its input control template. A field must be shown in field-visibility before its appearance applies.
Where do control templates come from?: Share ships FTL control templates under /org/alfresco/components/form/controls/ — textfield.ftl, textarea.ftl, checkbox.ftl, date.ftl, selectone.ftl, and more. Leave the control blank to use the default control for the property's data type.
Where do I deploy this file?: In a Share AMP/JAR module, share-config-custom.xml goes under src/main/resources/alfresco/web-extension/. Restart Share (or the Tomcat hosting it) for the form changes to take effect.

Official Resources

Share Form Configuration (Alfresco Docs)