What this category of data looks like
This category of data typically originates from content data, advertising revenue sharing systems, financial systems, and creator account backends. Daily associated documents include incentive rules, settlement details, appeal records, and payment lists. Data update cycles are mostly monthly or aligned with individual operational campaigns. Data fields usually include creator identifiers, revenue accounting items, settlement cycles, appeal status, and payment progress. Units include yuan, items, person-times, and others, with no unified fixed format. All fields must match the output specifications of their respective systems. This category differs from creator onboarding and certification scenarios, as it centers on revenue calculation and payment processes. Forms must therefore prioritize fields related to revenue accounting and payment.
What constraints these characteristics impose on the "forms and interactions" workflow
Multiple data sources require cross-system field mapping via external business systems or subsequent workflow nodes to eliminate duplicate errors from manual entry. Monthly or campaign-level update cycles require external business systems or subsequent workflow nodes to support bulk import of datasets such as settlement details and appeal records. The time-intensive nature of revenue caliber verification and payment material validation requires external business systems or subsequent workflow nodes to implement field validity check rules and automatically flag abnormal fields. The risk of settlement disputes, incorrect payments, and missed payments requires external business systems or subsequent workflow nodes to retain complete operation logs and data traceability entries for subsequent verification. Multi-role access requirements for creators, operations teams, and finance teams also require external business systems or subsequent workflow nodes to configure fine-grained permission division rules.
How to configure settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Form input node formInput | Test example: Select 3 fields from creator incentive settlement data as required inputs; actual fields are determined by the task | This node collects user input; required items must be checked for interaction status to prevent subsequent nodes from receiving incomplete input |
User selection node userSelect | Test example: Set 2 business options, check corresponding branches one by one | This node handles user selection; querying and filtering records related to creator incentive settlement must be implemented by subsequent interfaces or external systems |
| Post-submission field passing | Test example: Prepare 10 creator incentive settlement input samples, covering complete filling, missing required items, and canceled operations | Compare input and node output to verify whether subsequent nodes receive corresponding fields; result thresholds are determined by the actual task |
| External implementation item: Bulk import field mapping (handled by external business systems or subsequent nodes) | Must be implemented separately by external systems; match standard field structures for settlement details and appeal records | Adapt to business requirements for multi-source data import |
| External implementation item: Bulk submission timeout threshold (configured by external business systems or subsequent nodes) | Must be implemented separately by external systems; 600 seconds | Adapt to processing duration for monthly bulk settlement data |
| External implementation item: Bulk import entry limit (configured by external business systems or subsequent nodes) | Must be implemented separately by external systems; 1000 entries | Adapt to scale limits for single bulk processing |
Three common configuration mistakes
- Phenomenon: Pulling the
formInputnode configuration via a share link (shareId) returns no valid data. Cause: The share access permission for theformInputnode was not configured, only internal use-related settings for theformInputnode were set. - Phenomenon: A system permission error pops up when user input interaction is triggered. Cause: Permission authorization rules relying on external interaction services were not configured; this type of interaction function must be implemented using external services.
- Phenomenon: Some data fails to map successfully when importing settlement details in bulk. Cause: The field order in the import template does not match the field mapping rules configured by the external business system or subsequent nodes, and data was not arranged in the preset field order.
How to verify proper configuration
- Pull the
formInputnode configuration via a share link (shareId), confirm that the returned fields match the presetformInputnode configuration. - Test the input function relying on external interaction services: enter a query statement, confirm that corresponding settlement detail data is returned within 3 seconds, with no system permission errors.
- Import the bulk settlement detail template, confirm that external business systems or subsequent workflow nodes automatically flag abnormal fields and generate a verification report.
- Switch between different role accounts, confirm that only authorized roles can access form configurations and settlement data.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.