DynamicForm Start free trial

Knowledge base

Answers about DynamicForm

118 short, direct answers for IT teams and IT services companies evaluating DynamicForm, grouped by topic. Each answer has its own link.

Getting started

What is DynamicForm?

DynamicForm by AG Studio Ventures builds business applications from configuration for web and Android. Describe your business or upload documents. AI Core proposes a versioned Business Blueprint, and your team approves everything before the application is built.

Who is DynamicForm for?

DynamicForm is for organisations that need business applications, their in-house IT teams, and IT services companies building applications for clients. Business users describe what they need, and the delivery team reviews, configures and manages the application.

Who builds the application?

Business analysts with some IT knowledge, in-house IT teams or IT services companies can build applications with DynamicForm. They describe the business or upload documents, answer focused questions, and review and approve the Business Blueprint before AI Core builds the application. Business analysts can then hand over to the core IT team for complex third-party integrations and technical setup.

We are an IT services company. Can we use DynamicForm for our clients?

Yes. Each client runs as its own company on one platform, with its own users, applications, data, web address and branded Android app. At onboarding, each data layer can be logically separate in a shared store or physically separate in its own store.

How fast can we go live?

About 30 days for a complex, multi-stage system such as loan origination. A one- or two-step process, such as a request and its approval, can go live in hours. After go-live, changes take days or less, because nothing has to be coded or released as a new app version.

What does the free trial include?

The free trial includes access to all platform features for 120 days, hosted by us. It is intended for testing and evaluating whether DynamicForm meets your needs, subject to our Fair Use Policy.

How is DynamicForm priced after the trial?

Commercial terms depend on your requirements and deployment arrangement. Contact sales.dynamicform@agstudioventures.com to discuss continued use after the trial. Customer and partner private-cloud or data-centre deployment is planned.

Is lending the only use?

No. Loan origination is one worked example. DynamicForm supports business processes involving forms, approvals, documents, integrations and field work. We are also testing the platform against requirements for a range of applications and plan to make these available in a sample application library.

What kinds of applications suit DynamicForm?

DynamicForm suits business applications that combine data capture, business rules, workflows, documents, reporting and integrations. Examples include employee leave, field inspections, onboarding, requests and approvals, and case management. Your team describes the requirements, reviews the proposed Business Blueprint and approves what gets built.

Building with AI

Is DynamicForm a RAD or low-code platform?

Yes. DynamicForm is a rapid application development (RAD) platform that builds business applications from configuration. AI Core proposes a Business Blueprint that your team reviews and approves before anything is built. The application runs on the DynamicForm engine using approved configuration and a normalised relational database.

What happens to our requirement document?

AI Core uses your documents and an interview to build one versioned Business Blueprint. It proposes screens, validation rules, mobile layouts, workflow steps, roles, reporting hierarchy, permissions and integration points. Your team reviews and approves everything before anything is built.

Does the requirement document need a special format?

No. Use plain words or upload documents. You can also start without a document by describing the business problem. AI Core asks focused questions to fill the gaps; in our tests, the interview took about 13 questions and roughly 10 minutes.

Can the AI change my app without me?

No. A human review gate approves everything before AI Core builds the application. Your team reviews proposed changes, and changes can be rolled back.

Does the AI write code?

AI Core produces configuration for the platform to run. After approval, it creates a normalised SQL Server schema, menus and list pages checked for load, with capacity and caching advice sized to the server. It publishes a web app and automatically builds a branded Android app.

Does the AI make decisions on live cases?

No. The running application is the platform's engine executing saved configuration. AI is used to build and change that configuration.

Can an application be changed after it goes live?

Yes. Describe the change in plain words; the AI proposes only the difference, and users get it after you save.

Can a proposal be undone?

Yes. AI Core keeps a versioned Business Blueprint, and changes can be rolled back. Your team approves proposals before anything is built.

If an expert can build a custom application with AI in days, why use DynamicForm?

DynamicForm gives your team a shared platform for screens, workflows, menus, identity and publishing. AI Core proposes configuration for review, and your team maintains that configuration as the business changes. The platform runs the approved application.

Our AI-generated custom app is secure and won't change much. Why switch to a platform?

A custom application may suit your needs. DynamicForm is useful when your team wants common tools for configuration, access control, workflows and publishing across several applications. AI Core helps propose changes while your team retains approval.

What about the licensing and intellectual property risks of AI-generated code?

