Variables

Setup Guide continued...

We’ll know when this template has been copied over to a new doc, by comparing the doc’s Created() timestamp with the timestamp we know that this doc was completed. If this doc is a copy, then we’ll display a notice at the top of

Encryption Template

⁠

urging the user to visit the

Finish Installation

⁠

page to complete all steps of the full setup flow.

Note that when a doc (or part thereof) is copied, all text inputs’ Created() timestamps are reset as Coda builds the new copy. When Coda copies a page over to another doc, it seems to build the components of the page one at a time, so it’s usual for their timestamp to be 15-30 seconds after the Doc’s Created() timestamp. This is handy to know, and is leveraged in this doc to determine whether or not the Published Form link for

Submit New Secret

⁠

needs to be updated. We’ll know if it requires an update when its Modified() timestamp is within a few seconds of the Doc’s Created() timestamp.

DateTime:

5/3/2022 6:20:36 PM

⁠

⁠

This is the datetime this Doc was created.

DateTime:

5/3/2022, 3:00:00 PM

⁠

⁠

This is the datetime this template doc was completed.

Bool:

true

⁠

⁠

If this doc’s Created() timestamp is later than the timestamp I’ve hardcoded as this template’s VAR Template Publish Timestamp value, then we know this is a copy.

Bool:

false

⁠

⁠

If the user hasn’t updated the

Submit New Secret

⁠

published form link since the copy has been made, then this toggles to true.

Fake Submit Button

This is the FAKE button I use at the bottom of the

New Secret

⁠

form.

Fake Decrypt Button

On the

Decrypt Secret

⁠

page, the user needs to “click away” from the password field to trigger the decryption. To encourage them to do so, we have a face “decrypt” button that actually does nothing.

Published Forms

URL:

https://coda.io/form/Submit-New-Secret_d25AMJqXi6x

⁠

⁠

The first form,

New Secret

⁠

has a Fake Submit Button that takes the user to the second form (this link).

This form requires the Encrypted Text, the Salt, and Title which are all passed via parameters in the URL, effectively pre-filling the fields’ values. The user then just clicks Submit and their encrypted data is saved to the table without much effort.

Current item:

[ ]

⁠

⁠

This is the row that the user is currently viewing on the

Decrypt Secret

⁠

page.

Character Mapping

Current Characters:

0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ”–’‘‚“‐‒—!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿

⁠

This is a string containing the currently supported characters. If a character is not in this field, it will be dropped during the encryption process. To manage supported characters, head over to

Setup and Config

⁠

(requires that you selected the Custom Setup option when you copied this template to your doc). As per my frustrated comments on

What's Changed?

⁠

, the [newline] character is automatically added as an additional character.

Value:

false

⁠

⁠

If an individual character appears more than once in the Character Mapping text field, then this toggles to TRUE. When TRUE, the user is prompted to re-cache the character mapping, using buttons which appear:

- Under “Custom Setup” on

Dear Diary...

⁠

- At the top of

Setup and Config

⁠