• ISmartWorklist: support membership in a smart worklist
• IBillable: support automated creation of ledger items
• IDecisionStep: support membership in a workflow

• Use a database trigger to populate some queue (e.g. QBO 2 Events)
• pros: any method changing the table will result in an item in a queue
• cons: a lot of items in the queue, triggers slow bulk operations down
• Use C# event infrastructure to raise appropriate events when a class is being inserted or updated
• pros: does not impact database performance, can filter items in the application tier
• cons: extra overhead on every insert/update, does not trap for updates made outside the application tier
• Poll the database for possible changes
• pros: any method changing the table will result in an item in a queue, no trigger contention
• cons: need an UpdateDate index for every table being polled to prevent constant table scans

• Worklist A: all Valuations in a Status of QC Review
• filter : Status IN ('QC Review')
• Worklist B: all Valuations in a Status of Awaiting Assignment
• filter : Status IN ('Awaiting Assignment')
• Worklist C: all Valuations of type Appraisal not in a completed Status
• filter: ValuationType = 'Appraisal' AND Status NOT IN (Final Status List)

• Add stuff that's not there but should be, and
• Remove stuff that's there but should no longer be

• Database trigger: 
• pros: {Filter.RecentlyUpdate/InSmartWorklist} narrow to a primary key
• cons: every update puts an items in a queue, with db trigger overhead; many of these queued items won't impact the worklists at all
• C# events: 
• pros: {Filter.RecentlyUpdate/InSmartWorklist} narrow to a primary key
• cons:  every update puts an items in a queue, with C# event overhead added
• Polling:
• pros: SQL will efficiently process the {Filter.SmartWorklistFilter} clause against multiple rows (e.g. all recently changed Valuations)
• cons: {Filter.RecentlyUpdated/InSmartWorklist} are more expensive than a primary key check

• Completed,
• Cancelled, or
• has an error condition

• Compression
• Encryption
• File Watcher
• List
• Version control
• Returning FileInfo (e.g. size on disk, etc.)

• Passing data via IDataReader, XmlReader 
• Complete control over file naming
• Saving to multiple file locations (e.g. local and client's FTP site)
• Producing a Zip file of 10,000 BPOs
• Open XML SDK integration
• Bulk generation (e.g. generate a contract for 10K brokers)

• Replacing existing EventQueue calls
• Generating 10,000 documents
• QDS integration
• Supporting callbacks (QDS posting data back)
• Geo-coding 10,000 Contacts against Google or Bing

• No need for Events to run workflow
• Windows Workflow Foundation integration
• Synchronous or asynchronous processing
• Strong error trapping
• Strong logging
• Setting parent status on start or completion

• AppliesTo (string): name of the parent object the template applies to (e.g. a DecisionTemplate may apply to a Loan)
• Repeatable (Repeatability): defines how often an instance may occur per parent
• One: (0) only one instance per parent is allowed
• OneActive (1) only one active instance per parent is allowed
• Many: (2) may instances per parent are allowed
• CustomStatusList (bool): defines whether an instance has a template-driven status list
• CustomTypeList (bool): defines whether an instance has a template-driven type list
• ExtranetEnabled (Extranet): determins if an instance requires ObjectAccess rows added

{Instance}.ashx/Summary?Object={Parent}&ObjectID={ParentID}&TemplateID={TemplateID}

ImportForm.ashx/Summary?Object=Loan&ObjectID=127&TemplateID=16

ImportForm.ashx/Summary?Object=Organization&ObjectID=3&TemplateID=27

• ImportFormTemplate.Repeatable = 0: if an ImportForm row based on the TemplateID exists, it is selected ("reused")
• ImportFormTemplate.Repeatable = 1: if an ImportForm row based on the TemplateID and with no ActualCompletion date exists, it is selected ("reused")
• ImportFormTemplate.Repeatable = 2: no existing ImportForm row will be selected, effectively creating a new row