Search K
Appearance
ProjectWise Document Changed ​
Polls a Bentley ProjectWise repository on a defined schedule and fires the workflow whenever documents have been added or updated since the last run, passing the full list of changed documents downstream.
Purpose ​
Use this trigger to build workflows that respond to document activity in ProjectWise — for example, sending notifications, syncing metadata to an external system, or publishing files — without requiring manual intervention. The trigger runs on a cron schedule, checks for changes since it last ran, and passes the complete list of changed documents to the workflow in a single execution. Use a Loop node downstream to process each document individually.
Service Account ​
Requires a Bentley ProjectWise service account configured with the WSG server URL, datasource, username, and password.
Inputs ​
| Label | Type | Required | Description |
|---|---|---|---|
| Poll Schedule | Schedule | Yes | Cron expression controlling how often ProjectWise is checked for changes. |
Outputs ​
| Name | Type | Description |
|---|---|---|
| Changes | List | A list of PWInstance document objects — each containing the document's instanceId, Name, UpdateTime, and all other WSG properties returned for that document. |
| ChangeCount | Number | The total number of changed documents found in this run. |
Manual / Debug Run ​
Clicking Run Now on the trigger fires it immediately without waiting for the cron schedule. The trigger polls ProjectWise directly and returns all documents updated in the last 24 hours. The output shape is identical to a scheduled run, so the rest of the workflow executes normally.
Important Limitations ​
Change detection uses UpdateTime polling
ProjectWise does not expose a change event stream that is consistent across all installation types. This trigger detects changes by querying the WSG Document endpoint filtered on UpdateTime. This approach works on both on-premise and cloud-hosted (Bentley Data Hub) installations.
Deleted documents are not detected
Because deleted documents no longer appear in the document listing, this trigger cannot detect deletions. Only documents that have been added or modified will appear in the output.
Changes during engine downtime may be missed
The last-run timestamp is held in memory and resets when the automation engine restarts. If documents are updated while the engine is offline, those changes will not be captured on restart — the cursor moves forward from the restart time, not from when the engine last ran.
It is safe to shut down the automation engine during quiet periods where no document activity is expected. If the engine is restarted and nothing changed while it was down, the trigger will resume normally with no missed events and no flood of historical documents.
If the engine experiences an unplanned restart during an active period, any documents updated during the outage window will not trigger the workflow. Users should manually re-trigger affected documents if required.