Skip to main content

In case this helps somebody, version 131 of Chromium based browsers such as Edge and Chrome have caused issues with editing BPA workflow elements on such the IFS API element as below. Note there is no API Name or EntitySet Name text box. This issues occurs on 23R2 only and I have not checked later versions.

 

 

This can be resolved by setting the SelectParserRelaxationEnabled flag to false or 0 depending on the OS. The details are here:

Chrome Enterprise policy list and management | Documentation

SelectParserRelaxationEnabled - Instinctive library of Chrome settings

It looks like there is a bug in v131 as according to the document the workflow functionality should still work if the policy is not set or is set as true/1/enabled. False/0 only seems to fix it. If this is corrected in the future, the policy will also need to be changed.

Thank you very much for this.  This was quite vexing for us last week.

Chromium has released a fix now and IFS RnD has verified it is working as before in Chrome. Edge is yet to be verified. However, RnD will provide a fix in 2024 December service updates changing what caused this issue in drop downs, so that similar problems will not occur in future with Chromium updates.

Thank’s for the update.

We are using IFS 23R1 and had this issue on edge starting last friday  version 131.0.2903.63

(OK on Google Chrome)

Reply


Terms & ConditionsCookie settings