Bug: in rare instances invalid QR Codes encoding on Document Templates is produced

[garysharp]

When generating a Document Template pages can optionally have a DiscoAttachmentId field which will be replaced with a QR Code which uniquely identifies the document, creation time/user, template id, etc. This QR Code contains a binary encoding syntax which is non-standard. In rare instances, the encoder/decoder fails to correctly transmit the document identification.
While there are benefits to embedding this information directly into the document, it may be better to move back to a standard QR Code encoding method.
A document would be provisioned a GUID and would be encoded as DiscoICT://v3/XXXXX/YYYYYYYYYYYYYYYYYYYYYY where X is a checksum that identifies the Disco ICT deployment (so a document can be tracked back to a Disco ICT instance) and Y is the Base64-encoded 128-bit GUID.
The GUID would be stored in a new database table along with all the other metadata (creation time, target, tech user, template id, etc)