Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Product version: |
EPiServer Connect for Sharepoint 2007 version 2.0 |
---|---|
Document version: |
1.0 |
Document last saved: |
25-11-2008 |
This tech note describes how todefine a separate File Summary configuration for each virtual path provider using the customFileSummary parameter when developing with EPiServer Connect for SharePoint 2.0.
The EPiServer Connect for SharePoint module contains a custom file summary (WSSFileSummary.config) for the virtual path provider with SharePoint specific field definitions, it can be found in the root folder of the EPiServer CMS Web site.
By using the file summary configuration file the user can define which properties should be available for edit and advanced search functionality for this virtual path provider. Users can only use the following SharePoint data types:
The form for Meta data editing can be configured in the FileSummary.config file - an XForms file with HTML markup and XForms data fields. The list of data fields declared in the model/instance section is as follows:
<model>
<instance>
<Title />
<TestText />
<TestChoice />
<TestRadio />
<TestCheckBox />
<TestTextArea />
<TestBool />
<TestDate />
<TestNumber />
</instance>
</model>
Each data type can be represented by different xforms controls. Reference to the data field should be declared in the ref control attribute. Here are examples of controls for different data types:
<xforms:input ref="TestText" value="" id="fieldTestText" size="40" class="commonInput" />
<xforms:select1 appearance="minimal" ref="TestChoice" id="fieldTestChoice" >
<xforms:item>
<xforms:label>Choice #1</xforms:label>
<xforms:value>Choice #1</xforms:value>
</xforms:item>
<xforms:item>
<xforms:label>Choice #2</xforms:label>
<xforms:value>Choice #2</xforms:value>
</xforms:item>
<xforms:item>
<xforms:label>Choice #3</xforms:label>
<xforms:value>Choice #3</xforms:value>
</xforms:item>
</xforms:select1>
appearance="full"
<xforms:select appearance="full" ref="TestCheckBox" id="fieldTestCheckBox" >
<xforms:choices>
<xforms:item>
<xforms:label>CheckboxChoice#1</xforms:label>
<xforms:value>CheckboxChoice#1</xforms:value>
</xforms:item>
<xforms:item>
<xforms:label>CheckboxChoice#2</xforms:label>
<xforms:value>CheckboxChoice#2</xforms:value>
</xforms:item>
<xforms:item>
<xforms:label>CheckboxChoice#3</xforms:label>
<xforms:value>CheckboxChoice#3</xforms:value>
</xforms:item>
</xforms:choices>
</xforms:select>
<textarea ref="TestTextArea" id="fieldTestTextArea"></textarea>
<xforms:select ref="TestBool" id="fieldTestBool" appearance="minimal">
<xforms:choices>
<xforms:item>
<xforms:label>Test Bool</xforms:label>
<xforms:value>True</xforms:value>
</xforms:item>
</xforms:choices>
</xforms:select>
<xforms:input ref="TestText" value="" id="fieldTestText" size="40" class="commonInput" />
Note that the tags are identical as for the simple text string values.