BiznextApp SharePoint Forms — User & administrator manual

This guide covers installing the solution, provisioning site artefacts, and day-to-day use of the BiznextApp SharePoint Forms web part (SPFx). For product marketing and tutorials, see BiznextApp Forms for SharePoint.

1. What this web part does

  • Design forms in the browser (drag-and-drop builder, optional AI assistance where configured).
  • Connect each form to a SharePoint list or document library.
  • Submit and edit items through a modern form UI (including libraries that use documents).
  • Runs in SharePoint pages, full-page apps, and Microsoft Teams (tab / personal app), subject to your tenant setup.

2. Deployment overview (tenant / farm administrators)

  • Build or obtain the SharePoint solution package (.sppkg) for BiznextApp Forms.
  • Upload it to your organization’s App Catalog and deploy as usual for SPFx solutions.
  • Site owners add the app to each site collection that should use the web part.

3. First use on a site (provisioning artefacts)

Before forms can be stored and listed, the web part creates hidden SharePoint lists on the site (if they do not already exist):

List Purpose (summary)
BiznextAppFormSettings App/settings storage
BiznextAppForms One item per form definition (configuration)
BiznextAppFormData Form submission data references

Who can provision

Users with Manage Web permission on the site (typically site owners) see Install necessary form artefacts on first run. Select it once to create or verify these lists.

After installation

  • A success or informational message may appear.
  • Available Forms appears once provisioning has completed and the app has confirmed the lists exist.

Help on the setup screen

4. Roles inside the web part

The web part distinguishes capabilities using SharePoint permissions:

Role How it is determined Typical capabilities
Admin User has Manage Web on the site Install artefacts, Design New Form, open Permissions, use Settings (links to underlying lists)
Contributor User has contribute-level access to the BiznextAppForms list Same action bar as admin except strict admin-only actions depend on Manage Web where the UI checks isAdmin

Users without these permissions can still open forms they are allowed to use if you share the right links or pages; they may not see the full toolbar.

5. Web part properties (edit page → web part)

  • Description — Appears as the web part’s description; you can use it for page authoring notes.
  • Advanced connection settings (for example AI API or license server URL) may be hidden in your build. When shown, they are optional and intended for administrators; empty values use product defaults where applicable.

6. License notice

If your organization uses the license service, an unlicensed or invalid site may show a License banner with a short explanation and a link to purchase or resolve licensing. Until the license is valid, the main experience may be blocked or dimmed according to your deployment.

7. Working with forms

7.1 Available Forms

After artefacts are installed, the Available Forms grid lists form definitions from BiznextAppForms. From each row you can typically:

  • Open the form builder to edit design.
  • Create a new item or open list/document views depending on configuration.
  • Use the row context menu for actions such as copying links (for example a link to the items view for that form).

7.2 Designing a form (admins)

  • Choose Design New Form (when you have rights and artefacts are installed).
  • Pick or create the target SharePoint list or library.
  • Add controls from the toolbox, map fields to columns, and save.

Forms can target both generic lists and document libraries; libraries may use document-specific behavior in the viewer.

7.3 Filling out a form (end users)

  • Open a form from Available Forms or a shared link (see below).
  • Complete required fields and submit; edits follow your list’s permissions and the form configuration.

The web part can read query parameters on the page:

Parameter Meaning
formId ID of the form item in BiznextAppForms
itemId Optional. When set, opens that list item in the form viewer

Example pattern:

https://your-site/pages/your-page.aspx?formId=12&itemId=45

Use these links in emails or navigation to deep-link open item or open form’s list view depending on which parameters you include.

8. Toolbar reference (when visible)

Control Purpose
Install necessary form artefacts One-time (or repair) provisioning of hidden lists
Design New Form Create a new form definition
Permissions Manage permissions for the solution’s lists (admin)
Settings Quick links to open BiznextAppForms, BiznextAppFormData, and BiznextAppFormSettings in SharePoint
Collapse / expand Toggles the action strip for a cleaner page

The toolbar can hide when the page URL contains a formId query (focused “form-only” view).

9. Items and documents views

For each form you may open:

  • A list items view for regular lists, or
  • A documents view for document libraries (folders, files).

Context menus may include copy link actions for sharing the current view or item. Exact labels depend on your version.

10. If something goes wrong

If the UI crashes inside the web part, you may see Something went wrong with a short explanation and:

Note anything you were doing and whether the problem happens on one browser or for one user only; your administrator may need to check list permissions, app deployment, or network policies (for example CORS for custom API endpoints).

11. Support contacts

Topic Contact / link
Product help https://biznextapp.com/forms-for-sharepoint.html
Email apps@devwals.com
Developer / publisher BiznextApp (devwals.com) — see App Catalog and package metadata for privacy and terms

12. Glossary

Term Meaning
Artefacts The hidden lists and fields the app needs on the site
BiznextAppForms Catalog of form definitions (titles, list wiring, JSON config)
Form viewer Read/write UI for filling or editing an item through the configured form
SPFx SharePoint Framework — how this web part is packaged and hosted

This manual describes behavior intended by the product. Minor differences can occur by version or tenant policy; refer to release notes and your internal IT team for organization-specific rules.

Questions about this manual?

Reach out for product support or licensing.

Email apps@devwals.com
Business Process Apps   

Technology Solutions

We are just a few developers building apps to simplify business processes.

Contact Us

To get support on some of our products, please reach out to us.