Applications

Summary

• Type of dynamic fields

• Local properties

• Relation properties

  • Services

Type of dynamic fields

There are two main types of dynamic fields for the application catalogs:

Local properties

Local properties are those properties that directly belong to an application; these fields are:

• id

• name

• createdBy

• metaTags

You can use these dynamic fields like

Code

[
  {
    "type": "text",
    "title": "Application id",
    "payloadName": "app_id",
    "defaultValue": "{{application.id}}"
  },
  {
    "type": "text",
    "title": "Application name",
    "payloadName": "app_name",
    "defaultValue": "{{application.name}}"
  },
  {
    "type": "text",
    "title": "Application created by",
    "payloadName": "app_createdBy",
    "defaultValue": "{{application.createdBy}}"
  },
  {
    "type": "dropdown",
    "title": "Application meta tags",
    "payloadName": "app_metatag",
    "dataset": {
      "data": "{{application.metaTags()}}",
      "label": "name",
      "value": "value"
    }
  }
]

Rendered

Meta tags are the only local field that can be used in dropdown dataset fields, but if you want to use one specific metatag value as a default value in text fields.

So, if you have some meta tags in your application as below, It will be rendered as a drop-down with those meta tags.

You have to use the text version to use meta tags in webhook headers and webhook payload.

Meta Tags

Code

[
...
    {
        "type": "text",
        "title": "Application metatag",
        "payloadName": "app_metaTag",
        "defaultValue": "{{application.metaTags('Environment').value}}"
    }
...
]

Rendered

Note that it's not a dropdown anymore.

Relation properties

Relation properties load up other catalogs related to the chosen one, and you can also access those fields.

Services

You can load up services connected to an application using this syntax for getting a list of application services, to be shown as a drop-down:

Code

[
// ... other user inputs
    {
        "type": "dropdown",
        "payloadName": "app_service",
        "title": "Application service",
        "dataset": {
            "data": "{{application.services()}}",
            "label": "name",
            "value": "id"
        }
    }
// ... other user inputs
]

This will only bring up to 50 first services for the application.

Rendered

It is also possible to use one specific service for a text field and use a supported application.services fields:

• id

• lifecycle

• name

Code

Example user inputs

[
  {
    "type": "text",
    "title": "Application service id",
    "payloadName": "app_service_id",
    "defaultValue": "{{application.services('6a9dc87a-82e5-46a1-a01a-37545e477c67').id}}"
  },
  {
    "type": "text",
    "title": "Application service name",
    "payloadName": "app_service_name",
    "defaultValue": "{{application.services('6a9dc87a-82e5-46a1-a01a-37545e477c67').name}}"
  },
  {
    "type": "text",
    "title": "Application service lifecycle",
    "payloadName": "app_service_lifecycle",
    "defaultValue": "{{application.services('6a9dc87a-82e5-46a1-a01a-37545e477c67').lifecycle}}"
  }
]

If the value in your service is null, it will be replaced with an empty string.

Rendered