31% of Part II — dates, conditions, and verifying the result.
3 tasks · this deck covers task 3 of 3
↑ Update Profile Attributes OverviewA date-driven attribute update is exactly the kind of flow that's easy to get subtly wrong — a timezone slip, an off-by-one in Add/Subtract, an Expression that's true when you expected false. Before it ships, run it.
The general testing discipline — the Run button, execution history, reading how data passed through each card — is covered there in depth. This slide adds only what's specific to a dates-and-attributes flow.
For a date-calculation flow, that execution history is what lets you confirm the actual computed value at each step — the raw Now output, what Add or Subtract produced, and the true/false the Expression card returned — rather than just trusting the logic looks right on paper.
Test Connection lets you point a test run at a real or temporary connection so date math resolves against real profile data. Feed test data for the Options/Inputs a real trigger would supply (a user ID, a term-start date), then read the execution history at the Expression card specifically — that's where a date/time bug in this use case actually surfaces as a wrong true/false.
Watch for this in your own sandbox run:
→ Testing the flow once with a single hand-picked date and assuming it's correct — retest with a date right at the boundary condition (exactly on the term-end date, one second before/after).
Sources: help.okta.com — Test your flows (type=wf&id=ext-connectorbuilder-test); cross-referenced with Troubleshooting Flows, Module 1