About the Completion of Automated Upgrade form

When upgrading Mongoose, the Form Sync process identifies the form and global objects that require manual decisions before the upgrade is finalized. Previously, all prompts were resolved in a single session by a single user, making large upgrades time-consuming and difficult to coordinate. The Completion of Automated Upgrade form decouples prompt processing from the synchronization session. Prompts are now presented in a persistent, hierarchical view that multiple users can work through incrementally. You can resolve some prompts now, return the next day to finish the rest, and distribute the work across team members without losing progress.

The Completion of Automated Upgrade form displays all prompts produced during the most recent Form Sync synchronization. Prompts are organized in a tree structure grouped by category such as Forms, Global Objects, Messages, with each top-level node showing the total prompt count. You expand a node to see individual prompts, select your action for each one (Keep, Remove, or Edit), and submit your selections for processing.

The form applies to the currently logged-in configuration and displays the date and time of the last synchronization from the most recent maintenance window.
Note: Changes submitted through the Completion of Automated Upgrade form cannot be undone. For information about when backups are performed in the cloud, refer to the SaaS Delivery Guide. If you are running an on-premises environment, consider taking a backup before running the Completion of Automated Upgrade form.

You can open the Completion of Automated Upgrade form from the Mongoose menu after the Form Sync synchronization has been performed. The form loads the active upgrade session for your current configuration automatically.

Key benefits

  • Incremental completion — Resolve prompts at your own pace over multiple sessions. There is no longer a requirement to address every prompt in one sitting. Progress is saved each time you submit a batch.
  • Multi-user collaboration — Different team members can work on different prompts concurrently. A developer can handle script-related prompts while a functional consultant addresses event handler decisions, with built-in conflict detection ensuring no work is lost.
  • Persistent documentation — The prompt list and its details remain visible until fully resolved, giving you a clear understanding of what the upgrade requires and what remains outstanding at any point.
  • Reduced upgrade risk — By allowing partial commits, the risk of accidentally losing a long session of work due to a time-out or connectivity issue is eliminated. Only the prompts you explicitly submit are processed.
  • Faster time to production — Teams can begin resolving known prompts immediately after synchronization completes, instead of scheduling a single extended maintenance window for one person to work through everything sequentially.

Form layout

The Completion of Automated Upgrade form is divided into these areas:
  • Session information - Displays the date and time of the last synchronization.
  • Submit Changes button - After selecting prompts under Forms or Global Objects, making decisions, and you have come to a stopping or completion point, this button is used to submit changes. If all the changes under a given node are satisfied by making decisions, and the Submit Changes button is selected, the node appears green.
  • Prompt Key - The colors represent the current state of the prompt. The colors is shown on the Prompt nodes under Forms and Global Objects.
    • Red for Unresolved
    • Blue for Resolution Pending
    • Green for Resolved
  • Prompt tree - A hierarchical view of all prompts, grouped by category:
    • Forms - Includes form-level prompts, components, event handlers, filters, and form variables.
    • Global Objects - Includes global scripts and other non-form objects.
    • Messages - Displays errors and warnings. such as read-only and not actionable. This is hidden by default.
  • Prompt detail panel - After selecting a prompt under Forms or Global Objects the prompt detail appears on the right side, along with its available actions.

Working with prompts

Understanding prompt actions

Each actionable prompt offers up to three responses:

Action Description
Keep Retain the customized version of the object. The vendor’s changes are not applied.
Remove Discard the customization and accept the vendor’s version.
Edit Open an editor to merge customized and vendor content manually. This is available only for scripts and event handlers.

Selecting and submitting prompts

  1. You must expand a category node in the tree to show individual prompts.
  2. Select the action for one or more prompts. You can select between Keep, Remove, or Edit.
  3. Click Submit to process your selections.

You are not required to resolve all prompts at once. You can submit as many or as few as you choose. Unresolved prompts remain available for your next session.

Caution: Submitted changes cannot be undone through this form. Review your selections carefully before submitting.

Editing scripts and event handlers

The Edit action is available only for:
  • Form Event handlers - EVENT_HANDLER prompts with field ID EVENT_HANDLERS.
  • Form scripts - FORM prompts with field ID SCRIPT.
  • Global scripts - SCRIPT prompts.
When you select Edit:
  1. A child form opens showing the vendor version and your customized version side by side.
  2. Make your edits in the customization panel.
  3. Click OK to accept your edits or Cancel to return without the changes.
    Note: If you cancel the edit, only that prompt reverts to an unresolved state. Any other actions you have queued for other prompts are preserved.

Multi-user workflow

Multiple users can work on the same upgrade session simultaneously:
  • Each user sees the full list of prompts and their current resolution status.
  • Users can resolve different prompts concurrently without interfering with each other.
  • After one user makes a prompt decision, if another user logs in and tries to make changes, the node appears as Resolved and is read-only.
  • If two users attempt to resolve the same prompt, the first submission succeeds and the second receives a concurrency conflict notification. The second user must refresh the form and verify the resolution.

The system acquires locks in a consistent order to prevent deadlocks, regardless of the order in which users select prompts.

Understanding results

After submitting, each prompt row displays a result in the error and warning area:

Result Meaning Action Required
Success The prompt was resolved and committed. None
ConcurrencyC onflict: Already resolved by another user Another user resolved this prompt before your submission was processed. Refresh the form. The prompt is already complete.
ConcurrencyC onflict: Prompt is not part of the active upgrade session The prompt belongs to an older session that has been superseded. Refresh the form. A new synchronization may have occurred.
Error A validation or processing error occurred. Review the error message, correct the issue, and retry.

After viewing results, the form refreshes automatically to reflect the current state of all prompts.

Session states

The form handles these session states:

State Display
No configuration connection Neutral message indicating the configuration is unavailable.
No active upgrade session Informational message indicating no synchronization prompts are pending.
All prompts resolved Completion message indicating the upgrade session is fully resolved.

Completion detection

  • See the Prompt Key in the Form Layout section above if there any questions about the state of a node in the Prompt Tree.
  • The form displays a completion indicator.
  • Server-side cleanup runs automatically, temporary state and backup data are removed.
  • The session marker is retained for audit purposes.

Clear the forms cache after completion. Form – Definition – Unload All Global Forms Objects.

Relationship to the original Form Sync form

The Completion of Automated Upgrade form replaces the prompt-resolution portion of the legacy Form Sync workflow. The underlying prompt generation and synchronization process remain unchanged:

  • Form Sync still runs as before, generating prompts during synchronization.
  • The synchronization log is still cleared on each new synchronization invocation.
  • Existing edit sub-forms for event handlers and scripts are reused without modification.
  • The original completion route remains available for backward compatibility.