Workflow and process logic

While creating a Fliplet app you may want to automate changes based on a user’s actions eg: based on a user’s answer to a question you may want to show a different screen. For this you’ll need to use Fliplet’s workflow logic. Workflow options can broadly be broken down into the following groups:

1. Triggers - inputs that start a workflow eg: clicks, swipes, screen changes
2. Actions - the actions to take eg: update screen content, send a notification, save data
3. Conditions - switching actions based on an input eg: “if this is true then do that”
4. Data storage and retrieval - work with stored numbers, text strings, files and contextual values (eg user ID or current time)
5. Manipulating data and custom functions - data calculations and manipulations, if statements and loops, time and date manipulation

To maximise versatility, Fliplet offers a “low-code” approach to workflow features. We provide Javascript based APIs and code snippets to allow users to manipulate app screens, data and components. A full list of Fliplet’s APIs can be found on our developer site. A summary of the potential options is provided below.

For all but the simplest workflows you will probably need to use Fliplet's developer options. Despite the name you do not have to be a developer to use these. While some workflows will require you to understand Javascript most can be created by copying and editing standard code snippets. And if you get stuck you can always chat to our Customer Success team via the help button in Fliplet Studio.

Fliplet's developer options can be found in the right hand menu of Fliplet studio. They provide three areas to add HTML, CSS and Javascript (as well as code libraries). For examples of the code snippets you can use to interact with Fliplet apps please see our developer site.

Triggers are the inputs that start a particular workflow process. They typically originate from a users interaction with an app but can also be time based. Some of the common triggers available through Fliplet are:

1. Screen load (run when a screen is viewed)
2. Gestures (triggered by taps, clicks, swipes, buttons)
3. Form submission (triggered when an answer is submitted)
4. List item selection (on tap of a specific list entry)
5. Time based (repeated every ‘#’ of seconds, triggered at a certain time, triggered after a certain delay)
6. User status update (eg a user logs in or out)

It is also possible to ensure the triggers above are fired every time or only the first time an input event occurs.

Actions are the output of a workflow. These are specified in code via the developer options so can be tailored to your needs. Common actions that Fliplet allows include:

1. Go to a new screen or open an overlay
2. Save, retrieve or edit data from the device, Fliplet’s datasources or a third party database
3. Change a screen’s content (eg, display, hide, update)
4. Send notifications, emails or chat messages
5. Run a custom function defined in the developer options

Conditions check on a user or app’s status before performing an action eg: if a user has admin rights then perform a certain action. Conditions are typically implemented with Javascript in the developer options. Common examples include:

1. Check data - True / false, empty / not nil, value equals, <, >, String contains, date equals etc.
2. Check status - User type, logged in?, device type, current time etc.

It’s possible to store, retrieve and update data at several levels with Fliplet apps. Data can be stored locally on a device, on Fliplet’s cloud data sources or on third party databases via an API or data service integration. A more detailed description of data storage options is provided here.

Fliplet also provides access to ‘environmental’ variables that are automatically updated by Fliplet’s infrastructure. These environmental variables include:

1. User ID and user type
2. App ID and screen ID
3. User log-in status
4. Local date and time
5. Device type and screen size

Data manipulation and custom functions can be created within Fliplet’s developer options. The developer options allow users to leverage the power of custom Javascript, HTML and CSS (as well as install code libraries such as jQuery or Bootstrap). Custom code can be executed at an individual screen level or globally across an app.

If you have a specific question you can chat with Fliplet's customer service team using the blue help button in Fliplet studio. If you're not a Fliplet studio user already you can create a free account here. For a list of Fliplet APIs (code used to interact with Fliplet apps) please see our developer site. For all other enquiries please contact us at hello@fliplet.com.