At ManyWho, the word we use for an ‘app’ is ‘flow’. We build a flow by logging into the ManyWho Drawing Tool, connecting an Identity Service for authentication, dragging and dropping Elements into the ManyWho Canvas, configuring the Elements, and connecting them with Outcomes. The canvas gets automatically converted into a production-ready, scalable application.
Here is how we create a new flow:
- Click LOG IN to login to the ManyWho Drawing Tool. If you do not have a ManyWho login, please click here to get one.
- Click New Flow.
- Select the service (Salesforce, Box, etc.) you want to use, to authenticate your end-users. If you do not have a service integration, or want your app to be available to the public, select the ManyWho Identity Service.
- Click Continue. This opens the Flow: New Flow screen.
- Enter a name for the flow in the Name field.
- Select the Access you want for end-users. There are three options:
- Anyone can run this flow (The app is public.)
- Any user that can login with the selected Identity Service can run this flow (The app needs authentication. For example, users with Salesforce credentials only, will be able to run the app.)
- Create restrictions for specific users and groups of users (The app can restrict access to certain users. For example, only the user that logs in with email@example.com can access the Jarvis app.)
- Select a Social feed for collaboration. There are two options:
- None (There is no social feed.)
- Display a social feed (You can choose to display a social feed. For example, Chatter with Salesforce.)
- Click Start Building. (Clicking on + Advanced lets us configure advanced flow options like Groups, Users, Navigation, and State. These are optional configurations.)
This is what a sample flow configuration screen may look like:
We can drag and drop ManyWho Elements (like Step, Page, Decision, etc.) into the canvas, configure the elements, and connect them with outcomes. The elements represent screens that are shown to the user (from a simple screen to a page with complex forms), or actions (like Database Save). The outcomes show how the flow progresses. We can also use swimlanes to set permission-based access for different categories of users (Account Manager, VP – Sales, CFO, etc.) for different elements of the flow.
The canvas gets automatically saved every time we change something.
ManyWho Pro Tip
Check out the ManyWho glossary for a definition of terms and key concepts that appear in the ManyWho website, Drawing Tool, technical documentation, blogs, and marketing communications.
If you want to take a closer look, click on the images to enlarge them. Have a question? Click the Help button on the bottom right-hand corner of this page to ask.