Skip to main content
Question

Simple process flow triggers `bad_request` in Universal GUI

S
Rookie
Forum|alt.badge.img

Universal GUI - Process Flow Triggers `bad_request` HTTP 400 error

 

Dear community,

When performing a process flow that has existed since 2017, but now executing it in the Universal GUI. It results in a `bad_request` error response. HTTP code 400.

Within our team we have seen a set of occurrences where the process flow works as expected in WinGUI, however not in UGUI. This process flow opens a detail view, edits a row and prefills a set of fields. After the user presses ‘save’ on the form edit. A row is added to the detail of the element.

See screenshot for reference of the process flow.

 

The problem is that the underlying problem is not traceable, since Indicium does not report an error. Just the universal GUI responds with a bad_request HTTP 400 error on the `continue` request. 

/continue Status: 400 Source: Network Address: 212.121.123.213:443 Initiator: _app-830f5064ccd20668.js:204:2481511

 

Couple of important remarks:

  • The error does not occur when running the application directly from within the Software Factory. When connecting Universal GUI through Indicium to this IAM database with url/iam/sf, the error does not occur.
  • No error log in Indicium runtime.
  • No clear error message in browser console/network.
  • Just a response from Indicium’s API stating bad_request as a return statement, without clarification in the request response body, nor in the Indicium log.

 

Did this topic help you find an answer to your question?

3 replies

E
Moderator
Forum|alt.badge.img+17
  • Erwin Ekkel
  • Moderator
  • 780 replies
  • July 24, 2025

I notice the detail name is quite long. Could be you run into an issue where the url becomes too long? We have seen this problem before at other customers. Can you check the length of the url and see if it works if you remove a detail or a filter to make the url shorter? 

S
1 person likes this
  • S
    Stijn Schuurman
S
Rookie
Forum|alt.badge.img
Erwin Ekkel wrote:

I notice the detail name is quite long. Could be you run into an issue where the url becomes too long? We have seen this problem before at other customers. Can you check the length of the url and see if it works if you remove a detail or a filter to make the url shorter? 

​@Erwin Ekkel 

Thank you very much for the swift response.
The domain that it worked on when connected to the SF was a total of 47 characters before the path to the requests (https://xx.xxxxxx.com/iam_ont_xx_xxxxxxx/sf/)
The domain that had the error has a total of 39 characters before the path to the requests (https://xxxxxxx.xx.nl/ind_iam_prod/iam/)

So the total URL seems to not be so bothered by it. The internal path, after the domain was the same length for both setups. The one failing, and the one succeeding.

E
Moderator
Forum|alt.badge.img+17
  • Erwin Ekkel
  • Moderator
  • 780 replies
  • July 24, 2025

Some things to check: 

Are you using the latest indicium/universal and do these versions match on both the development and production environments?
Did it ever work for you in universal, or only in windows gui? If it has worked in universal before, at what point did it stop working? 
Did you try a user that has the all rights checkbox? 

If all these do not point you towards a solution then I would like to ask you to report a ticket and a model export in the ticket. That way I can check if we can reproduce this problem using your model. 

Reply


Terms & ConditionsCookie settingsAccessibility statement

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