Consents - Revision history

Rdaverio: /* Bulk operations on consent records */

2019-06-14T15:19:46Z

‎Bulk operations on consent records

Rdaverio: /* Bulk operations on consent records */

2019-06-14T14:12:25Z

‎Bulk operations on consent records

Rdaverio: /* Bulk operations on consent records */

2019-06-14T14:10:20Z

‎Bulk operations on consent records

Rdaverio at 13:30, 18 February 2019

2019-02-18T13:30:57Z

Rdaverio: /* Bulk operations on consent records */

2018-11-20T11:34:05Z

‎Bulk operations on consent records

Rdaverio: /* Consent Mail Structure and Procedure */

2018-11-20T11:00:53Z

‎Consent Mail Structure and Procedure

Cberetta: /* Information */

2018-10-23T07:47:44Z

‎Information

Cbisso: /* Bulk operations on consent records */

2018-10-19T10:28:00Z

‎Bulk operations on consent records

Cbisso: /* Bulk operations on consent records */

2018-10-19T09:51:28Z

‎Bulk operations on consent records

Cbisso: /* Bulk operations on consent records */

2018-10-19T09:51:17Z

‎Bulk operations on consent records

@@ Line 235: / Line 235: @@
 |-
 |<u>Description</u>||record description.||Optional||Optional||Optional
 |-
 |<u>Lang</u>||''Data Subject'' selected language.||Optional||Optional||Optional

@@ Line 199: / Line 199: @@
 * "remove": Removal of ''consents''
-The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''scope'' will be removed.
+All the ''consent'' matched by ''data subject'' <u>email</u> on Privacy Now® ''service'' will be removed.
 * "wrongemail": Move ''consents'' in status "Wrong Email"
-The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''scope'' will be moved in "Wrong Email" status. Only consent in "Valid" status can be moved in "Wrong Email" status.
+All the ''consent'' matched by ''data subject'' <u>email</u> on Privacy Now® ''service'' will be moved in "Wrong Email" status. Only consent in "Valid" status can be moved in "Wrong Email" status.

@@ Line 228: / Line 228: @@
 |<u>Username</u>||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional
 |-
-|<u>Consent</u>||<u>Consent Type Code</u> to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory
+|<u>Consent</u>||<u>Consent Type Code</u> to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Optional||Optional
 |-
 |<u>Value</u>|| <u>Consent Value</u> given by ''Data Subject'' for the imported <u>Consent Type</u>. The value could be "1" (''consent'' granted) or "0" (''consent'' not granted).||Mandatory||Optional||Optional
@@ Line 236: / Line 236: @@
 |<u>Description</u>||record description.||Optional||Optional||Optional
 |-
-|<u>Service</u>||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional
+|<u>Service</u>||Privacy Now® ''service'' used as import target.||Mandatory||Mandatory||Mandatory
 |-
 |<u>Lang</u>||''Data Subject'' selected language.||Optional||Optional||Optional
@@ Line 242: / Line 242: @@
 |<u>uid</u>||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional
 |-
-|<u>Scope</u>||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory
+|<u>Scope</u>||A key word defining univocally the acquiring system.||Mandatory||Optional||Optional
 |-
 |<u>Operation</u>||This field specify which is the operation expected for current xlsx record: "insert", "remove" or "wrongemail"||Mandatory||Mandatory||Mandatory

@@ Line 125: / Line 125: @@
 Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: <u>Consent_'''[consent name]'''</u> , <u>Value_'''[consent name]'''</u> and <u>Date_Time_'''[consent name]'''</u>.
-Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on <u>Consent_'''[consent name]'''</u>, <u>Scope</u> and the option selected in <u>Data Subject Matching criteria</u>.
+Each ''consent'' present in mail will create a new record or update an existing record in Privacy-Now®. The existence of a consent is matched on <u>Consent_'''[consent name]'''</u>, <u>Scope</u> and the option selected in <u>Data Subject Matching criteria</u>.
 {| class="wikitable"

@@ Line 195: / Line 195: @@
 The operations allowed are:
 * "insert": Insert/Update of ''consents''
-The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''consent type'' code, ''data subject'' <u>email</u> and ''source'', otherwise a new ''consent'' will be created.
+The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''consent type'' code, ''data subject'' <u>email</u> and ''scope'', otherwise a new ''consent'' will be created.
 If ''data subject'' is not found: it will be created.
 * "remove": Removal of ''consents''
-The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''source'' will be removed.
+The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''scope'' will be removed.
 * "wrongemail": Move ''consents'' in status "Wrong Email"
-The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''source'' will be moved in "Wrong Email" status. Only consent in "Valid" status can be moved in "Wrong Email" status.
+The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''scope'' will be moved in "Wrong Email" status. Only consent in "Valid" status can be moved in "Wrong Email" status.
@@ Line 242: / Line 242: @@
 |<u>uid</u>||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional
 |-
-|<u>Source</u>||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory
+|<u>Scope</u>||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory
 |-
 |<u>Operation</u>||This field specify which is the operation expected for current xlsx record: "insert", "remove" or "wrongemail"||Mandatory||Mandatory||Mandatory

@@ Line 118: / Line 118: @@
 === Consent Mail Structure and Procedure ===
-Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).
+Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Scope Details|Consents Scope Details]]).
 A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).
@@ Line 125: / Line 125: @@
 Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: <u>Consent_'''[consent name]'''</u> , <u>Value_'''[consent name]'''</u> and <u>Date_Time_'''[consent name]'''</u>.
-Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on <u>Consent_'''[consent name]'''</u>, <u>Source</u> and the option selected in <u>Data Subject Matching criteria</u>.
+Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on <u>Consent_'''[consent name]'''</u>, <u>Scope</u> and the option selected in <u>Data Subject Matching criteria</u>.
 {| class="wikitable"
 ! Field !! Description
 |-
-|<u>Source</u>|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.
+|<u>Source</u>|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' scope(ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Scopes'''''.
 |-
 |<u>Name</u>|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.
@@ Line 146: / Line 146: @@
 |<u>Phone</u>|| The phone number of ''data subject''.
 |-
-|<u>User_id</u>|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).
+|<u>User_id</u>|| The univocal id (integer) of the user corresponding to ''data subject'' in consent scope(ie: id of user in web site).
 |-
-|<u>Username</u>|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).
+|<u>Username</u>|| The univocal login of the user corresponding to ''data subject'' in consent scope(ie: login of user in web site).
 |-
 |<u>IP_address</u>|| The ip address used by ''data subject'' during web site browsing.

@@ Line 35: / Line 35: @@
 * <u>''Consent Details''</u>, with the details of the ''consent'';
-Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.
+It's possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.
 When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).

@@ Line 232: / Line 232: @@
 |<u>Value</u>|| <u>Consent Value</u> given by ''Data Subject'' for the imported <u>Consent Type</u>. The value could be "1" (''consent'' granted) or "0" (''consent'' not granted).||Mandatory||Optional||Optional
 |-
-|<u>Data</u>||''consent'' date.||Mandatory||Optional||Optional
+|<u>Date</u>||''consent'' date.||Mandatory||Optional||Optional
 |-
 |<u>Description</u>||record description.||Optional||Optional||Optional

@@ Line 191: / Line 191: @@
   [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]
@@ Line 204: / Line 203: @@
 * "wrongemail": Move ''consents'' in status "Wrong Email"
 The ''consent'' matched by ''consent type'' code, ''data subject'' <u>email</u> and ''source'' will be moved in "Wrong Email" status. Only consent in "Valid" status can be moved in "Wrong Email" status.