Jump to content

GDPR - Consent Data Capture


admin

Recommended Posts

If you want to create your own Consent capture details - but don't know how to create a new data frame then this is for you. 

 

Whilst the information can be found within the Online Guides that Open GI produce, the User Group have produced a guidance video for your assistance - press the play button on the video below.

 

Let us know if you find this useful - and any other topics you may want covered!

 

  • Like 1
  • Thanks 1
Link to post

Thank you for the video on how to create the GDPR frame.  We have now done this.

We will be adding it to our clients level one, F11 to create a Client Profile but I cant seem to do a database enquiry on it.

If I phone Open GI it will take days for them to get back to me.

Does anyone have any ideas please??

Thank you

Carol Davies

Link to post

Hi Carol - First off - well done for creating the frame !!

 

As for the Database report - there are a Three Top Tips ....

  1. Use BL1.Module - to search for "Clients" with that frame type
  2. Prefix the Profile (Fact Find) frame keywords with "F." on the report (so [XX.Line01] becomes [F.XX.Line01]
  3. Have a look at the on-line guide which explains in more detail 

Hope that helps - let me know if you need some more info - but I'm sure you'll be off and running now :)

 

Mark

Link to post
  • 3 weeks later...

I tried to make my frame as 'user-friendly' as possible so made all the consent given/retracted dates auto populate based on when questions answered/changed.

GDPR1.png

GDPR2.png

GDPR3.png

GDPR4.png

Link to post
  • 1 year later...

Is everyone confident that they have purged the old data, which they should not be retaining?

For example, a policy that can only have a claim against it two years after it was taken out versus one where a child might be injured and claim 15+ years later.

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • There will be issues whichever way - so you need to pick the right way for you at get it right first time.   In short - and from experience  on both sides - I'd say transfer now to your server, as separate branches. This may involve some logistics for connectivity (I don't know your set-up) but on the face of it - is better than running multiple servers and multiple business processes. You'll thank yourself in the long run   Moving / migrating / transferring / consolidating to one branch - on the same server - is far, far easier to manage once the data is on one platform. Trust me on this.
    • We were thinking to merge on our system but can well foresee a few issues 🙂  
    • not to any great extent so this shouldn't be a problem but thanks again  
    • Sorry Sandra - Are you planning to merge the branches on THEIR system - or merge and migrate to your server?   The first is as everyone has said above - the latter is potentially a whole new world of complexity - x 10!
    • Just thought, do you/they use Open Attach?
×
×
  • Create New...