I’ve been asked to build my first content type. During the discussion it was determined for this Reporting Request workflow to create a Base “Report Asset” to be used in a workflow\survey to determine what exactly the end user is requesting. e.g. A crystal report hosted in BusinessObjects, a data dump for an excel spreadsheet, Tabular Model, SSIS ETL for a vendor….
Then once that base “Report Asset” exists we want to track dependencies of the report in another content type “Report Dependencies” each related dependency would be its own row, e.g datasource= SQL2012, Database = AdventureWorks, Command = “usp_GetOrders”, Developer = “Tom”, modified_date = now….
Another content type for future changes to the asset would track each change in a “Report Change Log” content type and another content type “Report Change Log Result”. The result log would basically track whether or not the DBA approved or rejected the change in the “Report Change Log” and the reason for failure if the Change was not approved and flag the change as back to a draft mode.
I watched a SharePoint Workflow demonstration and also have read up a bit on them and it seems I might not be able to attach individual workflow(Stages?) to the individual lists.
I was surprised I could not find an example or post for a report request workflow on the web. I am not sure if a Service Desk workflow is similar enough. I am also trying to fill out the MS content type spreadsheet and the two rows of examples they have seem very limited in explaining what default items might be in a list.
If I buried all those columns into into one “Report Lifecycle” content type it seems like I’d have a lot of empty columns most of the time. And maybe that does not matter. I am trying to comprehend how I maintain changes to the content type to be able to track the history.
So my first “Report Request” form would fill out the first few columns which Could be Report name, Report Writer, Originating Data Source, Report Requested by, Department, Report Type…
Then a second “Report Dependencies” form would only show the columns for Data Source – Reporting Database, Stored Procedure, SQL Writer, Peer Review… But here is the begin of the mess. I have have 20 tables to list as dependencies would I really want to create 30 columns to hold whatever might come?
On the third form “Report Change Request” would need a column to describe the change, who is requesting it, I’d assume it would pull in the report’s information.
Fourth form would be something like “Report Change Log” with columns for Reviewer name, review text, and a flag for the Approved, Denied….
Thanks,
Phil
Then a
