Skip to content
AgentZforiMIS®

Forms and applications recipes

Prompts for form audits, contact updates, applications, approval forms, placement, testing, response reporting, and launch checks. The recipes make writeback and routing visible before launch.

Copy a request into your AI app and replace the words in square brackets with your own. See Using a recipe.

Audit existing forms and where they appear

Section titled “Audit existing forms and where they appear”

Recipe R-09-01 · Kind of request: Look up · For: Forms owner, Digital team

When to use it: Use this when staff inherit forms, prepare a launch, or suspect old forms are still live. It gives the team a map before they edit or replace anything.

What AgentZ does: AgentZ reads forms, page placement, and related configuration evidence, then organises it into a practical inventory. It should flag forms that need owner review, testing, or retirement.

Before you begin: Have the site, process, or form name scope ready.

Keep in mind: A form existing in iMIS does not mean it is live on a page. Check placement and route behaviour too.

Recipe R-09-02 · Kind of request: Multi-step plan · For: Membership team, Digital team

When to use it: Use this when members should maintain their own contact details. The team wants fewer manual updates while protecting core data quality.

What AgentZ does: AgentZ reviews the member-data fields, designs and creates the native form through the governed Form Builder writer, prepares placement, and verifies the intended audience and writeback with a controlled test. It returns an explicit alternative only when a requested business outcome belongs to commerce, Process Automation, PanelEditor, cloud post-processing, or a custom iPart.

Before you begin: Have the fields, audience, approval requirement, confirmation text, and page location ready.

Keep in mind: Contact forms can overwrite important data. Test with a controlled member record before launch.

Recipe R-09-03 · Kind of request: Multi-step plan · For: Membership team, Digital team

When to use it: Use this when creating or improving a join form. Membership teams need the form to collect enough information for onboarding without creating duplicate or incomplete records.

What AgentZ does: AgentZ maps the application journey, builds the supported native form after presenting the governed write plan, and connects it to member setup, approval, placement, and verification. Standard iMIS commerce owns payment; AgentZ must not imitate checkout inside a post-processing script.

Before you begin: Have member type, eligibility rules, required fields, payment policy, approval path, and launch page ready.

Keep in mind: Application forms affect data quality and member experience. Test duplicate handling and staff notifications before launch.

Design a nomination, survey, or approval form

Section titled “Design a nomination, survey, or approval form”

Recipe R-09-04 · Kind of request: Multi-step plan · For: Governance team, Membership team, Digital team

When to use it: Use this for awards, committee nominations, surveys, bursaries, or applications where submissions need review. Staff need the form and the back-office process designed together.

What AgentZ does: AgentZ turns the process into native fields, rules, approval configuration, notifications, and reporting needs, builds the supported Form Builder configuration, and verifies each configured outcome. Delivery and task execution remain owned by Communications and Process Automation even when Forms supplies the trigger.

Before you begin: Have the purpose, audience, questions, reviewers, deadlines, and outcome process ready.

Keep in mind: Approval forms fail when routing is unclear. Name the owner and test the full path before launch.

Place a form on a portal page and verify it is connected

Section titled “Place a form on a portal page and verify it is connected”

Recipe R-09-05 · Kind of request: Multi-step plan · For: Digital team, Forms owner

When to use it: Use this when a completed form needs to appear on the public site or member portal. Placement is where many launch issues happen: wrong page, wrong audience, or wrong confirmation.

What AgentZ does: AgentZ checks form and page evidence, uses the canonical Forms iPart serializer and RiSE owner to place/publish after the exact governed confirmation, then verifies the saved binding and rendered route as the intended audience.

Before you begin: Have the form name, page URL, audience, confirmation message, and launch date ready.

Keep in mind: A form can be correctly built but incorrectly placed. Verify the actual page as the intended audience.

Run a controlled form test and verify writeback

Section titled “Run a controlled form test and verify writeback”

Recipe R-09-06 · Kind of request: Multi-step plan · For: Forms owner, Membership team

When to use it: Use this before launching a form or after fixing one. Staff need evidence that submission, notification, and data writeback work together.

What AgentZ does: AgentZ prepares the test case, guides or performs supported submission steps, and checks response/writeback evidence. It should produce a pass/fail checklist with screenshots or route notes where useful.

Before you begin: Have the form, test record, expected values, and allowed test scope ready.

Keep in mind: Never test risky writeback on a real member without explicit approval and a rollback plan.

Recipe R-09-07 · Kind of request: Multi-step plan · For: Forms owner, Reporting team

When to use it: Use this after applications, surveys, nominations, or contact-update forms start collecting responses. Staff need usable insight and follow-up lists, not just raw submissions.

What AgentZ does: AgentZ reads form-response evidence, profiles answer patterns and exceptions, and designs a reporting view if needed. It should ask before creating saved queries or dashboards.

Before you begin: Have the form name, date range, questions of interest, and reporting audience ready.

Keep in mind: Survey or application data may be sensitive. Limit exports and report columns to what staff need.

Gate a form for launch with a readiness checklist

Section titled “Gate a form for launch with a readiness checklist”

Recipe R-09-08 · Kind of request: Look up · For: Forms owner, Digital team, Process owner

When to use it: Use this immediately before launch or after major form edits, especially for applications, contact updates, surveys, or approval forms that affect member data. It gives staff a shared go/no-go view before members or applicants rely on the form.

What AgentZ does: AgentZ checks the form, page, and related setup evidence it can reach and turns it into a readiness matrix. It should clearly state what has been verified and what still needs manual testing.

Before you begin: Have the form, page, audience, and launch date ready.

Keep in mind: Readiness is not the same as live. Complete the test submission and owner sign-off before announcing the form.

Recipe R-09-09 · Kind of request: Multi-step plan · For: Forms owner, Integration team

When to use it: Use this when the native form must invoke a supported iMIS REST/domain operation after submission. It is not a route for arbitrary JavaScript, SQL, payment, subscription, or security mutations.

What AgentZ does: AgentZ compiles the bounded formswebhook(ID, Ordinal, FormName) process page, normalizes an omitted/blank optional Ordinal, deploys and verifies the script fingerprint and submit-action binding, uses a separate staff context route when selecting an on-behalf Party, submits the intended public/shared or member form route, and verifies native process-resource observation, counter movement, clean-before/matched-after target state, context restoration, rollback, and cleanup. When processTable names a reusable Multi Layout source, AgentZ proves the process at that exact row Save, matches the observed Ordinal to the saved native row key, keeps the later main-form Submit separate, and returns an attested post-processing evidence packet that carries directly into launch readiness. For approval forms, the same approval owner waits through the native observation window and proves the completed decision. If iMIS persists no process identity and emits no call/resource/receipt, AgentZ may invoke that exact Published canonical process once as explicitly labelled recovery; a multi-row Ordinal must be supplied from correlated evidence or uniquely derived from a complete pre/post row diff.

Before you begin: Have the form, intended audience, supported target entity/operation, a disposable test record, expected after state, and rollback policy ready.

Keep in mind: A saved script page or process binding alone is not success. The controlled rendered submission or completed approval plus canonical receipt and target readback prove causality. AgentZ recovery after a proven native omission must never be reported as a native iMIS invocation. Use native commerce, Process Automation, or a custom iPart when the requested outcome lies outside the governed REST contract.