General Project Settings

Toolbar Options

Save
Click to save changes made on the page.
Note: If you make changes and do not click Save, you are prompted to save your changes when you navigate away from the page.
Discard
Click to discard changes made on the page.
Show Workflow
Click to open a graphical view of a workflow. When you are adding or editing a project, click this button to view the workflow assigned to the project.

Project Name Options

Project Name
Indicates the project's display name. Note that sibling projects cannot have identical names.
Name Displayed to Users Without View Privilege
Indicates the name that users who do not have view privileges see for this project. For example, an organization may be working on a company proprietary proposal, and users without view privileges should not see the actual name of the project. A different project name can be displayed to these users.
Internal Name
Indicates the unique database name automatically assigned to the project. Use this name to reference the project in scripts, Web service calls, and embedded reports based on an SBM Composer report definition that uses a primary table.
End-user Help Text
Add descriptive text that will appear to end users in Serena Work Center. For example, when users are searching for a project to submit items to, they can hover over the project name to see the information you provide here.

Use the Rich Text Editor to apply formatting to help text.

End-user help text is project specific and is not inherited by sub-projects.

Workflow and Sequencing Options

Use Parent Project's Workflow
If selected, this check box indicates that the project is using its parent project's workflow, which is specified in the Workflow Name list. The child project inherits modifications made to its parent. Clear this check box to use a different workflow for the project. In this case, the child project does not inherit any of the modifications made to its parent project.
Note: If you clear the Use Parent Project's Workflow check box for a child project, all default values that are inherited from the parent project are removed. You should review all fields in the child project to ensure that default values are set as expected.
Use Parent Project's Sequence Numbers
The numbering sequence controls the Item ID value assigned to submitted items. For example, an item that is submitted into a project might be assigned the Item ID 00001; the next item that is submitted is assigned Item ID 00002.

When the Use Parent Project's Sequence Numbers check box is selected, the sequence numbers for items in the project are assigned from a parent project. This ensures that unique IDs are assigned to all items in the parent and child projects. Clear this check box to assign a unique numbering sequence to items in the project.
Next Number
If the Use Parent Project's Sequence Numbers check box is cleared, use this option to assign the starting item number for the project. This is useful if you want different projects to have different starting numbers. For example, one project could start with 1000 and another project with 2000. You could then determine which project the item belongs to by its number.
Zero Fill to
Use this option to add the specified number of zeros to the beginning of an item number. Disable zero filling by entering a 1 in the Zero Fill to box. For best results, however, use zero filling since the item numbers are stored as strings and are sorted accordingly.

For guidance on using sequence options, refer to Frequently Asked Questions About Projects.

Item Submission Options

Allow New Items to be Submitted
If this option is selected, users can submit new items into the project.
Disallow Submission
If this option is selected, the project serves as a placeholder project and items cannot be submitted into it. You can also select this option if you want the project to be available for searching and reporting, but you do not want new items submitted into the project.
Allow Anonymous Submit
(On-premise only) - This option allows users without user accounts to submit items into the project. For details, refer to Enabling Anonymous Submits for a Project.
URL
Indicates the information that should be appended to the SBM URL for anonymous submit users. A sample final URL provided to anonymous users might be http://serverName/tmtrack/tmtrack.dll?AnonymousSubmitPage&projectid=11.

Project Form Options

Default State Form
Indicates the form that will be used for all states in the project, unless you override the form used for a specific state. Selections here override the default form specified for the workflow assigned to the project. Quick Form indicates that the built-in form will be used; other forms are custom forms created in SBM Composer.
Default Transition Form
Indicates the form that will be used for all transitions in the project, unless you override the form used for a specific transition. Selections here override the default form specified for the workflow assigned to the project. Quick Form indicates that the built-in form will be used; other forms are custom forms created in SBM Composer.

Time Capture Options

The Time Capture feature is enabled or disabled at various levels, but you can override inherited setting for all states and transitions in a project or set of projects. For details, refer to Time Capture.

Note: If Time Capture settings are explicitly set for a project rather than inherited, and you later change the settings to "inherited," time capture overrides set for states and transitions in that project are removed.

Project options are:

Time Capture
- On
  Enables the Time Capture feature.
- Off
  Disables the Time Capture feature.
- Inherited (On)/(Off)
  Inherits the Time Capture settings from the system or a parent workflow or project.
States/Transitions
- Visible
  Displays Time Capture options on forms.
- Hidden
  Hides Time Capture options on forms.
- Inherited (Visible/Hidden)
  Inherits the setting from the system or a parent workflow or project.
