Getting Started

Mangologic is a system with two main components.

Mangologic Web

Login and configure apps.

Mangologic Android

Download and use the apps you have configured

You use Mangologic to produce the mobile systems you need.

Getting Started

This is one of three Getting Started presentations available.

They each cover a major aspect of Mangologic:

● Apps● Process Logic● Deployment

So you want to define some logic?

Processes in Mangologic

A Process in Mangologic is usually an interactive dialogue with the user.

Typically it presents the user with questions and may also execute defined actions which, for example, record information in the database.

Mangologic makes it easy to define logic to make questions appearing and actions happening conditional upon what the user has told us.

Mangologic Web

When you login you see two tabs: Projects and Deployments.

A Project is where we configure Apps and Processes and other things.

A Deployment is where we manage the deployment of an App we have created.

Click on the +Project button and add a new project

● Give a name for the Project● Select the default language

Projects can have the status “Test” or “Production”. This is just to help you organise your work. The status of any project can be changed at any time.

● Check the “This is a Test Project” checkbox

● Click Ok button

The new Project appears listed in the Test table.

If you click on the project name, editing functions would appear on the right.

You can “go into” the Project itself by clicking on the Go button..

Click on the Go button and go into the new Project

The “breadcrumb trail” at the top shows your email and the name of the Project you are working on.

Elements of the breadcrumb trail are clickable (for easy navigation). You can click on your email to go back to the top-level.

A default app has been created for this project already.

● Select the Processes tab

● Click on the +Process button and add a new Process

● Give the Process a name

● Click Ok button

Now we are in the Process configuration. We see the “Process Level” tabs.

The most important tabs by far, and the only ones we will deal with in this presentation are Nodes and Conditions.

Nodes are steps in the process we define.

Conditions represent certain logic we define. We can use that logic to choreograph the dialogue - to make it adaptive to specific circumstances.

About Nodes first - there are three types of Node:

❖ Interaction❖ Action❖ Section

Interactions are usually questions. There is just one kind of interaction which is not a question - Display only lets you just show messages to the user without requiring input.

● Select to add a Display only node

● Enter “Hello” into pop-up window

● Click Ok button

So now we have a node - a Display Only node with the message “Hello”.

If you select the node, you will see editing controls for that node on the right.

You can edit the text of the node by clicking as indicated by the arrow.

Most interaction nodes are questions - which receive input from the user. You will be familiar with the different kinds available (such as Yes/no questions, Number input questions, etc.)

They are added in the same way you added the Display Only node.

Each different interaction type requires slightly different configuration.

Note: a new node is added immediately following the currently selected node (or at the end of the process if no node is selected).

In contrast with Interactions, Action nodes define steps in the process which are not visible to the user.

One important thing we can do with actions, for example, is record (and update) information in the device database.

One can define other kinds of actions - such as sending an SMS.

So the content of a Process is made up primarily of Interaction nodes and Action nodes.

Here is a screenshot showing part of a typical (complex) Process “tree” structure.

● Section nodes are shown in black.● Interaction nodes are shown in blue.● Action nodes are shown in green

Nodes can be moved around in the Process by drag and drop.

Nodes are shown preceded by numbers signalling their position in the process. Some nodes also appear with an “If” condition in parentheses.

This indicates a pre-condition. If a node has a pre-condition, a node is only used if the pre-condition is satisfied.

Look at node 9.8.3 above. The question asks how long has pus been draining from the child’s ear. The name of the pre-condition suggests that we only ask 9.8.3 if we already know there is pus coming from the ear (which makes sense).

Pre-conditions are defined in the Conditions tab.

Conditions are defined by point and click in terms of the information provided by the user. With the “Ear - pus yes” condition selected in the list here, we can see its definition on the right.

The definition means: the condition is true if the user responded Yes to question 9.8.2 “Does the child have PUS draining from the EAR?”

Mangologic maintains and shows references.

With the Ear-pus yes condition selected, we can click on the References tab on the right and see that it is in fact used as a pre-condition of three nodes (other nodes clearly later recommend treatment for pus).

The References tab also shows that this condition is used in the definition of a meta-condition. What is a meta-condition?

Meta-conditions

We should make a big deal about meta-conditions, hence this separate slide.

A meta-condition is simply the combination of other conditions via a logical operator such as AND or OR.

It is easy to define conditions by “point and click” based on questions. It is just as easy to define meta-conditions by “point and click” - simply select some conditions and select an operator.

The conditions with a meta-condition definition can include meta-conditions. The conclusion is: it is easy to define very complex logic!

Here is the meta-condition containing the “Ear pus yes” condition. It is called “Classify chronic ear infection”. It has three conditions within it and the operator is “All”. This means the meta-condition is true if all sub-conditions are true. -

Classify as chronic ear infection any ear pus which has lasted more than 14 days and we have ruled out mastoiditis

Let us follow this through - Not mastoiditis is also a meta-condition - it contains just one condition “Classify mastoiditis” and the operator is “None”

So “Not mastoiditis” is true if “Classify mastoiditis” is not true.

“Classify mastoiditis” is true if the user answered “Yes” to the question 9.8.4 which asks whether the child has tender swelling behind the ear.

This complex logic is entirely intelligible to (and definable by) non-programmers!