Form Editor: Settings Tab

Overview

The Settings tab controls the form’s identity, record behavior, record ID format, uniqueness rules, layout, and the roles that can create records. The settings apply to the current form, not to every form in the application.

Use this tab when you need to change the form name or description, control translations and record copying, hide the displayed record status, prevent new comments from being added through Record History, include the creation date in generated Record IDs, define unique-field combinations, adjust the form layout, or change record-creation access.

Open the Settings Tab

  1. Open the application in the Application Designer.
  2. Select Forms, then open the form you want to configure.
  3. Select Settings in the Form Editor.
  4. Review the current values before making changes, especially the Record ID settings and role access.
  5. Save the form after completing the required updates.

General Settings

Field or optionDescription
Form NameThe name displayed for this form. Use a descriptive name that is easy to recognize in the application.
Form DescriptionA short explanation of the form’s purpose.
Disable TranslationsTemporarily prevents field-language settings from being used. This can be useful while translations are still being prepared.
Use a Field to choose the LanguageOverrides the user’s browser-language choice and uses a field on the form to determine the displayed language.
Disable Record CopyRemoves the Copy Record option while users view or edit records in this form. View-level record-copy behavior can also be controlled from the applicable View settings.
Hide Record StatusHides the record status from the record action navigation for records in this form.
Disable Add Comments in Record HistoryPrevents users from adding new comments from the Record History/record audit sidebar for records in this form.
Figure 1. General Settings includes the Hide Record Status and Disable Add Comments in Record History controls.

Hide Record Status

Hide Record Status is a form-level display control. It changes whether the record’s current status is shown in the record action navigation; it does not change the record’s underlying workflow stage or workflow configuration.

Field or optionDescription
Before — setting offThe record status is displayed in the record action navigation, subject to the user’s normal access.
After — setting onThe record status is hidden from the record action navigation for records in this form.
What remains unchangedWorkflow stages, routing, action buttons, security rules, triggers, and recorded history continue to use the record’s actual workflow state.
ScopeCurrent form only. Configure other forms separately.

Use carefully: Hiding the displayed status can simplify the record interface, but users may lose helpful context. Confirm that the workflow buttons and page content still make the record’s next step clear.

Disable Add Comments in Record History

Enable this control when users should be able to review record activity but should not be able to add new comments from the Record History sidebar.

Field or optionDescription
Before — setting offThe add-comment control is available to users who can open Record History and are otherwise allowed to add a comment.
After — setting onThe form prevents users from adding new comments from the Record History/record audit sidebar.
Existing historyExisting comments and other recorded events remain part of Record History. The setting controls new comment entry; it is not a history-deletion control.
Other history functionsUsers can continue to review the record activity available to them. Filtering and export behavior remain governed by Record History and user access.
ScopeCurrent form only. It does not disable comments for records created with other forms.

For the comment composer, history filters, and history export behavior, see Record-Level Comments.

For broader audit material published on the support site, open the Audit & Compliance category. Link the dedicated Application Record Audit and Application History articles here after those pages are published.

For organization-level administrative events, see Platform: Audit. Platform Audit is separate from the history of one record and from application-design history.

Record ID

A Record ID is the unique identifier generated for each record created with the form. It can be a simple incrementing number or a formatted value made from a prefix, a padded increment, an optional suffix, and—when enabled—the record creation date.

Field or optionDescription
Reset IncrementResets the numeric sequence so the next generated number starts again from 1. Use this only after confirming that duplicate IDs cannot be created.
PrefixOptional text placed before the numeric portion. The current interface notes that the prefix cannot end with a number.
Min LengthThe minimum number of digits in the numeric increment. GW Apps pads the increment with leading zeros.
SuffixOptional text placed after the numeric portion. The current interface notes that the suffix cannot start with a number.
Include record creation date in IDAdds the record’s creation date to the generated Record ID. Use the live Example shown in the editor to verify the exact date representation and order before saving.
ExampleA live preview of the Record ID pattern produced by the current settings.
Figure 2. Record ID settings include Prefix, Min Length, Suffix, Reset Increment, the creation-date option, and a live Example.

What Fields Are Unique

Use What fields are unique to select one or more fields whose combined values must be unique. A single selected field must be unique by itself. When several fields are selected, GW Apps evaluates the combination.

Example: If First Name is the only unique field, two records cannot both contain John. If First Name and Last Name are selected together, John Smith and John Jones are allowed, but a second John Smith is not.

  • Select the field selector and choose a field to include in the unique combination.
  • Add other fields when uniqueness depends on more than one value.
  • Remove a selected field when it should no longer participate in duplicate prevention.
  • Test both a valid combination and a duplicate combination before publishing the form.
Figure 3. What fields are unique can contain one field or a combination of fields that must produce a unique value.

Form Layout

Field or optionDescription
Form WidthSets the maximum display width. Choose Medium, Wide, or Full according to the form’s layout and the amount of information displayed.
Form OutlineDisplays a right-side outline for quick navigation between sections in a longer form.
Figure 4. Form Layout provides Medium, Wide, and Full width options and the Form Outline control.

Who Can Create New Records

Use Role Access to select the application roles that can create records with this form. This setting controls record creation; it does not replace workflow-stage or field-level permissions.

Figure 5. Role Access identifies the roles allowed to create new records with the form.

Troubleshooting

Field or optionDescription
Record status is still visibleConfirm that Hide Record Status is enabled on the correct form, save the form, then reopen the record.
Users can still add commentsConfirm that Disable Add Comments in Record History is enabled on the form that created the record and that the latest settings were saved.
Users cannot find Add CommentCheck whether the form-level disable control is enabled and confirm the user’s access to Record History.
Record ID does not contain the dateConfirm that Include record creation date in ID is selected, verify the Example preview, save, and test with a newly created record.
Record IDs could duplicate after resetStop creating records, review existing IDs, restore a safe sequence or pattern, and validate uniqueness before resuming use.
A user cannot create recordsConfirm the user’s role is included under Role Access and review the form’s security configuration.

Continue with Design – Form Editor Overview, Workflow, or Security when those settings are part of the task.

Updated on August 26, 2026
Was this article helpful?

Related Articles