How to set mandatory fields for REST API insert/update without affecting record producers?

[JC S_]

We are trying to enforce mandatory fields when incident tickets are created/updated via REST API. To do this, we created data policies, however, this affected our Service Catalog items that is creating incident tickets via record producers. How can we implement mandatory fields for incident tickets created/updated via REST API without affecting the record producers on our Service Portal?

[JC S_]

One concern is we will flood the import import table since every update made via the api will be coursed through the import table. And can the transform be made automatically once the import set api call is made or does this need to be manually triggered?

[Chuck Tomasi]

I wouldn't be concerned about the amount of traffic. That's what import sets are for.

The transform gets triggered automatically. Basically, you post a record to the import set table via the import set API and the rest is automatic.

[JC S_]

Okay we'll check this. Going back to your first reply - I'm doing some testing now and it seems that one of our service catalog item is having an issue with data policy in place, how can we make sure that updates made through record producers on service portal is not affected by data policy. Meaning we only want to apply the data policy on rest api calls/soap calls/import sets other than that the data policy should not apply.

[Chuck Tomasi]

So you WANT to enforce the data policy on the REST API, but not on the record producer or is it the other way around?

[JC S_]

Yes we want to enforce data policy for calls/posts from REST API but not on record producers on service portal - we have UI policies in place to make fields mandatory on the incident form on fulfiller view and they are not affecting our record producers which is our desired behavior.