Smarter, self-serve control of Opportunity fields and forms
We’re giving admins full front-end control of Opportunity fields and the Opportunity form, so firms can align Nexl Opportunities with their own processes without waiting on backend changes.
1. Front-end admin for Opportunity fields & form configuration
Admins can now manage core aspects of the Opportunity schema directly in the web app.
What you can do
Create, edit, and delete custom fields
Add new Opportunity fields (e.g. Court, Judge, Matter Type, Cross-Border flag)
Update labels and options as your process evolves
Manage Opportunity custom statuses
Add, rename, and remove custom statuses
Align Nexl pipeline stages with your internal BD / matter lifecycle
Control field ordering on the Opportunity form
Drag-and-drop to reorder fields on the create/update Opportunity form
Group the most important inputs at the top (e.g. Client, Matter Type, Value)
Mark fields as mandatory on the form
Toggle Required on form to make specific fields mandatory
Applies across all statuses (firm-wide definition of “must-have” data)
What this means in practice
No more support tickets for:
“Please add this new Opportunity field…”
“Can you make this field required?”
“We need to reorder these fields on the form…”
Firms can iterate quickly on their Opportunity configuration as strategy and reporting needs change.
2. How mandatory fields work (“Required on form”)
We’ve kept the mandatory-field model simple and future-proof, especially with AI-based creation in mind.
On the Opportunity form (web & Outlook)
Fields marked Required on form:
Must be filled to submit the create/update form
Are enforced consistently on both:
Web app Opportunity create/edit
Outlook add-in Opportunity create/edit
Existing Opportunities:
When you edit, the form will ask you to fill any required fields that are currently empty
This ensures data quality improves over time without blocking background processes
3. Outlook add-in: aligned Opportunity experience
The Opportunity enhancements are also available in the Outlook add-in.
What changes in Outlook
The Opportunity create/edit panel in Outlook:
Reflects your custom fields and custom statuses
Respects field ordering defined in the web admin
Enforces Required on form rules in the same way as the web form
Result
Lawyers and BD users creating Opportunities straight from Outlook see the same structure and required fields as in Nexl web
Admins only configure once in the web app; Outlook picks it up automatically.
4. Edge cases & behaviour to be aware of (client-friendly view)
A few nuances that admins and power users should understand:
Required fields are enforced only on forms
Web and Outlook forms: enforced
AI/API creation: not enforced; required flags are treated as guidance
Hide-from-form vs. Required
Existing “hide from form” settings for custom fields still apply
A field cannot be both hidden and required on the same form configuration
If a field is set to Required, it will be visible on the form
5. Who benefits
BD Managers and Partners
Can shape Opportunity fields and statuses to match firm strategy, without technical help
Ensure the right information is always captured at the point of entry
Firm/System Admins
Gain no-code control over Opportunity configuration
Reduce reliance on support for routine schema changes
Any Nexl user logging Opportunities
Gets a clearer, better-structured form focused on the information that truly matters