Floworks Deployment Guide

Management of Change Form

Going forward all updates to the Floworks Field Service Platform or any related support and/or versioning software changes require a Change Form to be completed and authorized before deployment. Change Forms are to be signed, scanned and attached to the Floworks Release Notes Page under the corresponding version notes.

Testing Updates in Development Environment

Prior to Version 2.2

After all necessary Client and Internal Changes have been made to environment, it is required to fully test the new changes on the Github "FloworksDev" Repository before production deployment. Please ensure that all database changes occur as expected on the test laptop and that any new XML is generated successfully and placed in C:\Outbox. See Github Commands & Troubleshooting for instructions on pushing changes to the Dev/Production repositories.

Version 2.2 and later

All syncing is now done via rsync. Localhost can be used as a development environment.

Pushing an update to the field laptops

Version 2.2 and later

As of version 2.2, FloWorks no longer uses Github as its source control (syncing) mechanism. FloWorks has been moved a RSync-based system, please refer to the FloWorks RSync Page for more details and how to push changes to the field clients. As with previous versions, please ensure that the version number is updated appropriately in config.php within the Floworks core prior to pushing the new version.

Prior to Version 2.2

Please ensure that the version number is updated appropriately in config.php within the Floworks core prior to pushing the new version. Once again please reference the Github Commands & Troubleshooting page for instructions on how to push the update. You should begin seeing the new version number embedded in field generated documents (as well as .lastlogin) files shortly.