There are a lot of scenarios here so let me try to cover them one by one.
In general, you specify the default value for the property in the Entity Framework designer, and when the object is created, DevForce will set those properties to their default values. This doesn't solve the problem that the Entity Framework does not get the default from SQL Server, but within DevForce, there should not be a problem where validation fails before the default value is set.
Now for the specific cases:
If want the server to record the Owner for the record (instead of doing this in the client) you can do this in the EntityServerSaveInterceptor. Here, by overriding ExecuteSave(), you can modify the Order's Owner to the current user just before the save.
For primary key fields, DevForce has an IIdGenerator interface that allows the client to create new records with temporary ids and the server will assign them the permanent primary keys just before save. DevForce will then will fixup the object graph to correct all the foreign key references to the permanent primary key value.
I believe you may be working with our professional services, so we can go over these patterns in more detail when you're ready to start.