25r2 Workflow IFS internal REST API Call

​@ext.nchen2  could we have more contexte please?

Which API are you trying to call? whata parameters?...Etc

​@N.GEORGI  

Thanks for the response, I am trying to access this API: 
GET /main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='XXXXXX')/SupplierPayments(Company='XXXXX',Identity='XXXXX',PartyType=IfsApp.SupplierHandling.PartyType'Supplier')/PaymentWayArray

 
The request works in postman with an Authorization token, but no method seems to work in workflow (there is no body in the request)
 

Hi ​@ext.nchen2 

I tried calling the API you mentioned using a REST task with both the same host and a different host in the 25R2 central environment. Here are the workflow steps I followed. I hope this is similar to what you are trying to do as well.

Same Host (ifs25r2bnddevcmb)

Different Host (calling an API hosted in ifs25r2bnddevlkp from ifs25r2bnddevcmb)

1. Create a REST Task Configuration. The IAM details can be found on the IAM Client page in ifs25r2bnddevlkp .

   

    

   Token Endpoint : https://ifs25r2bnddevlkp.rnd.ifsdevworld.com/auth/realms/ifs25r2bnddevlkp/protocol/openid-connect/token
   
    

2. Select Authentication Type as OAuth 2.0 and set Auth Config Name to the REST Task Configuration you created.

   

    

​@pdollk Thanks for the response, I’ve tried the exact same setup with both no authentication and the OAuth 2.0, both on the same realm. However I run into errors.

 

Hi ​@ext.nchen2 , 

If i were to suggest an alternative approach to try out and see

We may be able to take advantage of how the OData spec works here for our advantage.

In “API explore,” page we can analyze how the api spec is declared. The request format appears as shown below. Under “SupplierHandling,” in the “Get entities from PaymentWayArray” section, the GET request is:

/main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='{SupplierId}')/SupplierPayments(Company='{IdentityPayInfo_Company}',Identity='{IdentityPayInfo_Identity}',PartyType=IfsApp.SupplierHandling.PartyType'{IdentityPayInfo_PartyType}')/PaymentWayArray

the actual request you shared is like this

GET /main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='XXXXXX')/SupplierPayments(Company='XXXXX',Identity='XXXXX',PartyType=IfsApp.SupplierHandling.PartyType'Supplier')/PaymentWayArray

From there, we should be able to reference SupplierPayments directly, which is really an IdentityPayInfo entity reference underneath. Per the OData spec, we can point to it through Reference_IdentityPayInfo and then use the “PaymentWayArray” nested entity array to pull the information needed in the API task below.

for the Party type we have the following options, in this case its “Supplier”

in the API task we can do a call like this get the same result 

​@kamnlk Thanks a lot for your response. Although this method does work, the reason I wanted to access that specific API was so that I could update, modify, and delete the entries within it. Do you know any way to do this or how to fix my original problem of the IFS REST API always having a 500 http error for only IFS API calls (including other realms)?

Hi ​@ext.nchen2 

You can update, modify, and delete entries using this alternative approach by changing the action here.

It is a much safer approach because when you use a REST Task, there is no rollback if an error occurs during the OData request or later in the workflow execution. However, if you use an API Task as in the alternative approach, the transaction will be rolled back when an error occurs.

Of course, the best approach depends on your requirements.

If you still need to investigate the original issue with the REST Task, obtaining the OData logs when the error occurs would be very helpful.

As mentioned in my previous comment, I tested this in the central environment and got the expected results. Can you confirm whether the URL and the results I shared are correct?

for the original question, i suspect its a problem with how its configured.

if possible, can you share the exact url value you are using in the URL of the IFS REST task ? 

in both the rest task configuration and in the REST task you must use a full url for it to work (<hostname>/main/ifsapplications/projection/...), rather than only the (/main/ifsapplications/projection/...) if not we might get errors