We have noticed that the links in the header part of screens have stopped working, e.g. on a Customer Order we are unable to ‘zoom’ to the customer record without RMB and opening in a new tab.This affects 23.1 and 22.2.6 and later.Has anyone else noticed and has anyone found a fix?
Has anyone used Oracle DB as a Service to host IFSCloud? Is there anything specific that we need to look out for?
While trying to develop a BPA Workflow using collections, I had repeated issues with the Temp tablespace filling up when debugging. It seems that whenever an element of the workflow is called, the message data is written to the temp table space. In my case, the data was around 180k, being written for about 15 actions 150 times. This doesn’t take long to add up. Has anyone found a way to get round this, apart from finding and killing the offending session? SELECT S.sid || ',' || S.serial# sid_serial, S.username, S.osuser, P.spid, S.module, P.program, SUM (T.blocks) * TBS.block_size / 1024 / 1024 mb_used, T.tablespace, COUNT(*) statements FROM v$sort_usage T, v$session S, dba_tablespaces TBS, v$process P WHERE T.session_addr = S.saddr AND S.paddr = P.addr AND T.tablespace = TBS.tablespace_name GROUP BY S.sid, S.serial#, S.username, S.osuser, P.spid, S.module, P.program, TBS.block_size, T.tablespace ORDER BY sid_serial; ALTER SYSTEM KILL SE
We have recently seen an issue where the OWASP rules were uplifted to 3.2 and data is no longer returned on any screens in the application.How have others got around this issue?Feedback from the network engineer (a 3rd party) was as follows;“It was necessary to make a change to the Azure Application Gateway Firewall as the Firewall was running version 2.2.9 of OWASP (Open Web Application Security Project) no longer supported by Microsoft. OWASP upgraded to version 3.2 to implement the required fix and initial testing connecting to the IFS login page showed no errors, with no issues immediately reported. The latest version of OWASP 3.2 includes new protective features over the older version.The coding of IFS application and the way it operates resulted in selected OWASP filters detecting the IFS application operations as an attack resulting in block actions, which caused sections of the IFS application to fail in displaying data to the user. As a result of the blocks, it was necessary
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.