AI Core builds applications from configuration on DynamicForm. Your team still needs to review the terms that apply to the platform, connected services and any other software it uses. Using AI does not remove that responsibility.

Which AI providers can we use?

Gemini and Claude are available now, with structured answers and waiting and retries when a provider is busy. More AI providers — Beta: Try OpenAI, Azure OpenAI and local models through Ollama.

How does AI Core protect uploaded documents and secrets?

Uploaded documents are screened for prompt-injection attempts, tested with a 30-document attack set. Secrets never reach the AI. Your team reviews the resulting blueprint before the build starts.

How do AI Core and the AI Copilot work together?

AI Core turns a business description or documents into a versioned Business Blueprint and builds the application after approval. The AI Copilot helps your team propose and review changes inside the screen, workflow, menu and integration configurators.

Read more

Can I ask the AI to connect a new service to my screen or workflow?

Yes. Screen AI and Workflow AI propose links using existing services, fields and steps. If a connection has not been set up, they hand over to Integration AI to guide that work. Your team reviews the proposed changes before applying them.

Read more

Can Integration AI test against production?

No. An AI probe is a small test to check an assumption. It requires your approval and runs only against a mock or the provider sandbox, never production. The expired-token probe runs against mocks only. Results are saved as evidence for your team to review.

Read more

Does the AI choose our business decision rules?

Your team supplies the decision thresholds that determine workflow routes. The AI does not invent them. Your team reviews the proposed configuration and decides how each integration outcome should affect the screen or workflow.

Read more

Screens, workflows and menus

What can a screen contain?

Use text and number inputs, date pickers, dropdowns, searchable dropdowns, checkboxes, file uploads, mobile OTP fields and action buttons. Text inputs can use subtypes such as email or telephone. The runtime also supports multiline text and email fields through configuration. Embedded-content containers provide an extension point for specialised content. Screens can also contain panels, tabs, repeating and nested sections, calculated fields and embedded child screens.

Can steps run in parallel?

Yes. A split starts several steps at once and a merge waits until all finish.

Can a case be sent back?

Yes. A reviewer can send a case back to an earlier step, and a remark can be made compulsory for that action.

Who can own a workflow step?

A step without a named owner falls to the roles required by its actions, otherwise to company administrators alone. The designer warns about missing ownership. Company administrator actions outside a step's roles are recorded.

Can steps have deadlines?

Yes. Each step can have a deadline in working days, and overdue cases are flagged and passed up.

Can access depend on the process step?

Yes. Each section and field can be editable, read-only or hidden at each step, and the server enforces the same rules.

What can a menu item open?

A blank screen for a new entry, a searchable work list, a report or a group of items, or it can create a case and start its workflow in one click.

Do different users see different menus?

Yes. Menus are given to roles, so each person sees only the items their roles allow, on the web sidebar and on the phone home screen.

Can I reuse a screen inside another screen?

Yes. Embed an existing child screen inside a section of another screen. Reuse its configured layout and fields instead of recreating them individually. Repeating and nested sections let you organise related entries within the parent screen.

Can fields calculate values?

Yes. Calculated fields derive values from configured inputs. Portable numeric formulas run on web and mobile; for example, calculate a line total from quantity and unit price. Technical teams should review the formula language when configuring a calculation for both devices.

Can we add specialised components to a screen?

Yes. Technical teams can use an embedded-content container and a lifecycle script to mount a specialised component in a web screen. This extension requires technical configuration. Android renders HTML content and links; it does not automatically run the same web component scripts.

Mobile

Which mobile platforms are supported?

Android today.

Does the phone app work offline?

Yes. Mobile list pages work offline, and corrections are queued until the device is back online. Forms are stored on the device and sent when the signal returns.

Do we build the mobile app separately?

The same application configuration serves web and Android. After approval, AI Core publishes the web application and builds its branded Android app. Each application has its own mobile identity.

Do users need to update the app when a screen changes?

No. Screens are drawn from their saved design, so users get changes without a new app version.

Can we use our own brand and colours?

Yes. Each application chooses a theme from the company theme library and carries its own logo. The whole web app takes the open application's colours and logo. Android supports System, Light and Dark appearance.

How does DynamicForm adapt a screen for mobile?

The mobile renderer interprets the shared screen configuration. Fields stack vertically, and panels and tab sections become expandable sections. Repeating entries and nested sections remain connected to their parent entry. The presentation changes to suit the device.

Which configured behaviour carries across devices?

The mobile runtime evaluates configured visibility, required-field and read-only rules, portable calculations and dropdown dependencies. Your team should preview and test the configured behaviour on both devices, especially when using technical extensions.

Integrations and security

Can the platform read a provider's API document?

Yes. You can start with a written guide, an Excel field list, plain text or examples of the information sent and returned. Technical inputs are also supported: OpenAPI, Postman collections with environment settings, cURL, WSDL, and JSON or XML samples. Structured files are read directly without AI; the AI extracts relevant details from written documents. The Gap Report then shows which details are supported by evidence, which have been assumed and which are still missing, so your team knows what to check.

Which API security methods are supported?

The security method is how your connection proves it is allowed to use the service. The provider specifies which method you need; a technical colleague can review that choice. DynamicForm supports API keys, Basic authentication, bearer tokens, OAuth 2.0 client credentials, password and refresh token flows, tokens obtained from another call, signed JWT, HMAC and mutual TLS. These cover keys, passwords, temporary access passes, digital signatures and certificates. Tokens are cached for reuse and refreshed once even when several requests need renewal together.

How are outside services secured?

The DynamicForm server makes calls to partner systems using secure outbound authentication. Credentials stay on the server and secrets never reach the AI. Calls are blocked from reaching internal network addresses.

Where can a connected service be used?

You can use a connection when a field changes, a button is clicked, a document is uploaded, a screen opens, a record is saved or a workflow reaches a step. The connection may call one provider or run several calls in a flow. Your team chooses what happens for each result, such as filling a field, displaying a message or taking a different workflow path.

Can we test an integration before going live?

Yes. Start with mocks, which are prepared replies using invented data, or use the provider sandbox, which is its test environment. Inspect the values sent and returned, the fields filled, the outcome and the time taken, with personal data hidden. Save useful runs as test cases so your team can repeat the same checks after a change.

Can I use my own credit or scoring models?

Yes. Models in PMML format or any scoring service can be connected and used at a workflow step.

Can documents fill the form?

Yes. Configure the document upload control to call your company’s chosen document-processing API, such as DocExtract, and map returned values into form fields. Extraction, verification and fraud checks depend on the selected service. Your team reviews the returned information. See the Document Analyzer pages for configuration details.

What if documentation is incomplete?

You can still start. The Gap Report marks information as Known, Assumed or Missing and shows the evidence available for each item. The AI asks one question at a time; if you do not know an answer, it can record a safe default or prepare a question for the provider. The Assumption Ledger keeps those unconfirmed settings visible, with their risk and checking plan. High-risk assumptions must be verified before production; others must be verified or accepted by an approver.

Can the AI publish by itself, and who approves production?

No. The AI proposes settings, and people decide what to apply. Four-eyes approval means the person making the change plus one separate approver; six-eyes approval requires two separate approvers. Approvers are selected from the reporting line and receive requests in their inboxes. The maker cannot approve their own change, and the same person cannot approve twice. The final approver promotes the provider version to Production for real work. This approval process covers provider-version promotion and all reverts. Publishing a flow or saving a logical operation or provider group remains a direct action for authorised users in this release.

Can we build before the sandbox is ready?

Yes. A sandbox is the provider test system; a mock is a prepared reply that simulates the service without calling it. Mock Studio lets you prepare up to 10 request-and-response sets per API using invented data. Use them to check how screens behave when a call succeeds, fails, takes too long or is still pending. A coverage strip shows outcomes that have not been tested. You can save test cases and run them again when the connection changes.

What happens when a provider is down?

Your configured recovery rules determine what happens next. A circuit breaker stops further calls to a provider that is failing. A provider group can switch requests to an eligible backup, called failover, and return to the original provider when it recovers, called failback. Retries can wait longer between attempts instead of repeatedly calling immediately. If a call changes data, it is retried only when the provider supports idempotency, a mechanism that prevents the same request from making the change twice.

How long are call logs kept?

Masked call traces are kept for 90 days by default. A trace records what happened during a service request so the team can investigate a failure or slow reply, while personal information is hidden. Your team can change the retention period within the supported limits. The audit trail serves a different purpose: it records who changed settings, approved requests or performed operational actions, and can be exported to CSV for review.

How do company users sign in?

