| 1. | Rejected article details | The OPRS Notification Service, POST rejected Articles Details in query params (Document Id and Site Name) to MuleSoft Rest API |
| 2. | Get Submission, Author and Person Details | Marketing preference experience API Request to Scholar One API to retrieve the Submission, Author, Person data |
| 3. | Response Submission, Author and Person Details | Returns the success response to MuleSoft along with Submission, Author and Person data. |
| 4. | Validate if person is opted-in | Process the payload is person is Opted-in. |
| 5. | Validate if either Email ID or ORC ID supplied | Validate Email ID or ORC ID should be present, If validation fails, service returns specific error response. |
| 6. | Response Message Accepted | On successful validation API sends accepted response to client. |
| 7. | Post Account and Preference Details | The MuleSoft experience API Post account and preference details to marketing preference process API. |
| 8. | Create or Update End User Person Account | Marketing preference process API validates if record exist in salesforce, accordingly, sends PUT or POST call to downstream Salesforce system API. |
| 9. | Feed End User Person Accounts data | Salesforce SAPI creates or updates End User Person Account feed. |
| 10.1 | Success Response Create or Update | Salesforce SAPI responds back to caller API with success details in JSON format |
| 11.1 | Failure Response Create or Update | Salesforce SAPI responds back to caller API with exception details in JSON format. |
| 11.2 | POST Data Feed Exception | Salesforce SAPI transform the exception details and feed the details back to Salesforce Data Feed Exception object. |
| 12. | Return response from Salesforce System API | Returns the success response to marketing preference process API. |
| 13. | Return response from marketing preference process API | Returns the success response to marketing preference experience API. |
