Skip to content

Introduce the metadata property to tasks and other concepts #945

@ricardozanini

Description

@ricardozanini

What would you like to be added:
As discussed in #928, there are a few use cases where metadata information is useful such as when designing a graphical interface for representing the DSL.

This field must not change the behavior of the workflow in runtime. For example: adding additional properties to a function call that only the given implementation would understand. The metadata information must describe static information regarding the workflow definition, not changing in any matter its behavior.

Why is this needed:
Several times users and community members faced a situation where some dynamic data could be added to the DSL to facilitate some parts of an implementation and there was no room for it in the current DSL version.

Apart from the obvious include to the task object, other parts of the DSL must be assessed.

Metadata

Metadata

Assignees

Labels

area: specChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version change

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy