Consent notes while testing

[Cantor, Scott]

On 11/17/14, 10:08 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>Oh, right, that's a missing TODO. I have a note to look at your auditing 
>code.

I don't think we need the same degree of extensibility here, because the 
flow is V1 and we're not trying to expose a lot of guts. But it really 
depends how easy it is to separate the code populating audit fields from 
the code that knows what the data is.

>The consent context holds current and previous Consent objects.
>Consent object IDs are passed as parameters. For every Consent ID
>received as input from the user, the ExtractConsent action sets
>approved to true, which otherwise defaults to false.
>
>Is that quick explanation enough ?

Enough to start with.

Basically what I have to figure out is, can we use a separate action that 
uses lookup functions to populate the audit fields (that's how most of the 
other fields get populated now), or do we need to just hardwrire in some 
field population code in (probably) ExtractConsent.

And of course have to figure out what the actual fields to record should 
be.

I don't see any reason not to just add them to the existing record for SSO.

-- Scott