What's new in Customer Journeys?

Connect and learn more!
Different Approval Logics for Manual Supplier Updates and via APIs — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Different Approval Logics for Manual Supplier Updates and via APIs

Received Response
4
Views
1
Comments
edited Jan 15, 2024 6:10PM in Supplier Management 1 comment

Summary:

Can separate approval rules be built based on who initiated the Supplier profile change - an internal user or an integration via APIs?

Content (please ensure you mask any confidential information):

We have the following scenario:

  1. Supplier records can be updated either by users or the Suppliers themselves (standard) or via an integration.
  2. We need to auto-approve the changes made by the integration via APIs, but send for approval all the other changes.

We could not locate an attribute like Creation Source to build this logic. Is it possible? And if yes, what attribute can be used?

Also, can updates made via APIs be auto-approved via the APIs themselves?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!