Ektron 9.00
Use Smart Form configurations to display, save, and validate the content properly. Smart Form configurations use XML tags (that are hidden from users) and serve content to various presentation devices (PDAs, mobile phones, and so on), which saves users from creating duplicate content. An XML schema validation ensures the accuracy and format of your Web content, which reduces review and revision time.
Prerequisite
Only members of the Administrators group or those defined in Manage Members for Role: Smart Forms Admin screen can create Smart Form configurations.
Ektron Smart Forms provide the following benefits:
The following are examples of industries that can benefit from XML Indexing.
You should use XML content whenever possible because of the following advantages.
To access the Smart Form section of the Workarea, go to Settings > Configuration > Smart Form Configuration. The View Smart Form Configurations screen appears.
When you click a Smart Form configuration to view its information, you can do the following:
If the Smart Form configuration was created using external XML files (instead of the Data Designer), the following information also appears:
NOTE: If no edit XSLT is specified, the Edit Data Design option is enabled in the toolbar.
The display information tab lists the XSLTs that are used when displaying XML in the respective environment.
NOTE: When a Smart Form configuration is created using the Data Designer, a default display XSLT is also created which looks similar to the edit XSLT created in the editor. This default XSLT can be applied to the XML content.
An asterisk (*) denotes a Smart Form's default XSLT.
The Preview tab displays the XSLT applied to the editor when XML content is created. This is the XSLT that was created for the Smart Form configuration.
If you need to make major changes to a Smart Form configuration, copy it and modify the copy so that you do not affect the content controlled by the original configuration. To copy a Smart Form:
A verification button () appears to the right of some fields on the Add Smart Form screen. After you identify an XSLT or schema, you can click this button to verify that the file exists in the location specified and contains well-formed XML.
NOTE: The XML Verification feature does not validate the contents of the XML file.
Possible results when clicking the verification button:
You are ready to assign the Smart Form configuration to a folder or content item. See Assigning a Smart Form Configuration to a Folder for more information.
NOTE: If you want users to insert Smart Form information using eWebEdit400, you cannot create or edit Smart Forms using external files. However, you can access eWebEdit400's source view, paste the external file's XML, then return to design view.
To add a Smart Form configuration using external XML files:
General Information
Editor Information
Validation Information
Display Information
NOTE: When a Smart Form configuration is created using the Data Designer, a default XSLT is created based on the configuration. To learn about modifying the packaged XSLT, see Editing a Smart Form Configuration’s XSLT.
For each field on the screen:
Ektron provides several options that let you insert or edit fields in the editor. Each field type is described below.
NOTE: For information about these data field types, see Using Data Field Types.
IMPORTANT: You can place content from folders of the following types on a Smart Form: standard, root, site, blog, and eCommerce catalog. You CANNOT place content from Community, Discussion Board, or WebCalendar folders on a Smart Form.
- <root> - <Information> <LastName /> <FirstName /> <MiddleName /> <Gender>male</Gender> <Address /> <city /> <state>MA</state> <Zip /> <SSN /> <BDate /> <HomeTel /> <WorkTel /> <x-ray /> - <Dental_Insurance> <Field1 /> <OtherInsurance>N/A</OtherInsurance> <Account_Number>N/A</Account_Number> </Dental_Insurance> <medication /> <lastAppointment /> <clincal /> </Information> </root>
<xs:schema elementFormDefault="qualified" attributeFormDefault="unqualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="root"> <xs:complexType> <xs:sequence> <xs:element name="Information"> <xs:complexType> <xs:sequence> <xs:element name="LastName"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:minLength xmlns:xs="http://www.w3.org/2001/XMLSchema" value="1" /> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="FirstName"> <xs:simpleType> <xs:restriction base="xs:string">. .. ..
<fieldlist> <field name="LastName" datatype="string" basetype="text" xpath="/root/Information/LastName" title="Last Name">Last Name</field> <field name="FirstName" datatype="string" basetype="text" xpath="/root/Information/FirstName" title="First Name">First Name</field> <field name="MiddleName" datatype="string" basetype="text" xpath="/root/Information/MiddleName" title="Middle Name">Middle Name</field> <field name="Gender" datatype="choice" basetype="text" xpath="/root/Information/Gender" datalist="IDAPK3KC">Gender</field> . .. .. ..
<indexable> <xpath type="string">/root/Information/SSN</xpath> <xpath type="string">/root/Information/HomeTel</xpath> <xpath>/root/Information/WorkTel</xpath> </indexable>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" omit-xml-declaration="yes" indent="yes" encoding="utf-8" /> <xsl:strip-space elements="*" /> <xsl:variable name="ektdesignns_fieldlist" select="/*/ektdesignpackage_list/fieldlist" /> - <xsl:template match="/" xml:space="preserve"> <p> </p> - <fieldset id="Information" title="Demographic Information"> <legend>Patient Information</legend> - <div> - <p> <strong>Last Name</strong> <xsl:text> </xsl:text> <xsl:value-of select="/root/Information/LastName" /> <strong>First Name</strong> <xsl:text> </xsl:text> <xsl:value-of select="/root/Information/FirstName" /> .. .. ... ..
Buttons at the bottom of the Data Designer screen let you edit the content several ways.
To edit any field's properties, select it, right click the mouse, and select Field Properties.
You also can use Ektron’s rich formatting capabilities to design the screen. For example, you can format text, and use tables, images and hyperlinks to guide the user through the data entry process.
The following example shows how to create a simple data entry screen that has a group box with 2 text fields and a choices field.
Prerequisite
You must be a member of the Administrators group or a Smart Form administrator. See Also: Defining Roles
Sample Smart Form
. The screen refreshes and the editor appears.Address
in the Descriptive Name, Field Name, and Caption fields and click OK. The Address group box appears on the form.Street:
" then click Text Field (). Street
in the Descriptive Name, Field Name, and Tool Tip fields and click OK. The text field box appears on the form inside the Address group box.City:
" then click Text Field (). City
in the Descriptive Name, Field Name, and Tool Tip fields and click OK. The text field box appears on the form inside the Address group box.:
" then click Choices Field (). State
in the Descriptive Name, Field Name, and Tool Tip fields.You can specify a field or group of fields to appear on a Smart Form configuration only under certain conditions. For example, a Winter outdoor image does not appear until November, and drops off on April 1. As another example, one group of fields appears if the user is using a mobile device (such as a smart phone), and a different set of fields appears if the user is not on a mobile device.
$deviceConfiguration = 'Smart Phones'
not($deviceConfiguration = 'Smart Phones')
$currentDate >= '2011-01-01'
$userId != '0'
Use xpath to build the expression. For example, $deviceConfiguration = 'Smart Phones'
. You can click View Data as Index () to see the configuration's xpath structure.
NOTE: Developers can modify the examples by editing workarea/ContentDesigner/ConditionalExamples.xml
.
The expression looks like this: $deviceConfiguration = 'Smart Phones'
Every Smart Form configuration has a packaged XSLTExtensible Stylesheet Language Transformations, which is a default XSLT created from the configuration’s display information. To modify the Smart Form’s appearance:
.xslt
extension to your site root/xmlfiles
folder. You can edit the custom XSLT at any time. The changes immediately affect the appearance of the Smart Form on your website. So, the XSLT is quite different from other aspects of the Smart Form configuration, which generally cannot be edited for existing content.
To view a Smart Form's XSLT, click (). The View XSLT screen appears. You can use this information to create your display XSLT.
If you break inheritance on the Smart Forms tab of a folder properties screen, you can select the Smart Form configurations to be assigned to content in the folder.
You may delete a Smart Form in the same way that you delete other content. See Deleting Content.
You can delete a Smart Form Configuration only if no content is assigned to it. If no content is assigned, click Delete () to delete a configuration.
If content is assigned, you must first delete all assigned content.
Prerequisite
You have permission to delete the assigned content. See Also: Managing Folder and Content Permissions
XML indexing lets site visitors search XML information collected from Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input.s and view the results. The results appear as a list of topic titles, optionally followed by the content summary. The Ektron Windows Service manages the background processing that creates XML indexes. See Also: Handling Background Processing Functions with the Ektron Windows Service.
There are 2 ways that XML indexing can make XML content available to your site visitors.
You can choose the XML fields to index with the Data Designer. You can also validate those fields to be numbers, dates, Boolean, or string values. After you identify fields to be indexed, a search dialog is created. Where appropriate, the dialog automatically populates drop-down lists from the indexed data.
To create a search:
IMPORTANT: If a Smart Form configuration field's xpath exceeds 64 characters, Microsoft Search Server 2010 cannot search it. So, if you need to index such a field, reduce the length of its xpath to less than 64 characters.
To see a configuration's XPaths, click the Display Information tab.
NOTE: To select more than one value on the search screen, the user holds down the Ctrl key while selecting additional options.
If you choose NoSelection in a search field, the search disregards that field when compiling results. However, you must select a value (or range of values) in at least one field to get results.
NOTE: The IndexSearch server control has been deprecatedfunctionality that is being phased out and may become invalid or obsolete in future versions; migrate to the current and recommended version.. Use the XML Search server controls to display a Smart Form’s search screen on a Web form.
Validation ensures that the user completing an XML form enters the right type of data. You can decide if the user’s input should be a number, boolean, date, string, zip code, and so on. If you do not specify type attributes using validation data, the field is a string.
Validation is especially important when users search XML data, because it helps the search find the correct information. For example, if a field collects a zip code but you set its type to plain text, a user completing the form can insert anything into the field. If the user inserts the letter “o” instead of the number zero (0), the field accepts that input but the search will not find that record. On the other hand, if you set validation to zip code, the user can only insert 5 or 9 digits—any other entry is rejected.
There are 2 ways that XML Indexing can make XML content available to your site visitors.
NOTE: The Ektron Windows Service manages the background processing that creates XML indexes. See Also: Handling Background Processing Functions with the Ektron Windows Service.
Ektron content has a Content Searchable check box, which must be checked if you want the Index Search to find Smart Form content. See Also: Making Content Searchable
XML Indexing allows multi-dimensional searches on all types of XML data.
NOTE: Choices field values can consist of single letter.
alt
or src
attribute valuehref
attribute valueFor every search field, NoSelection is a value. If this is chosen, the search disregards that field when compiling results. However, the user must select a value (or range of values) in at least one field to get results.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
For Smart Form fields to searchable, they must be stored as elements not attributes. If you are upgrading to version 7.5 or higher, inspect your Smart Forms and change field properties as needed so they are stored as elements not attributes.
XML indexing allows multi-dimensional searches on all types of XML data.
alt
or src
attribute valuehref
attribute valueIf a Smart Form configuration field's xpath exceeds 64 characters, Microsoft Search Server 2010 cannot search it. So, if you need to index such a field, reduce the length of its xpath to less than 64 characters. To see a configuration's XPaths, click the Display Information tab.
If the standard validation options do not provide the flexibility you want, use the custom validation feature to ensure the following about the user’s input.
NOTE: Your system administrator may customize the choices.
NOTE: Your system administrator may customize the choices.
If the user’s response fails to meet the criteria, you can compose an error message that appears when that happens. Your system administrator determines if a user can save the invalid data.
As an example of custom validation, assume that a field collects telephone numbers, and you want to make sure the user enters 10 digits. To accomplish this:
string-length(.) <= {X}
appears in the Condition field.
string-length(.) = {X}.
{X}
with 10. Now, it looks like this: string-length(.) = 10.
must be 10 digits
. Your screen should look like this.You can insert the following data field types into a data entry screen.
IMPORTANT: For Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input. fields to searchable, they must be stored as elements or attributes not content.If you are upgrading to version 8.5 or higher, inspect your Smart Forms and change field properties as needed so they are not stored as content.
Use a calculated field to perform a calculation based on values in other fields. For example, if your screen collects mortgage information, you could create one field to collect the mortgage and interest payment and another to collect taxes and insurance. The calculated field could sum those 2 numbers and display the monthly payment.
You can validate a calculated field. For example, you can require a positive number between 100 and 1,000.
Calculated fields are display only.
IMPORTANT: If a field is referenced in a calculation, use validation to require a value. This forces the user to enter a number used in the calculation.
If you assign any value other than No validation, the field is surrounded by red dashes in Data Entry mode. If the user’s response does not meet the validation criteria, the field remains surrounded by red dashes. Your system administrator determines if a user can save a screen with invalid data.
NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.
{X} * number({X}<= {Y}) + {Y} * number({X}>{Y})
, you only need to replace the first occurrence—the editor replaces subsequent occurrences for you.NaN
appears in the field. (NaN
stands for “not a number.”)Infinity
appears.sum()
and count()
, all values with the field name are considered. For example, a document includes 3 books whose prices are $10, $20 and $30. In this case, sum
’s value is $60.<price>
, its value is $10.{X} * {Y}
with ../price * 1.15
.(round(Field1 * 0.80) + (1 div Field2)) - 2
.concat( title, ' ', givenname, ' ', familyname)
, which could produce “Dr. Jonathan Smythe”.In this example, you must place the third field below or to the right of the first 2 fields. Calculated fields that are defined later in a document do not appear in the Select Field or Group dialog.
These formulae appear in the Examples drop-down list of the Calculated Field dialog. Your system administrator can customize the list.
{X} + {Y}
{X} - {Y}
{X} * {Y}
format-number({X} div {Y},'0.###')
format-number({X} div {Y},'#0%')
{X} * (number({X} > 0)*2-1)
{X} * number({X} <= {Y}) + {Y} * number({X} > {Y})
{X} * number({X} >= {Y}) + {Y} * number({X} < {Y})
({X} - {Y}) * number(({X} - {Y}) >; 0)
{X} * ( {Y} * number( {Z} ='true') + number( {Z} !='true'))
For example, {X}=2 and {Y}=3
round(3.14).
The result is 3.round({X})
ceiling(3.14)
. The result is 4. For negative numbers: ceiling(-3.14) = -3ceiling({X})
floor(3.14)
. The result is 3. For negative numbers: floor(-3.14) = -4floor({X})
format-number({X},'0.00')
sum({X}[text()] | {Y}[text()] | {Z}[text()]))
sum({X}[text()])
For example:
Plain Text Field properties
XML Data
<root>
<Miles>89</Miles>
<Miles>12</Miles>
<Miles>23</Miles>
<Miles>19</Miles>
</root>
Sum(Miles) equals 89+12+23+19=143
Only elements that contain a value are summed. Empty elements are excluded.
format-number(sum({X}[text()]) div count({X}),'0.###')
To continue the example from the Total a list of numeric values field:
Plain Text Field properties
XML Data
<root>
<Miles>89</Miles>
<Miles>12</Miles>
<Miles>23</Miles>
<Miles>19</Miles>
</root>
Average=89+12+23+19=143
divided by the number of values (4)= 35.75
Only elements that contain a value are summed. Empty elements are excluded.
count({X})
To continue the example from the Total a list of numeric values field:
Plain Text Field properties
XML Data
<root>
<Miles>89</Miles>
<Miles>12</Miles>
<Miles>23</Miles>
<Miles>19</Miles>
</root>
Count = 4
translate({X},'ABCDEFGHIJKLMNOPQRSTUVWXYZ','abcdefghijklmnopqrstuvwxyz')
translate({X},'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')
normalize-space({X})
concat('The',' ','XML')
yields The XML.
concat({X}, ', ', {Y})
string-length({X})
Insert a calendar field when you want a Smart Form to include a date field. You may use the current date or click one from a calendar. Because users cannot enter digits, a standard date format is ensured. The date is stored as a standard XML date (in the format yyyy-mm-dd), and localized to the computer of the user viewing it.
NOTE: If you enter a default date, you cannot later remove it. You can change it. If necessary, you can delete the field and enter a new one.
If you check May be removed, when this field appears on a data entry screen, an icon () appears to the left of the field. If the user clicks the icon, a drop-down menu provides an option to remove the field.
If the user removes the field, field name replaces the field on the data entry screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field (see the Use field). So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.
As an example of custom validation, assume a field collects the date when a patient’s health insurance policy expires. You want to make sure the date is later than today. To accomplish this:
Must be after today
. Your screen should look like this.A Checkbox field is only one character wide and accepts one of 2 possible values: checked or unchecked. For example:
NOTE: The Descriptive Name field only appears on this dialog when you create the Check Box field. If you later try to edit the field, it is not on the dialog. However, you can edit the Descriptive Name text within the editor.
Use a Choices field to give a data entry user several options. For example, you create a Choices field named Interests that lists these options. The data entry user could check the first 2 and leave the third blank.
You can do the following with a Choices field.
List type | Example | Description |
vertical | All choices appear, arranged vertically. | |
horizontal | All choices appear, arranged horizontally. | |
list box | All items appear. The default one is selected when the screen first appears, but can be changed. | |
drop list | Only the top item appears. To its right, a down arrow appears (circled). The user clicks the arrow to display all items and select one. |
music
to be collected when the data entry user selects this item and saves the page, enter music here.NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.
To create your own set of list options, accept the List field’s default value, Custom. Then, enter the list values using the Item List section of the screen.
To indicate an option is the default choice, check the Selected checkbox.
For example, if Interests appears in the Name field, and you want music to be collected when the data entry user selects this item and saves the page, enter music here.
To add a new choice, delete an existing choice, or move a choice up or down within the list, click the menu icon () next to that choice. Then select a menu option.
Although you can create a custom list of choices using the Item List area of the Choices Field dialog, that list is only available in that field of that screen. If you want to insert the same list in another section of the screen or a different screen, you must re-enter all options. However, if you create a list according to the following steps, your custom list is stored in the configuration file (along with the standard choice lists, such as Countries). As a result, any user connected to your server can insert the list into any Choices Field on any screen.
To insert a custom list of choices:
siteroot/workarea/contentdesigner/DataListSpec.xml
.<datalist name="MyNewList"> <schema datatype="string" /> <item default="true" value="Green" /> <item value="Red" /> <item value="Blue" /> </datalist>
NOTE: You can specify a data type of value: string, nonNegativeInteger, date, decimal. You also can specify a default value (as shown in the third line).
You specify the elements of the custom options list described in the configuration data. You can also create a dynamically-populated list from any XML source. The source can be on your server or on a remote website. Follow these steps to add a dynamic data list to the Choices field.
siteroot/workarea/contentdesigner/DataListSpec.xml
.<datalist name="MyNewList"> <schema datatype="string" /> <item default="true" value="Green" /> <item value="Red" /> <item value="Blue" /> </datalist>
<datalist name="MyNewList" src="{url to xml data source}" select="{xpath to data item element}" captionxpath="{relative xpath to data item's display text}" valuexpath="{relative xpath to data item's value}">
IMPORTANT: The datalist name
must match the listchoice data
attribute.
For example
<datalist name="USPS-CA" src="[eWebEditProPath]/uspsca.xsd" select="/xsd:schema/xsd:simpleType/xsd:restriction/xsd:enumeration" captionxpath="xsd:annotation/xsd:documentation"\ valuexpath="@value" namespaces="xmlns:xsd='http://www.w3.org/2001/XMLSchema'" validation="select-req">
In this example, the data list is stored in the uspsca.xsd
file, located within the ewebeditpro
folder. However, it could be in any XML data source.
A Group Box field lets you group related fields together by surrounding them with a box and optionally placing a caption above them. After you insert a Group Box field, to insert other kinds of fields within the box, place the cursor inside the box then select a field type button.
NOTE: The tabular data field type might better accommodate your needs. See Tabular Data .
Grouping fields in Data Entry mode lets you add another instance of a group. For example, if a screen collects information about each telephone call, you can click Insert Below to insert a new group of fields, ready to collect information about the next call.
Use the eyeglass icon to expand or collapse fields within a group.
You also can suppress a group of irrelevant fields. For example, assume a screen includes 2 groups of fields that collect information about hardcover and paperback books. When adding information about a hardcover book, you can collapse paperback book questions because they are not relevant.
If you check May be removed, when this field appears on a data entry screen, an icon () appears to the left of the field. If the user clicks the icon, a drop-down menu provides an option to remove the field.
If the user removes the field, field name replaces the field on the data entry screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field. So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
After you insert this field onto the screen, you can use the editor's formatting capabilities to modify its size, font, color, and other attributes.
NOTE: The Caption field only appears on this dialog when you create the Group Box field. If you later try to edit the field, the Caption field is not on the dialog. However, you can edit Caption text within the editor.
By default, Ektron surrounds your Data Design with <root>
tags. To replace <root>
tags with another element name:
1. After creating a new Data Design screen, insert a Group Box as the first field.
2. In the Group Box dialog’s Field Name field, enter the root text.
3. On the Group Box Dialog box, click the Advanced tab.
4. In the Root tag section, select Use this element as the Root tag and press OK.
5. Place all other screen elements within the Group Box field.
The Advanced tab lets you generate XML microformats made up of standard XHTML tags and attributes that contain a specific structure and values.
For example, the microformat of an event looks like this.
<span class="event"> <a class= "url" href="https://www.lisa.org/events/2006nyc/ package_registration.html?from=fn1206 "> LISA Global Strategies Summit</a> </span>
NOTE: If the element is a group box or table, its type must be Element because it surrounds other elements. If the element is a Rich Area field, its type must be Element or Content.
<Lastname>Rogers</Lastname>
<PtInformation Lastname="Rogers">
</PtInformation>
NOTE: Only one Content type field is valid within a containing field.
<PtInformation>
Rogers
</PtInformation>
By default, Ektron surrounds your Data Design with <root>
XML tags. You can replace the <root>
tags with another element name by following these steps.
The Relevance tab allows a group of fields to appear or disappear according to the value of other fields in the configuration. It appears on both the Group Box and Tabular Data Box dialogs.
Here are some example uses.
Only the following field types can be used in a Relevance condition.
NOTE: If using a Choices field, in the Appearance area of the dialog, you can only choose List Box or Drop Box. Vertical List and Horizontal List are not supported.
NOTE: The location of the Group Box field is independent of the location of the fields to which you will apply conditions.
A checkbox field is checked ({X} = 'true')
, click the check box field whose value must be true
for this group to appear.You should switch to Data Entry mode and test the Relevance conditions.
Assume you want a list of states in the United States to appear only if a user selects United States from the Country field.
To accomplish this:
See Also: Choices
A field has a given value ({X} = 'value')
.IMPORTANT: The text that replaces Value must exactly match the desired value of the selected field.
Use an Image Only field to place an icon on the screen, which the user can click to insert an image into the content. You can insert a default image if desired. To let the user insert any file, such as a Microsoft Word document, use a Link field.
In Data Entry mode, the image’s caption appears, followed by a default image (if you specify one) and this icon:
NOTE: The user can only insert a file whose extension is defined within the <validext>
element of the configdataentry.xml file. Your system administrator can help you do this.
If you check May be removed, when this field appears on a data entry screen, an icon () appears to the left of the field. If the user clicks the icon, a drop-down menu provides an option to remove the field.
If the user removes the field, field name replaces the field on the data entry screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field. So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
<img src=”url” alt=”text” />
for an image.<validext>
tags in the configdatadesign.xml file. For example:<validext>gif,jpg,png,jpeg,jpe,doc,txt
</validext>
NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.
Use a Link field to place an icon on the screen. A user in Data Entry mode can use the icon to link to any Library file, such as a Microsoft Word document or a .gif image file. (You can also use an Image Only field to let the user insert an image. See Also: Image Only )
The File Link field does not let you link to Ektronassetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s.
In Data Entry mode, the file link field’s caption appears, followed by this icon: . When the user clicks the icon, a hyperlink screen prompts you to specify information about the link.
NOTE: Only insert a file whose extension is defined within the <validext>
element of the configdataentry.xml file. Your system administrator can help you do this.
If you check May be removed, when this field appears on a data entry screen, an icon () appears to the left of the field. If the user clicks the icon, a drop-down menu provides an option to remove the field.
If the user removes the field, field name replaces the field on the data entry screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field. So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
<img src=”url” alt=”text” />
for an image.<validext>
element of the configdatadesign.xml file. For example:<validext>gif,jpg,png,jpeg,jpe,pdf,doc</validext>
NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.
A Resource Selector field lets you place elements of Ektron content, taxonomiesa content-level categorization system that uses one-to-many relationships to create a scalable organization of content. A taxonomy lets you create a navigation system that is independent of the folder structure., collectionA list of Ektron content links for display on a Web page.s or folders on a Smart Form. For example, on the following page, content in a selected folder appears.
IMPORTANT: You can place content from these folder types on a Smart Form: standard, root, site, blog, and eCommerce catalog. You cannot place content from Community, Discussion Board, or WebCalendar folders nor PageBuilder pages on a Smart Form.
Each content item in the folder is represented as a hyperlink followed by its summary. A site visitor can click the link to view the content. An alternative display showing hyperlinks only appears as follows.
A Resource Selector field acts like server controla server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified.s that let you place content on a Web page, such as the Content Block and List Summary server controls. The advantages of the Resource Selector field are:
These steps summarize how to use a Resource Selector on a Smart Form.
To a content author, a Smart Form's Resource Selector fields appear as follows.
The upper field lets the author select content (ID 30 is the default), and the lower one lets the person select a folder (ID 36 is the default). To select either one, click the folder to its right, then select. If working with content, the tabs that appear on the dialog are determined when the resource is placed on the Smart Form configuration.
NOTE: If someone changes the title of content used in a Resource Selector field, the title is not updated on the Smart Form. In the illustration, if someone changed the title of content ID 30, you would still see Sample Content Block when viewing the Resource Selector field.
IMPORTANT: You can place content from these folder types on a Smart Form: standard, root, site, blog, and eCommerce catalog. You cannot place content from Community, Discussion Board, or WebCalendar folders on a Smart Form.
These settings affect the content author’s work with this field on a Smart Form in the following way. Assume you set a minimum of 1 and a maximum of 2. After the content author adds 2 content items for this resource selector, the only options are to remove or rearrange fields; you cannot add more.
Use the Type tab to limit the type of content that a content author may choose. It is available only if the Resource type is Content Resource.
NOTE: eCommerce products are also known as catalog entries.
The Configuration tab determines how a content author may select content or a folder on a Smart Form. It is available only if the Resource Type is Content or Folder.
The Appearance tab determines the default appearance of the resource on your website.
The folder’s breadcrumb path appears, as defined on the folder Properties screen’s Breadcrumb tab. See Also: Creating a Sitemap Breadcrumb Trail
This is the only option if the Resource Type is Taxonomy Resource. See Also: Directory
The Tabular data button inserts a table into which you can place other types of fields. It’s similar to a group box but its advantage over a group box is that it lets you place fields in columns. After you insert a table, you can insert an appropriate field type into each column. For example, the Description field type is plain text, while the In Stock? field type is a choice.
If you insert a field into a table and its caption appears to the left of the data entry region, move the caption to the column header.
NOTE: To delete a column, place the cursor in the column, right click the mouse, and select Delete Column. You cannot reduce the number of columns by editing the Tabular Data dialog’s Columns field.
IMPORTANT: Only table cells into which you place a field are available to visitors of your Web page.
If you check May be removed, when this field appears on a data entry screen, an icon () appears to the left of the field. If the user clicks the icon, a drop-down menu provides an option to remove the field.
If the user removes the field, field name replaces the field on the data entry screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field. So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
Tabular data creates 3 levels of XML tags:
To explain how this works, use the following contact list as an example.
When you insert a field into a table, a dialog helps you define the field type. For example, when inserting a plain text field, the Plain Text Field dialog appears. On that dialog, the value of the Phone field defines the tags that enclose that field’s contents.
To continue the example, every contact is represented in XML as:
<Name>John Doe</Name> <Phone>555-1212</Phone> <Email>john.doe@example.com</Email> and <Name>Mary Smith</Name> <Phone>555-8765</Phone> <Email>msmith@example.net</Email>
Each row of the table collects information for one contact. On the Tabular Data Box dialog, the Row Name field defines the XML tag that groups information for each contact. For example, the Row Name field value is Contact.
</AddressBook> <contact> <Name>John Doe</Name> <Phone>555-1212</Phone> <Email>john.doe@example.com</Email></Contact><Contact> <Name>John Doe</Name> <Phone>555-1212</Phone> <Email>john.doe@example.com</Email> </Contact> Contact> <Name>Mary Smith</Name> <Phone>555-8765</Phone> <Email>msmith@example.net</Email> </Contact> </AddressBook>
Use a text field when you want the user to enter a text response.
NOTE: If a plain text field tries to perform a numerical calculation with a value that is blank or contains letters, NaN
appears in the field. (NaN
stands for “not a number.”)
If a plain text field tries to divide by zero, Infinity
appears.
The following capabilities are available with a text field.
New York
as the value.If you check May be removed, when this field appears on a data entry screen, an icon () appears next to the field. If the user clicks the icon, a menu provides a remove option.
If the user removes the field, field name replaces the field on the screen to indicate that the field was removed and can be re-added if necessary. For example, if the field’s display name is street address
, and the user removes the field, appears in place of the field.
NOTE: The menu icon () can also indicate that the user can add instances of a field (see the Allow field). So, if a field is required, the icon could appear but omit a Remove option.
IMPORTANT: Do not insert a calendar field into a Smart Form that allows multiple entries (using the Allow more than One option on the dialog). If you do, you cannot search the Smart Form using that field.
If the user entering data clicks , a menu appears, which lets the user click Duplicate to add instances of the field to the screen.
NOTE: The menu icon () can also indicate that the user can remove a field (see the Use field). So, even if a field allows only one instance, the icon could appear but the menu would only display Remove.
ek_EditControlWin
key (for Windows computers) or the ek_EditControlMac
key (for Apple computers). Or, if UserPreferred
is the web.config
value, the author uses the editor selected in the user profile.<p>
tags around a single line of text. Uncheck this box if you want the editor to strip <p>
tags from a single line of text.NOTE: This checkbox has no effect if text that allows rich formatting consists of more than one line.
Sample Results
Checked: <p>Here is sample text</p>
Unchecked: Here is sample text
If you assign to this field any value other than No validation, the field is initially surrounded by red dashes in Data Entry mode. If the user’s response does not meet the validation criterion, the field remains surrounded by red dashes. The system administrator determines whether or not the user can save an invalid document.
NOTE: The configuration data controls a command's appearance on the toolbar and on the Data Style dialog. For example, if <button command="cmdfontname" />
is removed from configdatadesign.xml, it disappears from the toolbar and the Data Style dialog.