Set up OpenID Connect, Microsoft Entra ID or SAML 2.0 per company. Company policy can require authenticator-app two-factor sign-in, with lockout after repeated failures. On Android, single sign-on opens in the secure system browser, and authenticator setup and codes work on the phone. A new phone is registered only after the second factor; PIN and biometric sign-in remain available afterwards.

How is each company kept separate?

Each company has its own users, applications, configurations and data, and can run several applications. Its web address or branded app identifies the company, so users never choose one. Configuration, transactions, documents, logs, cache and files are isolated per company. Every endpoint is denied by default unless an access rule allows it. Automated sweeps of every read endpoint found zero cross-company leaks.

Who administers each company?

Each company has its own administrator. Platform operators sign in at a separate address. Any work they do inside a company uses an audited session with a stated reason. The platform console handles onboarding, company web addresses, mobile app keys, suspension and ending sessions.

Can we limit which records a role sees?

Yes. Set a role's record scope to Own, Team through the reporting line, Branch or All. Review scope alongside Permissions and Application access on the role page.

How do API clients authenticate?

Secure API clients can use a client secret, mutual TLS, signed JWT or SAML bearer authentication. These client authentication options are separate from company users’ single sign-on policy.

Are REST, SOAP and GraphQL supported?

Yes. REST connections can use JSON, XML, form values or multipart requests with fields and files. Your provider’s documentation determines the style and format. Your team can map fields, test replies and choose how the application handles results.

Read more

How do we match application fields to a provider’s fields?

Mapping connects your fields to the provider’s inputs and outputs. Transformations can adjust dates, join text or handle lists. Validation checks required values, formats, ranges and conditions before sending a request.

Read more

Can one business service use several providers?

Yes. A provider group can route requests by failover, configured shares, rules, quota, cost, response time or first answer. Provider replies are mapped into the same result fields. Stickiness can keep one case with the same provider.

Read more

Can we connect several service calls into one process?

Yes. An Integration Flow can branch on results, run calls in parallel, repeat work for list items, wait for a delayed reply or run another saved flow. Your team can define compensation steps to undo earlier work. AI can draft the flow for review, and the checker highlights unreachable steps and outcomes with no next action.

Read more

Can a service return its result later?

Yes. A callback brings the provider’s result back when its work is complete. The receiver validates it using the configured signature, token or permitted network address, and repeated copies are processed once. Polling can check for the result within a configured limit. The web screen can update when the result arrives.

Read more

What happens to an integration call when a phone is offline?

If “Queue when offline” is enabled, the call waits until the phone reconnects, then runs without creating duplicates. The phone checks pending results while a form is open and when the app resumes. Results for saved forms appear in Updates for the user to review, apply and save.

Read more

Does a delayed integration result send a phone notification?

Optional push delivery can prompt the app to check a result sooner, using only a reference without personal data. It requires extra server and app setup and is switched off in the documented build. It does not display a notification in the phone’s notification tray; polling on resume handles background results.

Read more

Can we roll back an integration or check what a change will affect?

Yes. Compare saved versions and request a revert, which creates a new version from earlier settings and goes through approval. The Usage tab shows affected screens, flows and provider groups. Direct provider connections can stay on a chosen version or follow compatible updates. Flows, logical operations and provider groups have one live version, so review their connected screens before a breaking change.

Read more

How do we monitor integration problems?

The Monitoring screen shows request counts, outcomes, response times, provider switches, token renewals and pending callbacks. Filter by service, provider or environment and inspect masked traces. Alerts appear on that screen; email and SMS alert delivery are not included in the current release.

Read more

Can browsers, phones or the AI see integration credentials?

No. Keys and passwords are entered into protected storage as write-only values and are not shown back as readable secrets. The server calls the provider. Personal information is masked before it appears in logs, traces or an AI request. Credential audit records describe actions such as rotation without recording the secret itself.

Read more

Can we separate who edits, publishes and manages credentials?

Yes. Viewing settings, editing them, publishing, managing credentials and operating integrations are separate permissions. Provider production promotion and reverts require the configured human approvals. The maker cannot approve their own change.

Read more

What happens if there is no eligible integration approver?

A provider approval request cannot proceed until an administrator sets up an eligible approver in the reporting line. The maker cannot approve it instead, and one person cannot provide both approvals when two separate approvers are required.

Read more

How is company isolation different from row-level data scope?

