Hi IFS Community!IFS Cloud Aurena Client uses dynamic LOVs and some of them has session user as a filter. Meaning that when the user opens a LOV field, the search result is dynamic and will depend on the user which is logged in. Where are the LOV definitions visible in a readable format so that the user would know why a LOV is empty or the LOV doesn’t show the wanted value? One example from IFS Maintenance work task (23R2), task allocation page. The allocated to LOV field execute the following database query. SELECT A.* FROM (SELECT 'MaintResourcesLov2' luname, 'COMPANY='||company||'^'||'RESOURCE_ID='||resource_id||'^'||'RESOURCE_PARENT_ID='||resource_parent_id||'^'||'SITE='||site||'^' keyref, resource_id resource_id, description description, resource_parent_id resource_parent_id, resource_parent_desc resource_parent_desc, resource_type resource_type, company company, site site, org_code org_code, resource_seq resource_seq, resource_parent_seq resource_parent_seq, vendor_no vendor_no
Hi,We have faced system slowness in some IFS Cloud pages after upgrade from IFS 9. We performed the upgrade to IFS Cloud 21R2 SU 11.For example active Work Orders page returns 480 rows of data very slowly for the users (projection ActiveWorkOrdersHandling). The browser will prompt the users of unresponsive page but eventually the data is refreshed to the user. During this query the system runs the following GET request:https://HOST_NAME/main/ifsapplications/projection/v1/ActiveWorkOrdersHandling.svc/ActiveSeparateSet The underlying SQL performs quite well with execution time of some seconds. However when the client performs the respective GET request the execution time is significantly slower. What administrative tasks exists that might improve the Aurena client response times? Should indexes be refreshed? Or should some caches be refreshed accordingly?
Hi,IFS EE client had a debugger console with capability to trace database level. Meaning that the PL/SQL trace showed what methods and packages were used in background and it told developers easily what DB procedure or function caused a error. It could also be utilized when developing data migrations and one needed to see what procedure is needed for migrating data through standard APIs. How is this done in IFS Cloud? IFS Cloud client has a debug console but it shows only rest API level (call/response) and doesn’t show what PL/SQL methods are actually executed when storing data or when some error is raised in the client.
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.
