# Concept & Goals

{% hint style="danger" %}
:white\_check\_mark: **IMPORTANT - PLEASE READ IT** :white\_check\_mark:

**While the app is available at the** [**Atlassian Marketplace**](https://marketplace.atlassian.com/apps/1234290/pipeline-forms-schedule-with-parameters-advanced-fields?hosting=cloud\&tab=overview)**, it can be installed only from this** [**install link**](https://developer.atlassian.com/console/install/969025b6-9d62-4f5c-ab1b-c141fd1c41fe?signature=069a192f2c144997e0f53c1c04841b3f9160cd83823404b64984f8b2f528bcc2a8d7511b42c10b8765b3938ab35e1dfe567e8ba356ffefb8c2109ad2d9d4adb4\&product=bitbucket)**.** Since Forge on Bitbucket is so new (it just left EAP and became GA), it is impossible to install Bitbucket Forge apps directly from the Atlassian marketplace. It is **Safe to install** from here and will be available on Marketplace when Atlassian makes it possible. See more details at [installation](https://docs.meta-inf.hu/pipeline-forms/user-guides/administration-guide/installation "mention").

By installing the app, you automatically accept our [Terms of Use](https://www.meta-inf.hu/legal-documents/terms-of-use).
{% endhint %}

## Goals & Purpose

Building apps within the Atlassian ecosystem usually involves tools like Jira, Confluence and Bitbucket.

In **Confluence** you can write documentation, in **Jira** you can manage issues and in **Bitbucket** you can manage your software's source code.

Bitbucket is great in terms of **integration** with other tools, but lacks some **features** as a CI tool.

> **Pipeline Forms (PFO) is created to improve the experience using Pipelines in Bitbucket.**

## Problems we solve

* Lack of **flexible customization of** **pipelines**, especially in terms of custom input values
* Huge `bitbucket-pipelines.yml`since pipelines need to be **copy-pasted** for different variations
* Lack of dynamic field values (they have to be static or freetext)
* Inability to **overwrite default values** while scheduling
* Inability to **edit** and **view scheduled** pipelines

## What we add

* **Forms** - extend pipelines attributes with many supported field types and several attributes
  * select, remote, text, textarea, number, checkbox, checbox group, radio, date fields are made available
  * mandatory, secure, read-only, hidden, remote, regex fields can be created
  * remote fields can be pre-populeted through public API
  * with forms added, `bitbucket-pipelines.yml`file complexity can be reduced
* **Scheduled** pipeline executions - run form-extended pipelines when needed
  * manage schedules, view, edit, inactivate, and delete them
* **Audit** history - track changes and view execution history
* **Pretty UI** where users can self-serve with well-configured pipelines

## Getting started

{% content-ref url="features" %}
[features](https://docs.meta-inf.hu/pipeline-forms/general-product-information/features)
{% endcontent-ref %}

{% content-ref url="how-pfo-works-securely" %}
[how-pfo-works-securely](https://docs.meta-inf.hu/pipeline-forms/general-product-information/how-pfo-works-securely)
{% endcontent-ref %}

{% content-ref url="../user-guides/administration-guide/installation" %}
[installation](https://docs.meta-inf.hu/pipeline-forms/user-guides/administration-guide/installation)
{% endcontent-ref %}

{% content-ref url="../user-guides/user-guide" %}
[user-guide](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide)
{% endcontent-ref %}

## Deep dive

{% content-ref url="../user-guides/user-guide/create-forms" %}
[create-forms](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/create-forms)
{% endcontent-ref %}

{% content-ref url="../user-guides/user-guide/run-pipelines/schedule-a-form" %}
[schedule-a-form](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/run-pipelines/schedule-a-form)
{% endcontent-ref %}

{% content-ref url="../additional-information/examples/showcase-an-example-with-every-feature-used-in-the-form" %}
[showcase-an-example-with-every-feature-used-in-the-form](https://docs.meta-inf.hu/pipeline-forms/additional-information/examples/showcase-an-example-with-every-feature-used-in-the-form)
{% endcontent-ref %}

{% content-ref url="../user-guides/user-guide/audit-logs" %}
[audit-logs](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/audit-logs)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meta-inf.hu/pipeline-forms/general-product-information/concept-and-goals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.