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

Engine does not start when assigning an iterator to an activity #207

Closed
mellistibco opened this issue Mar 30, 2018 · 1 comment
Closed

Comments

@mellistibco
Copy link
Collaborator

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

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

Current behavior (how does the issue manifest):
When starting the engine with an iterator attached to an activity the following error is thrown:

2018-03-28 15:18:09.971 ERROR  [main-engine] - Failed to start engine due to error: error unmarshalling flow: Unsupported task type: iterator

Expected behavior:
The engine starts and the iterator works as expected

Minimal steps to reproduce the problem (not required if feature enhancement):
Add an iterator to an object from webui, export and build the app.

          {
            "id": "counter_2",
            "type": "iterator",
            "name": "Increment Counter",
            "description": "Simple Global Counter Activity",
            "settings": {
              "iterate": "5"
            },
            "activity": {
              "ref": "github.com/TIBCOSoftware/flogo-contrib/activity/counter",
              "input": {
                "counterName": "",
                "increment": false,
                "reset": false
              },
              "mappings": {
                "input": [
                  {
                    "type": "literal",
                    "value": true,
                    "mapTo": "increment"
                  },
                  {
                    "type": "literal",
                    "value": false,
                    "mapTo": "reset"
                  },
                  {
                    "type": "assign",
                    "value": "increment",
                    "mapTo": "counterName"
                  }
                ]
              }
            }
          }

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

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

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

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

@mellistibco
Copy link
Collaborator Author

Resolved in 0.5.3

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

No branches or pull requests

1 participant