Skip to main content
Solved

Procesflow works in Windows via IAM, but hangs in Universal (clicking submit has no action)

  • December 24, 2021
  • 7 replies
  • 104 views
Freddy
Forum|alt.badge.img+16
  • Freddy
  • Thinkwise Local Partner Brasil
  • 533 replies

I created a process flow which works via de IAM with the windows client, but unfortunately not via the Universal (the platform of our demo), what could be wrong?

  • Task 1 is an upload of a payment file
  • The step that follows is a HTTP connector to check if a tenant exists. (in this case not)
  • So a task is shown to define a code that is needed to be registered.
  • In windows the flow continues where a tenant is added via IAM API, but in Universal it stops here. You can click many times on submit (executar) but nothing happens. There is also nothing in the logfiles. 

 

Best answer by Erik Brink

To summarize a conclusion: we've investigated the cause. Improved errorhanding in the GUI on patching a parameter of a task or report for upcoming release 2021.3.15.

On location the processflow is updated to be able to go on with the demo, on the short term.

@Freddy, please report a ticket in TCP when the problem still occurs.

View original
LEF — Lift. Empower. Fulfill. [lef.digital]
    Did this topic help you find an answer to your question?
    This topic has been closed for replies.

    7 replies

    E
    Moderator
    Forum|alt.badge.img+17
    • Erwin Ekkel
    • Moderator
    • 768 replies
    • December 27, 2021

    Can you post a screenshot of the process flow you are using?

    Freddy
    Forum|alt.badge.img+16
    • Freddy
    • Author
    • Thinkwise Local Partner Brasil
    • 533 replies
    • December 27, 2021

    Hi @Erwin Ekkel , 

    Find attached a screenshot of the flow and an accompanying .HAR file. 

     

     

    1 Attachments
    LEF — Lift. Empower. Fulfill. [lef.digital]
    Erik Brink
    Moderator
    Forum|alt.badge.img+5
    • Erik Brink
    • Moderator
    • 497 replies
    • December 27, 2021

    Hi Freddy,

    The HAR-file confirms your description about this issue. The weird thing is, the GUI doesn't even try to send the submit/commit to Indicium. The HAR-file doesn't mention why.

    Did you install the "Redux” plugin for the Chrome DevTools already? Hopefully this can give us more details about this behaviour. 

    Else I this it would be better to initiate a direct call to exam the situation.

    Regrads, Erik

    Freddy
    Forum|alt.badge.img+16
    • Freddy
    • Author
    • Thinkwise Local Partner Brasil
    • 533 replies
    • December 27, 2021

    @Erik Brink I installed it and have run the login and process until it stopped. Does the download then help (json)? I attached it here. Otherwise we can have a call. 

    1 Attachments
    LEF — Lift. Empower. Fulfill. [lef.digital]
    Erik Brink
    Moderator
    Forum|alt.badge.img+5
    • Erik Brink
    • Moderator
    • 497 replies
    • December 27, 2021

    The Redux tooling puts a top on the amount of shown statement. You can configure via the Settings button in the right bottom of the Redux tab. We now only see “execute” actions coming by.

    It seems like the value of the changed field of the task is not being processed yet, blocking the task execution. I miss this part of the Redux records to check it.

    To speed up things, you may contact me on email address: ebrink@thinkwisesoftware.com

     

    Freddy
    Forum|alt.badge.img+16
    • Freddy
    • Author
    • Thinkwise Local Partner Brasil
    • 533 replies
    • December 27, 2021

    @Erik Brink I have just sent you an email. 

    LEF — Lift. Empower. Fulfill. [lef.digital]
    Erik Brink
    Moderator
    Forum|alt.badge.img+5
    • Erik Brink
    • Moderator
    • 497 replies
    • Answer
    • December 29, 2021

    To summarize a conclusion: we've investigated the cause. Improved errorhanding in the GUI on patching a parameter of a task or report for upcoming release 2021.3.15.

    On location the processflow is updated to be able to go on with the demo, on the short term.

    @Freddy, please report a ticket in TCP when the problem still occurs.

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings