The Settings tab provides a place for managing XML output data for all types of data sets, as well as setting up access and themes for Form data sets.
XML Output Data
XML Target Namespace
When multiple Experlogix Documents (XD) data sets are associated with a template that originates from an external system (such as Smart Flows), a Target Namespace must be defined for each data set.
Configure this field to define a unique identifier for your data set. This ensures your data is correctly recognized by external systems and remains distinguishable from other schemas. The target namespace acts as a unique ID, preventing naming conflicts and ensuring data integrity.
By default, the system doesn't generate any namespace.
To add a target namespace:
| 1. | Go to Data Set > Settings > XML Output Data. |
| 2. | Enter the desired name into the XML Target Namespace field. |
While you can use any unique string, it is recommended to enter a valid URI (Uniform Resource Identifier) to identify the data schema.
| 3. | Select Save. |
The target namespace is now added to your schema. You can remove or change it at any time.
Form Data Set Settings
The Settings tab for Form data sets provides a place for managing Form access (private or public), Form themes and XML output data settings.
Public Data Sets
By default, Data Sets you create are private and not accessible to non-authenticated users. To support your clients completing an anonymous form, you must ensure the Public Data Set setting for your data set is toggled to Yes.
Example
Shelly in Benefits Management needs to get the updated benefits selections for everyone in the company before the end of Q3. She can create a custom form with field selections and then share that form with all employees. If everyone in the company is authenticated to use Experlogix Documents, she can keep her Form Data Set private. However, if not everyone who needs to complete the form is authenticated, she'll need to make Form Data Set public to allow non-authenticated users to complete the form.
Themes
Themes for form data sets allow users to assign a specific theme to an individual form, overriding the theme defined in the Project Settings. This provides the flexibility to control the desired look and feel for each form independently.
This is especially efficient for organizations operating multiple brands or product lines. Form designers can simply select the theme that aligns with the required branding from a list of available themes, applying it quickly and consistently without restyling every form individually.
Themes management
Themes must be added to your project within the project settings before they are available in the Form Data Set settings. See Project Settings Themes Tab for detailed instructions.
Licensing
To update and manage form themes, make sure your license includes Themes and Form Themes for Advanced Forms. For more details, see Licensing.
Permissions
Both "Read project themes" and "Write data sets" permissions are required to update a form theme. To understand how permissions work across all types of items and how to manage them effectively, see Permissions and Groups.
View and Change Form themes
You can manage a form theme in the Form Data Set > Settings tab.
In this view, you will see the theme currently applied to the form. If no theme has been explicitly selected, the form automatically uses the current theme, which is inherited from the project settings.
To change a Form theme:
| 1. | Go to Form Settings. |
| 2. | Select a desired theme from the drop-down list. |
| 3. | Select Save to apply the change. |
Changing a theme creates an Update entry in the form’s history.
If the theme applied to the form is deleted, the form reverts to the project’s current theme, or to the system theme if the current theme is deleted.
Theme Inheritance and Transfer Rules
| Case | Description |
|---|---|
| Nested Form themes |
Forms inherit the parent form’s theme when added as nested forms. However, when used as standalone forms, they retain their own theme. |
| Cloning a Form | When cloning a form, the original form’s theme is retained. |
XML Output Data
When multiple Experlogix Documents data sets are associated with a template that originates from an external system (such as Smart Flows), a Target Namespace must be defined for each data set. Please, refer to XML Output Data for detailed information and setup instructions.