What the product does.
WexaFlow provides a native Finance workspace for flow configuration and data exploration. Workspace visibility and Free/premium capability distinctions have been observed in an authenticated development session.
That observation does not establish end-to-end flow, query, job or premium integration execution. The agreed workflow and data-field behaviour need runtime acceptance before operational use.
Product capabilities
Native workflow workspace
Prepare and review the workflow in the Finance environment your team uses.
- Flow configuration workspace
- Data-exploration evaluation
- Capability visibility based on the issued grant
Product-specific tenant licensing
Access is granted for a registered tenant and a named set of product capabilities.
- Free and premium capability scope
- Flow, run, query, row, node and concurrency limits defined by the grant
- Tenant registration does not activate every product
- No automatic trial or key issuance
Premium operation scope
Integration and automation capabilities must be included in the agreed premium grant and tested in the proposed setup.
- HTTP integration scope
- Package jobs, schedules and triggers
- Email, file and hook capabilities
- End-to-end operational acceptance is pending
Evaluate the relevant tasks.
Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.
- Describe one workflow from its initiating event to the expected result, using anonymised records.
- Confirm Finance application/platform versions, package dependencies, evaluation roles and company context.
- Review flow configuration and the data fields required by the workflow; record missing or unsupported behaviour.
- Confirm which nodes and external operations need premium scope, and the quotas associated with the proposed tenant grant.
- Agree a controlled execution test and failure scenario before any query, flow, job or integration is run.
- Define customer installation, runtime acceptance, support and licence activation responsibilities for delivery.
Workflow walkthroughs
Review a representative flow
Connect the business requirement to the flow configuration and data it needs.
- Identify the initiating event, records and expected output
- Review the available workspace and nodes
- Confirm field metadata, company context and permissions
- Record the execution and failure scenarios that still need acceptance
Confirm a tenant capability grant
Establish the exact edition, capabilities and limits in the proposed licence.
- Confirm the intended tenant and product
- Review Free or premium capabilities needed by the workflow
- Confirm quotas and any external-system requirements
- Agree how the grant, activation and support will be delivered
Prepare operational acceptance
Establish a testable boundary before executing the workflow.
- Choose non-sensitive sample data and a permitted environment
- Agree the expected result and failure behaviour
- Arrange execution only within the confirmed evaluation scope
- Record results, unresolved cases and the owner of delivery acceptance
Prepare a useful support request.
Include the WexaFlow package, Finance versions, flow scenario and the capability or field behaviour needing review.
- Use anonymised flow descriptions, table/field names and error messages.
- Include the node type and licence capability involved when known.
- Omit tenant keys, tokens, credentials and sensitive business records.
- State whether the issue concerns configuration, data fields, a grant or an agreed execution test.
Your questions, answered.
Does the observed workspace mean every flow operation is accepted?
No. Workspace and capability visibility have been observed in development. Full flow execution and premium integrations still require acceptance for the agreed environment.
Which quotas does Free access include?
Limits belong to the issued tenant grant. Confirm the exact flow, run, query, row, node and concurrency limits in the proposal rather than assuming a public default.
Are HTTP, schedules and email part of Free access?
Those operations require premium capability scope. Their licence and runtime requirements are confirmed before activation and use.