Flow Development Guidelines
  • Introduction
  • Getting Started
    • Beginner Basics
    • Flow Studio Structure
    • Naming Convention
  • Developing a Flow
    • Workflow Types
    • Flow Elements
    • Programming
  • Promoting a Flow
    • Environments & Subscriptions
  • Advance Flow Features
    • Swimlanes & Offline Flows
    • Monitoring
    • REST API
      • Authentication
      • Troubleshooting REST
    • Importing data from flat files
      • Scheduled Flows
Powered by GitBook
On this page
  • Language
  • Designer

Was this helpful?

  1. Getting Started

Beginner Basics

PreviousIntroductionNextFlow Studio Structure

Last updated 4 years ago

Was this helpful?

Language

Always use English as the Design Language.

If possible, add the English translation together with the local in your workflows.

Designer

Use a named user as the designer, i.e. logged in user. Avoid anonymous user names. Anonymous users tend to reduce the quality in the development.