You need the IFS development knowledge and the IFS Developer studio tool for making the entities (tables, views, plsql logic ...etc) and the creating the projections.
For IFS10, as far as I experienced the integration development is similar to Aurena client development and you can use the same projection created for client in integrations by changing the integration support in API explorer. This will enable using basic authentication for the REST APIs.
But in IFS Cloud, the development concept is different for integration projections and only Oauth2 is supported.
Hope it clarifies some doubts between IFS Connect and the REST Apis :)
Regards,
Damith
Hi @dsj
Thanks
I have created the table with projection. And, I have done some testing exactly the same as what is in the link you provided
My question is mainly around what needs set up in order for a third party to send inbound data using REST.
Thanks
Ross
Hi @rosscortb
If you have developed and deployed the projection, then no more configuration is required for a 3rd party to send data other that configuring the authentication and authorization (permissions).
Create a user for the the integration and grant the projection you created using a permission set. You can use basic authentication when accessing the projection with {{IFS_URL}}/int/ifsapplications/projection endpoint or Oauth2 with the {{IFS_URL}}/main/ifsapplications/projection endpoint.
Hope this blog post will help to setup Oauth2 authentication in IFS 10:
Ok, so to test, I could create a user in IFS, grant them access to projection and use Oauth2 for authentication?
One of question is, so my custom table has a just a few fields and say I try to do Post request then try to send text to a number field, how is that validation handled and post return message?
Thanks again
Ross
Hi @dsj
Thanks for your reply.
Ok, so to test, I could create a user in IFS, grant them access to projection and use Oauth2 for authentication?
One of question is, so my custom table has a just a few fields and say I try to do Post request then try to send text to a number field, how is that validation handled and post return message?
Thanks again
Ross
I haven’t got a chance to check in a IFS 10 environment, but in IFS Cloud, it returns a HTTP 400 for a wrong data type. I hope this would be the same in Apps 10 as well