Describe the form you want — and let AI build it.

The AI Assistant builds and edits form configurations from plain-language prompts, and can review an existing form for issues. Tell it what you need — “add a 3-step approval wizard with a manager sign-off” — and it returns a ready-to-apply configuration, or a plain-text report if you’d rather it just advise.

You bring the AI. Modern DFFS does not include it. There is no AI model, subscription, or bundle of tokens inside the product, and the license price does not cover any AI usage. Whichever route you use, the model access is yours and is billed by whoever provides it: send inline with your own provider API key (Claude, OpenAI, Gemini, Mistral, Grok, Groq), or copy the prompt into an AI tool you already subscribe to. On Enterprise, your own relay runs on your organization’s provider account. Either way you need AI access of your own — SPJSWorks never meters, resells, or subsidises it.

From prompt to working form

A real request on a real form: a purchase-request form has an Approval tab, but no approver field and no notification. Here is the whole round trip.

1. Describe the change in plain language

   Scope the request to only the parts it touches — here Form and Rules — choose whether the AI should apply the changes or just review and report, then write the prompt the way you’d say it to a colleague.

   Provider configuration sits at the top, and the panel says it plainly: optional — required only to use Send to AI. That’s where the two routes diverge at step 3 — send inline with your own key, or Copy / Download the assembled prompt to run in whatever AI tool you already use, then bring the answer back at step 4.

   

2. It asks before it invents anything

   The response streams back — expand it any time to watch what’s being generated. This request needs an Approver column that doesn’t exist on the list yet, so rather than guessing or silently failing, the assistant lists exactly what it wants to create and waits for you: create the fields, or skip and wire them up yourself.

   

3. Apply it, or take the JSON

   Import the configuration straight into the form, or download it as JSON to review, diff, or move to another environment first. Nothing is written until you choose.

   

4. The field lands where you asked

   Back in the form builder, the Approval tab of the existing tab set now holds the Approver field — inside a proper row and column, matching the structure the rest of the form already uses.

   

5. …and so does the logic behind it

   It didn’t stop at the field. The assistant also wrote the rule that was asked for: when Approver: Email is not empty, on change → send email — with the recipient, subject and body built from field tokens like [[fieldValue:Approver.email]]. Editable like any hand-built rule.

   

6. Nothing the AI does is one-way

   A restore point is written automatically before the configuration is applied. Roll the form back in one click, or Compare the two versions to see exactly what changed.

   

Full AI Assistant documentation →  ·  Example prompts →