When Adding or Modifying Records in WPS on Windows is an automation trigger for starting a workflow when a record changes in a WPS database table; it includes 2 core tasks, with 2 available without membership and 0 membership-related items.
At a Glance
| Metric | Value | Notes |
|---|---|---|
| Core tasks | 2 | Matches the number of rows in the How-to Index |
| Available without membership | 2 | Matches the number of Free rows in the index |
| Membership-related items | 0 | Matches the number of membership-related rows in the index |
About This Feature
Overview
When Adding or Modifying Records is a built-in automation trigger in WPS Office for Windows database tables. It starts a workflow when a new record is added or when a selected field in an existing record is modified.
Core tasks include:
- Select the trigger condition for a blank workflow.
- Configure the trigger by choosing the target table, target field, and additional filter conditions.
This feature is useful for change notifications, status-based workflow routing, and table-driven business processes. It helps reduce repeated manual checking and lets one trigger cover both newly added and updated records.
System Requirements
| Item | Requirement |
|---|---|
| Operating system | A Windows device that can run WPS Office normally |
| App version | The latest version of WPS Office is recommended |
| Network | An internet connection is recommended when creating, saving, and enabling workflows |
| Other | You need access to the target database table and permission to edit automation workflows |
Download & Installation
| Item | Details |
|---|---|
| Official download | WPS Office Free Download |
| Check after installation | Open WPS Office, open the database table, and confirm that the Automation entry is available in the upper-right area |
Source: WPS download page
Compare with Alternatives
| Dimension | WPS | Microsoft | Notion | Adobe | |
|---|---|---|---|---|---|
| Capability Summary | In a WPS database table, you can create a blank workflow, choose When Adding or Modifying Records as the trigger, then set the target table, field, and filter conditions. | Microsoft SharePoint Connector in Power Automate includes When an item is created or modified, which starts a flow when a list item is created or changed. | Google Sheets can respond to spreadsheet edits through Apps Script triggers such as onEdit(e), which is more script-based than an in-product table automation panel. | Notion database automations support Page added and Property edited triggers for database changes. | Adobe Acrobat Sign automation triggers focus on agreement and signing events rather than record changes in a database-style table. |
| WPS Advantages | Advantage: one trigger covers both newly added and modified records. Distinct: the setup can directly target a table, a field, and extra conditions in the trigger settings. | Compared with WPS: supports created-or-modified events, but mainly in SharePoint list and Power Automate scenarios. | Compared with WPS: supports edit-based automation, but usually requires script setup and is centered on spreadsheet events. | Compared with WPS: supports database change triggers, but database automations are available on paid plans and depend on database access permissions. | Compared with WPS: better aligned with document-signing workflows than record-based table automation. |
| Official Source | — | Microsoft SharePoint Connector in Power Automate | Simple Triggers in Apps Script | Database automations | Triggers for Power Automate flows |
Overall Conclusion
If you want to start a workflow directly from record changes inside a WPS database table, WPS provides a table-focused setup path. Microsoft and Notion offer similar automation ideas in their own list or database environments, while Adobe centers its official automation triggers on document-signing events.
Use Cases
| No. | Scenario | Suitable For | Main Pain Point | How This Feature Helps |
|---|---|---|---|---|
| 1 | Start a workflow after a new record is added | Operations, sales, project teams | New records need manual follow-up | Use the trigger to start follow-up actions when a new record appears |
| 2 | Send a workflow signal when a key field changes | Data owners, collaboration teams | Important field changes are easy to miss | Select the target field so the workflow starts when that field is modified |
| 3 | Run only for records that meet conditions | Business owners | Triggering on every change creates noise | Add extra conditions so only matching record changes continue |
| 4 | Connect multiple tables in one process | Cross-team workflows | Handoffs between tables depend on manual work | Choose the target table as the starting point for later automation steps |
| 5 | Review failed runs through logs | Workflow maintainers | Failures are hard to diagnose | Check logs, then adjust the table or field settings and test again |
Membership & Benefits
Free vs WPS Premium
| Capability | Free | WPS Premium |
|---|---|---|
| Use the When Adding or Modifying Records trigger in database tables | Available | Available |
| Basic PDF features | Available | Available |
| Cloud storage | 1 GB | 20 GB depending on plan |
| Template downloads | Limited | More templates and expanded benefits |
| Advanced PDF and some AI features | Limited or plan-based | More features depending on the selected plan |
Source: WPS Office pricing page
Recommendations
| Scenario | Recommended Plan | Why |
|---|---|---|
| You only need basic record-change automation in database tables | Free | This feature can be used without membership, so the free plan is suitable for initial workflow setup |
| You also need more cloud storage, templates, or broader office features | WPS Premium | A paid plan is more suitable when your work also depends on expanded PDF, storage, or other office benefits |
How to Subscribe
- Subscribe here: Get WPS Premium
Source: WPS Office pricing page