Configuration

Application Directories

You will need to create an application configuration directory prior to setting up the demo application. The directory can be a local directory or a shared directory like MS OneDrive. Create a top-level directory that contains two subdirectories. The two subdirectories are required to be named InputFiles and OutputFiles. The OutputFiles directory contains a subdirectory that is required to have an email address as the name.

Example:

Directory	Description
Hedera Transactions	Top-level directory that contains subdirectories the application reads and writes data to.
InputFiles	The directory the application reads files from. This includes transactions (.tx), account information (.info), public key (.pub), CSV (.csv) and software update (.pkg) files. The account info file name must not include dashes ex. test-1.info. These are displayed on the 'Home' screen as new tasks.
OutputFiles	The application writes to this directory that is specific to the user.
[e-mail]	Transactions the user signs with the application are stored here.