examples

Examples

Running

Generally, examples can be executed using Concord Command-Line Interface. Examples that use Concord Forms require a running concord-server. Some examples may require external dependencies such as Ansible, Jira and others to be installed:

$ cd ansible
$ concord run
Starting...
16:20:00.000 [main] Using a playbook: playbook/hello.yml
16:20:00.020 [main] ANSIBLE: Can't find ansible-playbook binary in $PATH. Install a local copy or use 'dockerImage' or 'virtualenv' options.

Basic

• ansible - running an Ansible playbook from a workflow process;
• datetime - how to work with dates and date/time formats;
• forms - using basic forms;
• git - how to clone a Git repository;
• hello_initiator - a simple example that shows how to use automatically provided variables such as ${initiator};
• hello_world2 - how to send external parameters;
• hello_world - a simple example demonstrating how to pass a variable to a process;
• http - a simple example demonstrating how to call RESTful endpoints;
• in_variables - how to use IN-variables when calling a flow;
• jira - how to create an issue in Jira;
• ldap - how to query an AD/LDAP server;
• loglevel - how to use different logging levels;
• long_running - a simple example of a long-running process using sleep task;
• loops - how to iterate a collection;
• multiple_flows - multiple flows in a single YAML file;
• out - how to use process OUT variables;
• out_groovy - using OUT variables coming from Groovy scripts;
• parsing_yaml_json - how to work with YAML and JSON files;
• project_file - basic usage of a concord.yml project file;
• slack - sending a message to a Slack channel;
• slackChannel - how to manage Slack channels;
• smtp - using SMTP task.

Intermediate

• ansible_docker - using a custom Ansible Docker image to run a playbook;
• ansible_dynamic_inventory - using dynamic inventory scripts in Ansible;
• ansible_form - using forms and Ansible in a single flow;
• ansible_form_as_inventory - using forms to specify an Ansible inventory;
• ansible_kerberos - how to use Kerberos with Ansible;
• ansible_limit - how to use Ansible's limit/retry files;
• ansible_project - an example of creating and running an Ansible project;
• ansible_remote - running an Ansible playbook on a remote host;
• ansible_retry - how to automatically retry Ansible deployment for failed hosts;
• ansible_stats - shows how to get Ansible deployment stats back from a playbook run;
• ansible_template - running an Ansible playbook using the Ansible template;
• ansible_vault - using Ansible Vault to store encrypted data;
• ansible_windows - how to use Ansible with Windows hosts;
• custom_form - using forms with custom HTML/CSS and a templating library;
• custom_form_basic - a basic example of a custom form;
• docker - running a docker image with custom environment and arguments;
• docker_simple - running a simple command inside of a docker container;
• error_handling - how to handle failures;
• external_script - calling an external JavaScript file;
• form_and_long_process - how to deal with long "background" processes;
• forms_override - how to override default values in forms;
• groovy - running a Groovy script from a flow;
• groovy_grape - how to use Groovy's @Grab in scripts;
• groovy_rest - calling a REST endpoint from a flow using Groovy;
• imports - how to use external Git, HTTP, and Maven resources as project files;
• juel_java_streams - using expressions, Groovy and Java Streams;
• noderoster - how to use the Node Roster task;
• process_card_htmx - how to use "process cards" and HTMX to implement custom forms to start processes;
• process_card_jquery - how to use "process cards" and jQuery to implement custom forms to start processes;
• profiles - how to use profiles;
• python_script - running a Python script from a flow;
• ruby - running a Ruby snippet from a flow;
• script_url - running an external script file;
• smtp_html - how to send an HTML email.

Advanced

• ansible_out_vars - saving Ansible variables as Concord flow variables;
• ansible_roles - how to use external Ansible roles;
• approval - using forms and runAs to implement an approval process;
• context_injection - how to use automatic variable injection with custom tasks written in Groovy;
• custom_task - how to create a custom Concord task (plugin);
• dynamic_form_values - using custom forms with values added/removed dynamically;
• dynamic_tasks - using custom tasks provided with the process;
• form_l10n - how to use custom validation error messages in forms;
• forms_multi_group - how to restrict a form to a set of LDAP groups;
• forms_wizard - multi-step forms;
• inventory - using Concord Inventory to retrieve Ansible's inventory data;
• inventory_lookup - using the inventory lookup plugin for Ansible;
• process_meta - exporting process variables as process metadata;
• secret_files - how to store and export secrets as files;
• secrets - working with Concord's Secrets storage;
• secret_lookup - using the secret lookup plugin for Ansible;

Runtime V2

• runtime-v2 - examples using the runtime-v2 DSL and task SDK;

Expert

• dynamic_form_fields - how to define form fields at runtime;
• dynamic_forms - how to create a form dynamically (at runtime);
• fork - starting a subprocess;
• fork_join - starting multiple subprocesses and waiting for completion;
• generic_triggers - how to use custom trigger events;
• logback_config - overriding logging configuration;
• process_from_a_process2 - using output variables, starting a new subprocess from a project;
• process_from_a_process3 - starting a new subprocess using a directory as the payload;
• process_from_a_process - starting a new subprocess from a flow using a payload archive;
• mocking - how to use Groovy to replace "real" tasks with "mock" versions for testing;