Plan Details Form Configuration in OnePlan - Guided Workflow

Direct Answer: How Plan Details Form Configuration Works in OnePlan

Plan Details form configuration in OnePlan follows a recommended sequence: build the form’s Sections, Fields, and Elements first, split the form into multiple Pages if a single layout isn’t enough, configure the Process Flow Steps that mirror your lifecycle, add Stage Gates where approvals or validation are required, and finally layer in Business Rules for conditional field behavior and custom JavaScript if needed. Each stage builds on the one before it — for example, Business Rules typically reference fields that already exist on the form, and Stage Gates are attached to Process Flow Steps that must already be defined.

What This Article Covers: Plan Details Form Configuration

This article walks through the recommended order for configuring a new Plan Type’s Plan Details form end to end, linking to the How-To article for each stage. For conceptual background on the five components of a Plan Details form, see Plan Details Forms in OnePlan - Admin Overview.

What you will accomplish By the end of this article, you will know the recommended sequence for building a new Plan Details form from scratch, and where to go for step-by-step instructions on each stage.

Who This Article Is For: Plan Details Form Configuration

Administrators setting up the Details experience for a new Plan Type
Portfolio Admins planning a significant restructure of an existing Plan Details form
Anyone who has read Plan Details Forms in OnePlan - Admin Overview and is ready to start configuring

Plan Details Form Configuration at a Glance

Build the Form Structure — Add sections, fields, and elements to the base form.
Split Into Pages (Optional) — Organize content across multiple tabs if the form is large.
Configure Process Flow Steps — Define the lifecycle stages the plan moves through.
Add Stage Gates — Attach approvals or validation to specific process flow steps.
Add Business Rules — Layer in conditional field and section behavior.
Extend as Needed — Add JavaScript customization for advanced scenarios.

Step 1: Build the Form Structure

Every Plan Details form starts with its base structure: Sections that organize the layout, Fields that pull in plan or summary data, and Elements like tables, child plan tables, images, or text. Open the Form Editor for the Plan Type and build out this structure on the default Overview page before deciding whether the form needs to be split further.

Related task: - How to Configure Plan Detail Forms in OnePlan

Step 2: Split Into Pages (Optional)

If a single layout starts to feel crowded, split the form into multiple Pages — displayed as tabs at the top of the Details module — so related information is grouped together (for example, an Overview page and a separate Financials page). This step is optional: skip it for simpler forms that fit comfortably on one page. A form can have up to 8 pages, and existing content always starts on the default Overview page.

Related task: - How to Configure Plan Detail Forms in OnePlan

Step 3: Configure Process Flow Steps

Once the form’s content is in place, define the Process Flow Steps that mirror your organization’s plan lifecycle (for example, Initiation, Planning, Execution, Monitoring, Closure). Each step controls which Available Tabs — top-level modules like Financials or Work Plan — are visible while a plan is in that stage. This is a separate concept from Pages: Process Flow Steps and their Available Tabs operate at the top level of the plan, while Pages organize content inside the Details module itself.

Related task: - How to Configure Process Flow Steps in OnePlan

Step 4: Add Stage Gates

For any transition between process flow steps that needs governance, attach a Stage Gate. A Standard Stage Gate can require approvals, evaluate rules such as budget thresholds, and validate that required data is present before letting a plan advance. Auto-approval can be used for predictable transitions that don’t need manual review.

Step 5: Add Business Rules

With the form’s fields, pages, and process flow in place, add Business Rules to control conditional behavior — showing, hiding, requiring, or locking fields and sections based on plan data or the logged-in user’s security groups or teams. Because Business Rules apply to the whole form regardless of page, configure them after your pages and fields are finalized to avoid rework.

Step 6: Extend as Needed

For most forms, the previous steps are sufficient. For advanced scenarios, add JavaScript customization for validation logic or computed values that Business Rules can’t express.

Frequently Asked Questions: Plan Details Form Configuration

Q: What order should I configure a new Plan Details form in OnePlan? A: In OnePlan, build the form’s sections, fields, and elements first, split it into pages if needed, configure process flow steps, add stage gates, then layer in business rules. Add JavaScript customization last, only if needed.

Q: Do I need to configure Pages before Process Flow Steps in OnePlan? A: No. In OnePlan, Pages and Process Flow Steps are independent — Pages organize content inside the Details module, while Process Flow Steps control which top-level modules are available at each lifecycle stage. You can configure them in either order, but building the form’s base content first makes both easier to plan.

Q: Why configure Business Rules last in OnePlan? A: In OnePlan, Business Rules typically reference fields, sections, and pages that already exist on the form. Configuring them after the form’s structure and process flow are finalized reduces the chance you’ll need to rebuild a rule after a field or section changes.

What to Do Next: Plan Details Form Configuration

Learn the concepts first: - Plan Details Forms in OnePlan - Admin Overview

Start configuring: - How to Configure Plan Detail Forms in OnePlan - How to Configure Process Flow Steps in OnePlan