Hi, This is a known error on Apps10 UPD10. The bug is fixed on Apps10 UPD11. Please check solution 290150.
Hi, the bug is with API Documentation only. Custom LU generated APIs work all fine.
Hi, Your custom fields should be visible in the Aurena Page Designer. (As long as the IEE form and the Aurena page are both based on the same LU.) Do you see the custom field in the Aurena Page Designer ?
Nethmini’ suggestion is the answer. Please check if you have allowed it in the Approved Details Views.
@Afifa Is this something you can answer ?
@Carus_RGladhill Hi, The API Documentation is available on IFS Apps 10 and IFS Cloud via API Explorer page found in Solution Manager section in the navigator. Unfortunately, this is limited to IFS Aurena client as of now. We are working on exposing this info as a public service in the future.Until then, you can download the necessary openAPI specification for each API (via API explorer) you want to do the integration and then send it to the 3rd party. Then can use Swagger or any openAPI reader to visualize the content.
Would be good if you shared the solution ? :)I guess you had not bound to the correct context or enable data source ?
Not my area of expertise here, but regarding new features, yes they are getting added in each Feature Update. I am quite sure the relevant release material should be updated, including this change in the 22R1 content. Glad that the question was answered here.
Not at the moment, but is something R&D will be looking to support in the future. You can consume a QD projection via Lobby and Custom projection (i.e. Custom Page) at the moment (22R1).
Hi @bapehu Since the issue is actually related to which API to use rather than how to use, I suggest if this is posted in the relevant functional area for you to get a better answer. Thanks.
@TheoB Yes this is something in the plans. We will take note of this question and we will make sure to communicate the migration path well in advance before we remove this event action in a future Feature Update. There is no specific target release for this as of now.
@TheoB In general, the use of PL/SQL will be eventually deprecated for more configurable data extraction using Query Designer and Workflows etc. While you may still continue to use PLSQL event actions, in due future the same purpose would be more effectively fulfilled with other tools. I can’t confirm that you will have to manually migrate/rebuild what you already have, but I wanted to express the general direction we are heading.
I think it’s best if this question is asked in the DocMan Knowledge area since this is specific flows in that functional area that needs clarification.
Thorough response from @InfFilipV. Thanks. The recommendation as written there is to use the Browser console and locate the applicable call.
@GaSoGB This is something being discussed at R&D level to make the documentation independent from the client. We are still in the planning stage for this. For the moment though, you can download (copy,paste) the openAPI specification for a given API from the API Explorer and save it in any location. The openAPI specification is a standard so it can be opened from any standard tool like Swagger. Downside is you need to take an updated copy after each update or any customization.
Hi, the IFS Technical documentation for authentication process with integrations can be found here: https://docs.ifs.com/techdocs/23r2/030_administration/010_security/040_iam_settings/050_authentication_for_integrations/We are also working on a quick start guide to this, which I can share once IFS Cloud 24R1 is released soon.
@ronhu As Gonzalo mentions above the CPdmDataHandling API you are using seems a non-standard API. Please check the implementation of that API as to why this specific error is raised. If you need to understand which Standard APIs can be used to update Engineering parts, please find the corresponding API in the API Explorer in the IFS Web Client. Further reading here (IFS Cloud 23R2 specific):API Explorer - https://docs.ifs.com/techdocs/23r2/040_tailoring/300_extensibility/020_api_explorer/#api_explorerREST APIs: https://docs.ifs.com/techdocs/23r2/040_tailoring/300_extensibility/240_integration/400_rest_apis/
@feng This is not an answer, but I’m interested in the scenario you are working on. Are you trying to push out a Streams message upon a Workflow BPA execution ?
@CdcPatrCs I’m not an expert on this specific functional area, but from what I can see, the EquipmentObjectMeasEntity is a Standard Entity type API,, meaning it would allow you to do direct CRUD operations on the EquipmentObjectMeasSet which might be the reason it only allows single update. However, in the Web Client in IFS Cloud, it’s likely that there is another API which actually gets called to update multiple object points as you describe. Please check the API being invoked when doing this in the Web Client, you can use the Debug Console to identify this.
@CdcPatrCs To answer your question:“Yes, there are other APIs, but they are not from the Integration category. Is it correct to use APIs that are not from the integration category?”The recommendation is to use integration APIs wherever applicable. However in this case it seems as Gonzalo also mentioned above, there seems to be a issue with the integration API. If so, please do report a Support Issue on it and until it is fixed you ay chose to use the Standard API used by Web Client. Later once the issue is fixed, please be sure to revert back to the integration API.
Hi, could you please create a community Idea on this please so that we can consider this as a future improvement ?
All, is this now sorted in IFS Cloud versions ?
Apps10 only supports Basic Authentication for REST APIs.Please refer this thread for more details:
Already have an account? Login
No account yet? Create an account
Enter your 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.
