Version history
Version history
New features and options in the consent version history.
What's new in SIMA version 21.08.03!
Canary Islands market
Consent modifications
After clicking, a web page is displayed that allows viewing two different views:
- Customer view: the customer is usually present and we can sign a second time after modifying consents.
- Full Administration view: the customer is not present and all consents can be modified, with a justifying comment collected.
Full administrator view
- This view can be used by Opportunity staff or any operator dealing with the customer remotely without the customer being present.
- After modifying consents, the system will ask for an observation justifying the change.
- Modifications coming from the external CRM system will be justified with an observation indicating the origin of the change. Sales force — these observations will be visible from the history search we will see later.
Customer view
- The difference here is that with each modification, the user or customer can record the reason for the consent change.
- The customer also has the option of a second signature.
Signature options
Here we have three possible options:
- Sign: the signature is collected on the device itself.
- Print to sign: the document with consents is printed, to be signed on paper, scanned and uploaded later.
- Sign on another tablet or device: applied when sharing a tablet or other device that allows signing. The initial capture is distinguished from a second signature and must be directed to the specific page of each company where consents are collected.
Change history
From the Administrator view it will now be possible to access the history of changes in consents, saving snapshots of each modification at a complete level.
From this option the user can access the complete history of consent changes, where they can consult:
- The date/time of that change
- The user who records the change
- The reference to the external system (SalesForce/CRM) if applicable
Another example, when the origin of the change comes from the CRM: