I recently created an SDR within the AA workspace project. The thinking is that users should be encouraged to use the AA workspace tool as much as possible, as compared to generating an excel based SDR that has to be stored externally.
Some examples of what I built
1) a picture of the different sections of the SDR - ![](https://publish-p13952-e135760.adobeaemcloud.com/content/dam/baici_sandbox/AA_InTool_SDR.png)
2) a picture of the different panels, one for each variable (props illustrated) indicated its number, its name and whether or not the variable is enabled
![](https://publish-p13952-e135760.adobeaemcloud.com/content/dam/baici_sandbox/AA_InTool_SDR_listofProps.png)
3) an overview of a specific variable details.
![](https://publish-p13952-e135760.adobeaemcloud.com/content/dam/baici_sandbox/AA_InTool_SDR_PropPanel.png)
I get that there are some items in this example that might not be easy to automate, like the BRD reference number with a hyperlink,
but I think it would be great to have a tool in the AA admin areas that would generate an SDR template within Workspace grabbing all the information it can from the AA admin area report suite traffic and conversion variable screens.
UX: The admin would click a button, the script would create an AA project, add panels for all the evars, props and events and then pull in the details from the admin area. The script would have to be smart enough to know how many panels to generate - meaning company A may have 10 props where company B may have 30 props enabled. The script would have to check to see the 'largest' number variable (prop10 for example) that was enabled, use that number as an input and generate that number of panels.
The template should have additional placeholders for the 'BRD requirement number' and 'administrator notes', so you can then encourage adobe admins to fill in the missing details.
Longer term, it would be great to be able to click a button and 'update' the SDR project with any new information, not overriding the information that was entered in manually (like BRD reference number), but that might be too much to ask as an initial idea.
I also have an example of a BRD and a Tech Spec document I built within the tool as well. Meaning this idea could be expanded to include all types of documentation templates.
Given the flexibility of AA workspace, I don't see why we (as a community) can't document everything within the AA tool.
On a side note, I just saw Adobe's EXCEL based "adobe_analytics_inherited_implementation_playbook" that was just released. Again, why was this was done in Excel when Workspace's API could have been used, is beyond me.