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

Get whole attribute struct when map subflow activity's output #317

Open
lixingwang opened this issue Jan 3, 2019 · 0 comments
Open

Get whole attribute struct when map subflow activity's output #317

lixingwang opened this issue Jan 3, 2019 · 0 comments
Assignees

Comments

@lixingwang
Copy link
Contributor

I'm submitting a ... (check one with "x")

[*] bug report => search github for a similar issue or PR before submitting
[] enhancement request
[] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):
Map subflow activity's output to a log message and it get 2019-01-03 15:27:42.856 INFO [activity-flogo-log] - {"name":"output2","type":"string","value":"subflow output"} it should be only value, eg subflow output
Expected behavior:
Just get subflow output's value rather than whole attribute struct.
Minimal steps to reproduce the problem (not required if feature enhancement):

What is the motivation / use case for changing the behavior?

Please tell us about your environment (Operating system, docker version, browser & verison if webui, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X

Additional information you deem important (e.g. issue happens only occasionally):

@lixingwang lixingwang self-assigned this Jan 3, 2019
@lixingwang lixingwang changed the title get attribute struct when map subflow activity's output Get whole attribute struct when map subflow activity's output Jan 3, 2019
lixingwang added a commit that referenced this issue Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant