Welcome to TIBCO Flogo^® apps User's guide.

This section contains the following topics:

• Overview
  TIBCO Cloud™ Integration - Flogo^® is a wizard driven web-based tool that allows you to create integration apps without having to leave your browser. It is powered by Project Flogo™, a lightweight integration engine. You use TIBCO Flogo to interconnect APIs, systems, and data.
• User Roles in TIBCO Cloud™ Integration
  Some actions in TIBCO Flogo may not be visible or usable depending on your user role and app ownership.
• Tutorial on Building a Simple REST Service
  The following tutorial walks you through building a simple REST service in Flogo.
• TIBCO Flogo^® app
  Flogo offers a wizard driven approach to app development. You can create apps in Flogo using only a browser.
• Building APIs
  Flogo lets you take an API-first development approach to implement APIs from a GraphQL schema or a Swagger 2.0 specification. Once you upload a GraphQL schema or Swagger file, Flogo validates the file and if the validation passes, it automatically creates the Flogo flows and trigger for you.
• Using Connectors
  The Flogo offers the ability to use connectors that have enterprise support and also connectors that are custom developed extensions.
• Flows
  Each flow represents specific business logic in an app. An app can have one or more flows. A flow contains one or more activities. The flow is activated by a trigger.
• Flow Tester
  After you have finished designing the flow, use the Flow tester to test the flow.
• General Category Triggers and Activities
  The General category is available by default in all flows. It consists of activities and triggers that may be commonly used by any flow in the app. A trigger activates the flow in which it appears. An activity is used to perform a task.
• Mapper
  Use the mapper to enter input values manually or map the input schema elements to output data of the same data type from preceding activities, trigger, or the flow itself. An activity has access to the output data from the trigger to which the flow is attached in addition to the output from any of its preceding activities in the same flow provided that the trigger or activity has an output. This data is displayed in a tree structure under Upstream Output in the Mapper. The input schema for the activity is displayed in the pane to the left of the Upstream Output pane. You can map data coming from the upstream output to the input fields of the activity. Activities also have access to the input fields of a flow to which the activity belongs. You enter the flow input schema in the Input Settings tab of the Flow Inputs and Outputs accordian tab. Within a flow, use the mapper to pass data between the activities, and between the trigger and the activities or the trigger and the flow.
• Application Properties
  Application properties provide a way to override property values after an app has been pushed to the cloud. You can configure some supported fields with application properties when configuring triggers and activities. Connection-related application properties cannot be used for configuration anywhere within an app. Their only purpose is to allow you to change a connection value if need be during runtime. Configuration fields in your flow that require their values to be changed when the app goes from a testing stage to production are best configured using application properties instead of hard coding their values. Application properties for triggers and activities reside within the app. Application properties for connections are not modifiable from the App Properties dialog in the app.
• Serverless Deployments
  
• Using Extensions
  Flogo gives you the ability to make use of your own extensions.
• Exporting and Importing an App
  You can export and import apps and use them as templates to quick start development or simply put them in a version control system such as GitHub.