Be signed into your github account
Click into packages/webapp/src/containers/ConsentForm/Versions
To update integration ensure you are on develop branch
To update production ensure you are on master branch
This is the folder that is holding the different consent form files
To replace a file, first make sure its a .docx file and is named correctly so that it can replace the older versions of the same name
So currently either ‘OwnerConsentForm.docx’ or ‘WorkerConsentForm.docx’
The contents of each word file must begin with Version <Version Number>:, e.g. Version 1.0:
The app determines the document version by reading the string between positions of the first occurance of a space character and a colon. It does not matter how long the version number string is.
When a user(not new) chooses a farm upon login, the version number in the document is compared with the number recorded in the database. Users will be redirected to /consent page if the numbers do not agree. Once agreed, the new version number is updated on the database.
Once you are ready to upload files to this folder, click on top right ‘add file’ button, then ‘upload file’
Select the replacement consent form file from your computer. Once you have done this, at the bottom of the screen you can write any message desired or not and click commit
Note: you may not be able to directly commit to the branch if you are not an admin user. You may need to request admin user access from an existing admin or alternatively commit to a branch and then merge in.
Ways to check successful update:
In the versions folder, see that no new file was added, it was merely replacing the old file (if the name was the same this would be the case)
Can also wait for the build and double check the live version ~ 15 minutes