Real case of one of our prospects (now a Harmony customer) describing from flowchart to a fully working system (1) customer delivered a flowchart pdf, (2) we converted this to a Lucidchart - supporting collaboration in the cloud (3) the flowchart was then used to generate the system. We ran the system with our customer, we updated the Harmony configuration, which is stored in a Google DOCS spreadsheets, using his comments. We generated a new version ... and the cycle started again. The 1st "cut" of the application was created in one (1) hour !!

1. Creating a Harmony system in one hour
Demonstrating the power of
Harmony
Delivering a Proof-of-Concept (PoC)

2. Our (new) customer created a flowchart

3. We converted this to a Lucid Chart flowchart

4. We generated the Harmony application
• Importing the LucidChart flowchart
• The application/system was generated
– In 1 minute
And
• a Harmony configuation (the “source”
file) was shared via Google DOCS
• Next step:
– running the application

5. About the generated application
• It generated all process (workflow) steps
• Using decisions
– controlling the workflow
• It generated two database files
– Customer & Product
• Using the definition in the flowchart
– One sample entry (record) in each file
• With Harmony comes pre-defined & auto generated:
– User groups/authorization [sheets]
– Decision support [user interface (UI)
– History overview (UI showing all completed steps)

6. Running the generated application 1st
step
Customer registration

7. Step 2
Product specification

8. Etc, etc
• It will run all process (workflow) steps
– We check with customer
– and change the configuration
• About the modified configuration
– because this is stored in Google DOCS spreadsheet
format
• it’s easy to understand, hence easy to change
• It’s shared with the customer
– We created structures
– Customer added data
– We added extra fields (data input) to the screens
• Doesn’t make sense to specify this in flowchart (or other
diagramming tools)
– etc

9. Modifying dialogs: how to
• add more details to dialogs
– is very simple to do

10. Defining the workflow
controlling the dialog flow (sequence)

11. Create two expressions
• Expressions can be
– Computation
– Concatenations
– etc

12. re-generate the application
• Application is generated
– in one minute
• Check by running the application again

13. No changes in this user interface/dialog

14. If product exists -> create quote
• All decisions are displayed in decision support

15. Product does not exist ->
different dialog & workflow step
• Determine product is required

16. forgot something ?
• The new version:

17. The workflow continues

18. Standard with Google maps integration

19. Added “conditionally displayed” fields
• Add rules that control which dialog items are displayed
– If not satisfied: prompt “notes”

20. How to conditionally display fields
• Initially hide a dialog
• Create a rule

21. Some Notes
• Creating the flowchart was done by the customer
– This gave us a pretty good idea of what he wanted (he also
shared some of his quote samples (i.e. “data”)
• After creating a high-level flowchart we continued with
Harmony
– Creating process details is much easier with Harmony …
using data to verify if the correct actions are taken!
• Next steps involved:
– Verify with customer
– Add Harmony building blocks (like generating and sharing
order quotes)
– Create Testimony test.sheet (which is 5 min job)
– Asking customer to enter test data and start testing
• Which is fully automated with Testimony

22. Some more info
• Lucidchart
– flowchart (used in this PoC)
– Lucidchart event driven modeling
• Get started
– Creating Harmony applications
• Step-by-step explanation
• YouTube Samples of Testing with
Testimony