Sharing and Embedding for Water Treatment Yield Reports

Data sources include water project operation management systems and online water quality monitoring platforms. Data is updated daily, with summary

What the data for this category looks like

Data sources include water project operation management systems and online water quality monitoring platforms. Data is updated daily, with summary data generated for the previous natural day. The documents are structured daily report files, containing these fields:

  • Project code
  • Daily treatment volume (unit: cubic meters)
  • Reclaimed water output (unit: cubic meters)
  • Chemical consumption cost (unit: yuan)
  • Electricity consumption cost (unit: yuan)
  • Operation and maintenance labor cost (unit: yuan)
  • Current total revenue (unit: yuan)
  • Current net profit (unit: yuan)
  • Effluent turbidity (unit: NTU)
  • Operation duration (unit: hours)

Each daily report has a fixed number of fields. Daily reports for different projects only differ in field values, with no additional unstructured content.

What constraints these characteristics impose on the "Sharing and Embedding" workflow

Daily updated data requires embedded components to use a matching cache cycle to avoid pulling outdated daily report data. Mixed units across fields require configuring unified formatting rules during embedding to ensure clear, standardized display of values such as amounts, water volumes, and turbidity. Structured data containing sensitive enterprise operation information requires enabling authentication and access restrictions in the sharing process to prevent unauthorized access to internal operation data. The fixed field structure combined with the need to filter by project requires embedded components to support passing parameters such as project code to dynamically load dedicated data for the corresponding project. In addition, water treatment daily reports are mostly displayed on internal enterprise large screens or operation documents, so embedded components need to support responsive layout configuration to adapt to different container sizes.

Configuration Settings

Configuration ItemRecommended SettingRationale
share_auth_enabledEnabledWater treatment daily reports contain sensitive enterprise operation data, so unauthorized access must be restricted
share_cache_ttl86400 secondsWater treatment daily reports are updated once per day. The cache cycle matches the update frequency to reduce internal system interface call volume
embed_responsive_modeAdaptive container widthAdapt to embedding scenarios such as enterprise large screens and internal documents with varying sizes
embed_param_whitelist["project_code", "date"]Water treatment daily reports require filtering data by project and date. Only allow necessary parameters to avoid unauthorized access
share_link_expire_days7 daysLimit access permissions for old links to avoid long-term exposure of sensitive data
embed_allow_originEnterprise internal domain name listRestrict embedding scenarios to internal enterprise networks to prevent unauthorized external embedding

The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Individual analysis is required for specific issues. It is recommended to conduct testing on local samples before finalizing settings.

Three Common Configuration Errors

  • Scenario: Embedded component returns 403 Forbidden error after loading. Cause: share_auth_enabled is not enabled, or the access IP is not added to the embed_allow_origin whitelist.
  • Scenario: Embedded component displays outdated daily report data from three days prior. Cause: share_cache_ttl is not set to a duration matching the update cycle. An overly long cache expiration period prevents pulling the latest data.
  • Scenario: External devices cannot access locally deployed shared links. Cause: embed_allow_origin does not include the access domain name or IP of the external device, or authentication rules are not properly adjusted to support login-free access.

How to Verify Proper Configuration

  • Access the preset shared link, pass the specified project code and date parameters, and verify that the daily report data for the corresponding project and day loads correctly.
  • Open the embedded component display page, check that units and numerical precision of fields meet expectations, and confirm that the component size adapts to the current display container.
  • Wait 24 hours, then refresh the embedded page, and verify that the latest generated daily report data loads.
  • Attempt to access the shared link from a domain name or IP not included in the whitelist, and verify that access is blocked and content cannot be loaded normally.

Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.