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

Introduce global dictionary message direction #310

christophd opened this Issue Nov 21, 2017 · 0 comments


None yet
1 participant

christophd commented Nov 21, 2017

Global data dictionaries apply to all messages that get exchanged regardles of message direction inbound or outbound. In almost no cases a dictionary is able to be applied to both inbound and outbound messages.

Outbound messages may need dynamic field value generation while inbound messages may want to use variables, ignore element expressions and validation matchers.

Introduce message direction INBOUND/OUTBOUND for dictionaries so global scoped instances can decide which message to apply to.

@christophd christophd added this to the v2.7.3 milestone Nov 21, 2017

@christophd christophd removed the READY label Nov 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment