EDSA FieldTrack Connector
| 开发者 | edsadev |
|---|---|
| 更新时间 | 2026年6月8日 12:43 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Adds a FieldTrack settings page in WordPress.
- Provides the
[edsafico_request_form]shortcode. - Stores customer service requests in a local WordPress request inbox.
- Lets admins choose which FieldTrack-mapped form fields appear on the request form.
- Lets admins add custom intake fields that sync to FieldTrack internal notes.
- Lets admins customize service type choices.
- Supports optional photo/document uploads.
- Supports optional Cloudflare Turnstile or Google reCAPTCHA v2 spam protection.
- Provides editable admin and customer email templates.
- Gives admins request statuses for new, reviewed, sent, failed, duplicate, and rejected requests.
- Lets admins manually send or retry a reviewed request to FieldTrack.
- Can automatically create a FieldTrack work order after submission.
- Stores FieldTrack sync status, sync logs, and returned work-order keys on the WordPress request.
- Can refresh the latest FieldTrack work-order status after sync, including via WP-Cron.
安装:
- Upload the
edsa-fieldtrack-connectorfolder to/wp-content/plugins/. - Activate the plugin through the WordPress Plugins screen.
- Subscribe to EDSA FieldTrack if you do not already have an active FieldTrack subscription.
- In EDSA FieldTrack, open Customer Portal and generate a WordPress connector token.
- In WordPress, go to FieldTrack > Settings.
- Enter the FieldTrack service URL, tenant ID, and connector token.
- Test the connection.
- Configure form fields, service type choices, email templates, and spam protection as needed.
- Add
[edsafico_request_form]to the page where customers should request service.
常见问题:
Is an EDSA FieldTrack subscription required?
The WordPress connector plugin can be installed in WordPress, but FieldTrack sync features require an active paid EDSA FieldTrack subscription. Without a subscription, tenant ID, and connector token, requests can be stored locally in WordPress but cannot be synced into FieldTrack.
Does this replace FieldTrack?
No. WordPress handles intake and review. EDSA FieldTrack remains the operational system for work orders, technicians, customers, invoices, payments, status tracking, and reporting.
Can I review requests before they become work orders?
Yes. Leave automatic sync disabled. Requests will appear in WordPress under FieldTrack > Requests, where an admin can review and send them to FieldTrack.
Can requests create work orders automatically?
Yes. Enable automatic sync in FieldTrack > Settings. Automatic sync requires a valid FieldTrack tenant ID and connector token.
Can I control which fields appear on the form?
Yes. FieldTrack > Settings lets admins show, hide, require, and relabel FieldTrack-mapped fields. Admins can also add custom fields that are saved in WordPress and sent to FieldTrack as internal notes.
Does the plugin send customer data to EDSA?
Yes, when FieldTrack sync is used. The plugin sends service request details to the configured EDSA FieldTrack service URL so FieldTrack can create or track work orders for the configured tenant.
How do I subscribe to FieldTrack?
Use the Subscribe to FieldTrack button on the plugin settings screen, choose a CORE FieldTrack package, complete checkout, then generate the connector token from FieldTrack.
更新日志:
- Updated the WordPress.org contributor username.
- Moved public form styles and spam-provider scripts to WordPress enqueue APIs.
- Replaced generic plugin-owned identifiers and shortcode names with the unique
edsaficoprefix.
- Clarified that FieldTrack sync requires a paid EDSA FieldTrack subscription.
- Added configurable FieldTrack-mapped form fields.
- Added custom intake fields that sync into FieldTrack internal notes.
- Added configurable service type choices.
- Added optional Cloudflare Turnstile and Google reCAPTCHA v2 spam protection.
- Added editable admin and customer email templates.
- Added sync retry labeling and recent sync logs.
- Added automatic status refresh using WP-Cron.
- Expanded privacy and external service disclosures.
- Initial lightweight FieldTrack connector.
- Added service request shortcode.
- Added local WordPress request inbox.
- Added manual and automatic FieldTrack work-order sync.
- Added FieldTrack connector token connection test.
- Added request review statuses and FieldTrack status refresh support.