Entry Required
With Time Capture options set to "on" and "visible" for transitions, you can choose to require users to enter time spent on an item when they execute a transition. This requirement is ignored for automated processes, such as Web services and scripts.
- Yes
  Requires users to enter time spent on an item before they can complete a transition.
- No
  Users are not required to enter time when they execute a transition.
- Inherited (Yes/No)
  Inherits the setting from the system or a parent workflow or project.

Social View Option (Base Project Only)

You can enable or disable the Social view for all projects in your system at one time.

This setting is available only at the Base Project. To open the Base Project, select All Projects at the top of the Process Apps/Applications pane, select the Base Project, and then click Details.

To disable the Social view, clear the Use Social View check box.

To enable the Social view, select the Use Social View check box.

For details on the Social view, refer to The Social View.

HTML Support Options (Base Project Only)

The Enable HTML5 Features option enables modern HTML features, such as the Rich Text Editor, user profile card, and HTML5 form styling and layout. This option also determines which themes are available for the SBM User Workspace.

This setting impacts all projects in your system and is enabled by default. You can disable HTML5 features if you need to support legacy browsers, such as Internet Explorer 8 (IE8).

Note: For best results, users should disable Compatibility Mode in all versions of Internet Explorer when you enable HTML5 features for your system.

For details about the Rich Text Editor, refer to Rich Text Editing.

For details about HTML5 support for SBM, refer to Modern Browser Support.

Theme Settings (Base Project Only)

This option controls the theme that is used in the SBM User Workspace. The Modern Sand theme is selected by default.

This setting is available only at the Base Project. To open the Base Project, select All Projects at the top of the Process Apps/Applications pane, select the Base Project, and then click Details.

For details, refer to Configuring Theme Settings.

Security Settings (Base Project Only)

The following settings are available only at the Base Project. To open the Base Project, select All Projects at the top of the Process Apps/Applications pane, select the Base Project, and then click Details.

Allow login page to be embedded in another Web site
This option enables you to embed the SBM login page in another Web site's frame and it allows the login page to appear in the SharePoint Web Parts if you are using SBM Connect for SharePoint^®. Select this option if you are using SBM Connect for SharePoint^® or if you want to add the SBM login page to a Web portal.

CAUTION:
This option is selected by default; however, you can clear the check box for tighter security. Doing so prevents attacks that can potentially intercept clicks and send data to the enclosing Web site.
Sanitize HTML Values in Memo Fields, Journal Fields, and Notes
This option "sanitizes" HTML that is stored in the database for Memo fields, Journal fields, and notes that are configured to render HTML tags, which prevents cross-site scripting (XSS) attacks, JavaScript injections, and rendering of poorly-formatted or malicious HTML behavior from occurring. When this setting is enabled, SBM automatically compares the raw HTML in the database to the list of approved tags, attributes, and restricted styles that you configure to ensure the HTML is considered "safe" before it is rendered on the form. Any user-defined HTML formatting is also sanitized, which ensures that the HTML is formatted and displayed in a uniform, consistent manner.

Note: This option does not change any values that are already stored in the database; instead, HTML values in the database are sanitized at runtime before they are rendered on the form. When a user transitions an item with newly-sanitized HTML, the sanitized value is saved in the database when the transition is completed.

A default configuration of approved HTML tags and attributes is provided in case-insensitive JSON format. You can add or remove entries under each JSON field as necessary; however, the following JSON fields are required and cannot be removed:
- allowedTags – List of tags that are allowed
- allowedAttributesGlobal – Attributes that are allowed in all tags
- allowedAttributesByTag – Attributes that are allowed for certain tags
- restrictedStyles – List of styles that are not allowed
- needToValidateStyles – Flag to restrict styles or not
Note that the default configuration excludes the following obviously suspicious HTML tags, which means SBM does not render these tags by default:
```
<applet, </applet 
<embed, </embed 
<form, </form 
<frame, </frame 
<iframe, </iframe 
<input, </input 
<script, </script 
<textarea, </textarea
```
If you disable the Sanitize HTML Values option, only the suspicious tags listed above are not rendered. This includes the <a, </a and <img, </img tags unless they are added using the Rich Text Editor. However, these tags will not be rendered if they contain suspicious attributes, such as onload or onclick.

If you have made changes to the configuration and you want to compare them to the default configuration that is provided with SBM, click Reset Configuration, note the changes, and then click Discard.

To view a well-formatted version of the default settings and some configuration examples, refer to solution S141316.