This domain model would suggest that Status is not a property of Orders. And that an order points to a specific status. If you really want to use this domain model you need the Microflow to retrieve from the database the object with the status you would like to set on the order and change the Orders_Status association and set it with the retrieved status.
However my suggestion would be:
This is better because: if you accidentally change the Status object it would change the status for all related Orders, and that’s definitely not the behaviour you want.
More in detail: let’s say you have 3 statusses: New, Pending and Paid defined in the Enumeration and you create an instance (a row) of Status in the database for each Enumeration value, the database would look like this:
ID | OrderStatus
1 | New
2 | Pending
3 | Paid
And the Orders entity refers to the Status entity which means they are related based on the id. Accidently changing object 1 | New to 1 | Pending would thus change all Orders related to 1 from new to pending. Since status is actually a property of Order I would suggest you place it on Orders, and once the DatePaid changes, this attribute is change via Change object in the save Microflow
p.s. off topic advice: Use singular, don’t use plural for entity names, use Order instead of Orders