Content and Actions Model

Content Model for Use Actions, Functions and Flows

Key Pages

Default App View: File List

Individual Document View

• EG A doc preview screen for a PDF

Individual Attestations and Claims View

• This a HTML/CSS display of the contents of the JSON attestations and claims file objects, named on that wiki page.

Files

Documents

Attestations and Claims

Actions

Upload a File

Sign a File

• The user can 1 select a file to sign from the file list (and also perhaps from the file view directly if we wish) and 2 take an action to "sign the file".
• The above action should display the file to use for the to inspect and provide a "sign" action if/when they are ready to execute their digital signature on that file.
• The result of the signature function changes the "state" of the file in the file list from unsigned to signed by the user.

Share File

• This requies selection of a file and use takes action to share file.
• When above happens the useer should be presented a type-in filed to identify the other user to whom a request for signature is to be transmitted. This will be an email for our demo and could be a name.id, CU Member ID or public key or other identifier in future.

Make Request Signature on File

Receive Request for Signature on File

This is a "notice" action that requires only that the user has seen the information on screen that they have a received a request to sign a file.

• This action is another way for a file to be added to the users file store (a PDF for example from external user)
• The notice should include a method (like a thing to click) for the user to 1 see the file they are requested to sign (it should appear in a doc list too) and 2 be able to sign it if they so choose.