Wrapper API layer acros SN API
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2017 10:59 AM
Hi there
Did anyone implemented or thought of having a wrapper API across all SN API (Rest API). The biggest challenge SN allows end table data to be CRUD using REST API calls. But there might be many UI level rules, ACL scripts prior etc. CRUD. Sometimes its important to process in coming data prior moving to end tables. What is the best way to have all rules applied prior making end table updates? There might be ACLs with pre-script conditions as well. Deep link to a table will by pass all these rules.
Whats the best way to have a centralized convenience API which applies process+UI rules+Business rules+data massaging prior going to actual tables.
Thoughts?
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2017 11:34 AM
Hi Sashikanth,
Table APIs also apply business rules and ACLs. But if you want to do more processing on the data before moving into the end tables, you can use Import Set tables or Import Set WebServices.
Creating an import set web service
Hope this helps. Mark the answer as correct/helpful based on impact.
Thanks
Antin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2017 03:25 PM
Well that web service import sets. So in order to make Rest API to work same, you are recommending to create an import set for Rest end point as well.
Normally every out of the box table is WSDL enabled, rather using this you are recommending to create one Rest import set for each table? Same as Web service import sets, right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2017 03:42 PM
Not exactly. I would recommend the below if you have more processing to be done before the data is inserted/updated into the end tables.
1. Create an import set table based on your input fields
2. Process the incoming data based on associated transform maps and insert/update end tables
3. Invoke the ServiceNow provided Import Set REST interface Import Set API - ServiceNow Wiki
With this, you don't have to build any new APIs and fault tolerance can be handled easily too.
Hope this helps. Mark the answer as correct/helpful based on impact.
Thanks
Antin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2024 12:19 AM