Hi,The Supply Chain Management (SCM) forum could be a better place to find an answer for this question.https://community.ifs.com/supply-chain-251
Hi,This would depend on the batching capabilities of the external API you are calling. For example IFS Cloud REST APIs supports batching multiple operations into a single requests. https://docs.ifs.com/techdocs/23r1/040_tailoring/300_extensibility/100_odata_provider/700_batch_requests/Do you see any limitation in the Workflow designer itself that is limiting the payload to just one object?
Hi,You should be able to type this structure in the request body textbox in the Workflow designer right? I think more importantly what you need to check is whether the external API will accept such a structure and create multiple objects? This will not work unless the external API actually supports it.
Hi @FleStefSc Appreciate if could mark Gonzalo’s response as the answer to help others easily find a resolution to similar requirements
Hi @GaSoGB The best approach IMO here would be to place an API Management solution in front the IFS APIs (perhaps only the ones you need to expose) and get external systems to call IFS APIs via the API Manager. This will give you comprehensive governance capabilities (including monitoring, auditing etc.) for external API invocations.Regards,/Rifki
Yes this will need to be a third party solution that could be commercial (most likely) or free/open source. No we don’t have any plans to embed an API manager in the near future.
Hi @EntUviniG This is most likely due to how the APIs have been designed to work than the Workflow/BPA functionality itself. It seems like the the record you are trying to create will get filtered out in a subsequent read operation. Therefore the API prevents you from creating a record that you cannot access. This can be due to the values in your payload as well as some where condition in the underlying datasource.You can verify this by calling the API with the same payload from a tool like Postman using the same user credentials.Thanks,/Rifki
Hi,The main reason to have the “Include in Application Compatibility Type” feature in IFSAPPS 10 was to make it possible to use http basic authentication on the “int” context for APIs that were available on the “main” context. However IFS Cloud no longer supports/recommends http basic authentication due to security reasons. This means you can directly use the APIs from the main context using OAuth negating the need for “Include in Application Compatibility Type” in IFS Cloud.
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.