Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow definition of first message field by parameter value #764

Closed
treiher opened this issue Sep 6, 2021 · 1 comment
Closed

Allow definition of first message field by parameter value #764

treiher opened this issue Sep 6, 2021 · 1 comment
Labels
architectural decision Discussion of design decision model Related to model package (e.g., model verification)

Comments

@treiher
Copy link
Collaborator

treiher commented Sep 6, 2021

Context and Problem Statement

With the introduction of parameterized messages (#609) there is no strict need for a definite first field anymore, as the first field can depend on the value of a message parameter. Currently, the model is checked to have exactly one link to the first message field.

Considered Options

O1 Allow definition of first message field by parameter value

+ More flexible

O2 Keep current restriction

+ No changes needed

Decision Outcome

O1

@treiher treiher added model Related to model package (e.g., model verification) architectural decision Discussion of design decision labels Sep 6, 2021
@treiher treiher added this to To do in RecordFlux Future via automation Sep 6, 2021
@treiher
Copy link
Collaborator Author

treiher commented Mar 26, 2024

We decided to support multiple initial links to allow the first message field to be defined by parameter values (O1).

@treiher treiher closed this as completed Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architectural decision Discussion of design decision model Related to model package (e.g., model verification)
Projects
No open projects
Development

No branches or pull requests

1 participant