Company separation keeps each company's users, applications and data apart. Record scope controls which records a role can reach within its application access. Choose Own, Team through the reporting line, Branch or All.

Data and architecture

Which databases are supported?

SQL Server is available today, with business data in normalised relational tables. Additional database options Beta: MySQL / MariaDB and Oracle schema generation, and Azure SQL Database hosting, are available to try in beta.

Can our reporting tools read the data?

Business data is stored in ordinary relational tables that authorised reporting tools can query with SQL. Access must respect the company’s data isolation and permissions.

Can we export our configuration and data?

A solution package moves the application's design, with theme, logo and documents, between the company's environments. Business records are not included. Imports can be checked first with a dry run.

Is there a full history of each case?

Yes. Every workflow move is recorded with who did it, when and the remark, and administrators can see where every case is.

Does DynamicForm replace our existing systems?

No. It sits alongside them: it calls your services, uses your database and serves its screens and data over APIs.

Where can DynamicForm be deployed?

DynamicForm is available as our hosted service. Deployment in a customer or partner private cloud or data centre is planned. Contact us to discuss availability and deployment requirements.

How are platform changes checked?

Every change receives security review, then correctness review before release. The latest checks include more than 2,300 automated tests, company-separation checks, mobile app tests and real-browser walk-throughs.

Who will manage a private deployment?

Customer and partner private deployment is planned. Responsibilities for infrastructure, backups, security patches, platform upgrades and support need to be agreed during deployment planning.

Will a private deployment need internet access?

Private deployment does not by itself mean offline operation. Connectivity depends on the AI provider and third-party services you choose. Review those dependencies during deployment planning. Local AI models through Ollama are available in beta; this does not establish that the entire platform can run without internet access.

What infrastructure will a private deployment require?

Private deployment is planned. The infrastructure specification needs to be agreed for the applications, expected workload and services involved. AI Core provides capacity and caching advice sized to the server; this does not replace deployment planning.

Can partners host DynamicForm for their clients?

Deployment in a partner private cloud or data centre is planned. Hosting, administration, support responsibilities and commercial terms need to be agreed before offering a managed deployment to clients.

Speed at scale

Does it stay fast with heavy data?

Yes. Dashboards and work lists are served from Redis as prepared results, saves return at once while the heavy writing happens in the background, and lists come page by page.

Why do dashboards open quickly even on large data?

Dashboard figures are worked out in the background and kept in Redis, so opening a dashboard reads a prepared answer instead of counting millions of rows.

Are dashboard figures live?

Dashboard figures are prepared in the background on a schedule, which keeps them instant. Case screens, inboxes and saves always work on current data.

Can we add servers as usage grows?

Yes. Several servers can run behind a load balancer. Cache and other data layers remain isolated per company, whether they use a shared store or a separate store. AI Core provides capacity and caching advice sized to the server.

Company administration and applications

Can someone help administer without being a full company administrator?

Yes. Give them a role with the function they need, such as maintaining branches. Company administration shows only the functions their roles grant.

Who can create applications?

Company administrators can create hand-built applications with a code and a name. Every company also has a Main application. AI Core adds an application for each blueprint it builds. It shows as Draft until it is published. The application register brings these applications together with their current statuses.

Can I use my own AI keys?

Yes. Company AI keys serve only your company, and their values are never shown. A wrong company key fails rather than silently switching. Each AI call records whose key it used. Platform keys are available only where the platform allows your company to use them.

Can a role work in several applications?

Yes. The role page has Permissions, Application access and Data scope. Application tabs let you choose the menus the role reaches in each application.

Who decides where my data is stored?

The platform sets which layers may have separate stores. Within that policy, the company administrator chooses stores for each application. Records, documents, files, logs and cache can use company stores or their own stores. Only the affected application pauses during a move.

What happens to a retired application?

The application register shows its status as Retired, alongside Draft and Published applications. Company administrators can retire hand-built applications they no longer need.

Can platform staff see my company?

Only through an audited session with a stated reason. Platform operators use a separate console and sign-in address. Sensitive actions require a fresh PIN or authenticator code. Company administrators continue to manage company settings and application choices within the platform's limits.

How do I limit an API client?

Company administrators choose the applications each API client may reach. A calling system is limited to those applications. Manage clients in Company administration, alongside company sign-in settings. Integration scope separately controls which applications may use each company integration.

What happens after I sign in?

Sign in at your company's address. Your only application opens directly; several applications appear on a dashboard. Tiles show logos or coloured initials, waiting tasks and Draft status where applicable. The header switcher moves between applications and shared areas, and remembers your last application.

What stays at company level?

The company keeps sign-in, users, reporting lines, branches, holidays, roles and Company administration. Integration definitions, scoped API clients, company settings, OTP settings and the theme library also stay shared. Applications keep their own designs, records, identity, logs and any separate stores.

Can I reuse another application's design?

Yes. Browse the company library for screens, workflows, master lists, reports and dashboards. Review the copy plan and its linked items. Link to the target's item with the same code, or copy it. The copy belongs to the target application and remembers its source.

How do integrations stay scoped?

Define an integration once for the company, then choose which applications may use it. Designers see only in-scope integrations. Scope cannot be removed while the integration is in use. Calling systems reach only the applications selected for their API client.

Rules and calculations

Do rules need code?

No. Designers write rules in the rule builder, using Numbers, Text, Dates and Rows, with examples. A rule that does not work is never saved.

Are results the same on the phone?

Line totals update as lines change. Sums, counts, lowest values and highest values give the same result on web, phone and server. The server's value is the value stored.

What are cost classes?

Every rule receives a cost class at design time: Light, Moderate or Heavy. Heavy rules need explicit, recorded acceptance. Rule timings are monitored, giving administrators information for reviewing rules after design.

Configuration document

When can I download the configuration document?

Generate the document with a click from every AI Core step, starting with the first draft. Choose the full document for detailed review or the summary for an overview.

Does AI write the document?

The document is built only from stored configuration and is never written by AI. The same configuration version always gives the same document.

Compliance questions

Beta

Beta features are available to trial and pilot customers and may change before general release.

What does testing establish?

DynamicForm tests and documents a configured application against controls mapped to selected frameworks. Evidence combines tests, signed statements and approved exceptions. The report records its scope and limitations, helping reviewers understand what the evidence covers.

How are verdicts expressed?

The report gives an outcome for each selected framework.

  • Compliant with the DynamicForm control catalogue for the selected framework.
  • Compliant with the DynamicForm control catalogue for the selected framework, with exceptions. Approved, unexpired exceptions appear on the report's first page.
  • Not compliant with the DynamicForm control catalogue for the selected framework.

The verdict is calculated from tests, signed statements and approved exceptions, never typed.

Who approves an exception?

An exception needs a reason, an expiry and a different approver.

Does this replace examinations?

No. A regulator's, auditor's or assessor's own examination remains separate. The report does not replace an external VAPT, a QSA assessment or an auditor's opinion. It does not replace a SOX opinion, SOC 2 or ISO 27001.

Does a passing report mean there are no vulnerabilities?

No test report proves that no vulnerability exists. DynamicForm records tests and their evidence, acknowledged limitations and exceptions. Read those details alongside the report scope when deciding what further examination you need.

Does AI run inside my live application?

No. AI is used only while designing. Compliance tests are generated from the saved configuration without AI. A behaviour test checks that the running application makes no AI service calls.

Does DynamicForm store card numbers?

Card fields hold only a token and the last 4 digits. DynamicForm does not store full card numbers, CVV or PIN. These boundaries matter when designing which information your application collects.

Are screening services included?

DynamicForm does not supply sanctions or politically exposed person list data. It does not supply transaction monitoring. The Beta KYC onboarding template includes a screening connection and a suspicious-transaction case with approval.

Are identity services included?

DynamicForm connects to licensed Aadhaar e-KYC, CKYC and V-CIP services; it does not provide those services. The Beta KYC template includes e-KYC and CKYC connections and a V-CIP session screen.

Are infrastructure controls included?

No. DynamicForm does not provide a web application firewall or protection against distributed denial-of-service attacks. It provides neither a security operations centre nor a disaster recovery site. The report includes environment checks alongside application tests and platform security evidence.

How are statements collected?

Named people receive assignments through their inbox and sign fixed-wording statements in the product. Evidence uploads undergo virus scanning. Statements have validity periods, and company-wide answers can be reused across applications.

When does evidence change?

A report belongs to an application version. Any application change marks it superseded. Daily re-checks and framework badges help track currency. Publishing can be blocked until the report is approved. Readers can verify the report using its QR code or verification code.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Explore DynamicForm

Compliance · Rules and calculations

Updated 16 November 2026