Setting up
Set up in this order: install the app, fill the GDPR ToolBox Setup page, maintain the setup lists, then the table guidelines and the data structure. Do it with a user who has the app's setup role (Julia Beyer); the other users only need the basic role for their normal work.
-
Install the app. Search for Extensions Management, install QUALIA GDPR ToolBox and let Business Central restart the client.
-
(Optional) run the setup wizard. The app is not registered in Assisted Setup, so search for QUALIA GDPR ToolBox Setup and open the wizard. Choose Next, turn on Install Demo Data, choose the Language of the demo data (English, German or Polish) and choose Next and Finish. The wizard fills the setup lists, the record type STANDARD, the table guidelines and the data structure TENANT with its tables, fields and relations; it only installs data in a company that has no GDPR ToolBox data yet. The wizard does not fill the GDPR ToolBox Setup page (step 4). QUALIA's setup is done by hand in steps 4 to 9, so Julia Beyer runs the wizard without the demo data.
-
Give users their roles. In Business Central, assign the app's permission sets: Setup to Julia Beyer, Officer to Lena Hartmann and Basic User to Max Keller and the other users. The job queue account (JOBQ) runs the background jobs.
-
Open the GDPR ToolBox Setup page and complete it (search for GDPR ToolBox Setup):
- In Request No. Series, enter the series for requesting persons, here RQ.
- Enter the status codes the requests move through: Initial Status Code INI, Await Response Status Code AWAIT, Wait Status Code WAIT, Process Status Code PROC, Rejected Status Code REJ, Done Status Code DONE. These codes also drive the request cues on the role center.
- Under Job Queue for, turn on Job Queue for Scheduled Actions, Job Queue for Action Suggestions, Job Queue for Processing Action Suggestions and Job Queue to Import Details and Consents, and enter Max. Job Queue Retries, here 3.
- Turn on Reschedule Actions so changed records move their scheduled action with the default reschedule reason.
-
Create the job queue entries from the setup. On the Actions tab of the GDPR ToolBox Setup page, choose Scheduled Activity, then Action Suggestion, then Process Suggestions and Process Import Details and Consents. Each action creates a job queue entry for the app's codeunit if none exists yet; give each entry a start time so JOBQ runs it. Action Suggestion and Process Suggestions run the same job queue task, so they open the same entry: three entries exist in the end (scheduled actions, suggestions, import).
-
Maintain the setup lists (search for each name and enter the lines with New):
-
Protection Classes: SK-1, SK-2, SK-3. For the selected class choose Protection Levels and enter the levels 1 to 7 of class SK-1.
-
Record Types: STANDARD, Protection Class SK-1, Protection Level 3, Action Date Formula 5Y, Action Type Delete.
-
Data Collection Reasons: CONTRACT, LEGAL, MARKETING.
-
Data Source Codes: WEB (Campaign on), EXPO (Campaign on), REFERRAL. The Campaign flag opens the campaign field on the GDPR details.
-
Verification Codes: PASSPORT, ID_CARD, VIDEOCALL.
-
Reschedule Reasons: AUTO (Default on), DELAY.
-
Data Processing Purposes: NEWSLETTER and MARKETING with Segment Allowed on, BILLING.
-
Data Processing Consents: EMAIL "E-mail marketing", POST "Post and phone marketing". Choose a consent and use Process Purposes to say which purposes it grants (EMAIL grants NEWSLETTER and MARKETING).
-
Request Status: INI Initial, AWAIT Awaiting Response, WAIT Wait for person, PROC In Process, REJ Rejected, DONE Done.
-
Enter the table guidelines for the tables with personal data (search for Table Guidelines, choose New):
- Contact: Record Type Code STANDARD, Action Date Formula 5Y, Action Type Delete; also turn on Requesting Selection Allowed so a requesting person can be linked to a contact.
- Customer: STANDARD, 5Y, Delete.
- Sales Header: STANDARD, 5Y, Delete with Dynamic Action Type.
- Posted Sales Invoice: STANDARD, 10Y, Action Type Anonymize, Scheduled Action (Field No.) = Posting Date, Always allow Anonymization, Execute Delete Trigger and Collection Reason Code CONTRACT; this table has many records, so also switch on Manual Scheduled Action and give it the action indicator field so the job queue writes the actions in batches.
-
Create the data structure (search for Data Structures, choose New): code TENANT, description "Tenants: Contact, Customer, Invoices". Choose Tables and build the tree:
-
Add the lines 100 Contact (primary key), 200 Customer (relation to line 100, key Contact Business Relation, "Business Relation Code" = CUSTOMER), 300 Contact Business Relation (relation to line 100) and 400 Posted Sales Invoice (relation to line 200, key 6, export name Sales_Invoices); Indent and Unindent set the levels. The Table Filter that limits each line to the records of its parent comes with the structure configuration and is shown as Table Filter in the personal data view.
-
On each line open Table Fieldsetup and add the personal fields from the table's list (Contact: No., Name, E-Mail, Phone No., Address, City, Job Title; Customer: No., Name, Address, Contact, E-Mail; Posted Sales Invoice: Sell-to Name, Bill-to Name, Ship-to Address, Phone No.). Use Renumber Line No. so each field has its own line number.
-
On the Posted Sales Invoice line, open the Output Field List and add Document No., Posting Date and Bill-to Name; the line then shows Output Fieldlist Active and the information report and CSV export use this list.
-
Finish with standard Business Central work:
-
Search for Change Log Setup and turn on logging so the Change &Log action on the GDPR details pages can show history: the action reads the change log entries of the master data record (for example Customer or Contact), and the Change Log Entries list itself opens only while the change log is active. Activate logging for the master data tables you want to follow; without it the action says there are no change log entries for the table (see Common messages you may see).
-
In Database Table Trigger Setup, activate the trigger for Contact, Customer, Sales Header and Posted Sales Invoice. Without this trigger the app does not see new records, so no scheduled actions are created automatically.
-
Make sure the job queue is running on the server and that JOBQ has a license for the background work.
-
Schedule the old data. After the setup, choose Creating Actions from Historical Data on the GDPR ToolBox Setup page to create scheduled actions for the records that already existed, such as the posted invoice SINV0001 from 2018.
From now on, work with the app is done on the Role Center, which counts scheduled actions and requests by status; open it from the role selector.
