Workflows

Default Workflow - New project, SQL Database, Single Solution, Datalayer + Webservices

User creates project/solution
User creates a AU Context - Adds connection to a database
User configures context settings
- TBD
User configures standard queries (or selects them from presets) Create, Retreive, Update, Delete, Search, etc...
User is shown a list of all available tables (can filter / Select all, Select none, etc) - User can also specify a "group" key to combine tables/views/etc into a single logical unit. These selections are persisted so if a query template is updated all instances can be updated as well.
User is presented with a list of other db objects such as views and stored procedures (Can auto populate labels based on source table?)
Once user clicks "generate" queries will be auto generated against all selected objects

User views queries by "group" - typically this is the associated table name but can be overridden by a custom group name.
User can automatically add queries either from unused templates, or from scratch
User can override any query and re-write it by hand - If queries are regenerated overrides will be flagged for review
User can modify templates and re-run
On save user will be presented with a list of warnings (conflicts, uncompileable queries, etc...)
User can add labels to objects or queries to help classify and filter objects/actions during code generation

User creates new "node" and links it to either the context or another node (context always contains a "root" node)
User creates a "group" - A group contains "categories" that are user created so you can break all properties into subsets based on labels, metadata, etc
- Todo: This needs a better name
User can attach templates to each category - Each template will have a filename property and generated properties will be created in the same directory by template name
TODO: Actions vs Objects