Read Subscriber Resource
Basic Flow
| Step | Actor | Action | Description |
|---|---|---|---|
1. |
CSR / Back-Office Department User |
Search Subscriber |
Customer Sales Representative or Back-Office User via CRM GUI searches for a Subscriber. |
2. |
CRM |
Display Search Subscriber |
CRM System displays result of Search Subscriber to the User. |
3. |
CSR / Back-Office Department User |
Request for Read Subscriber Resource Details |
Customer Sales Representative or Back-Office User via CRM GUI requests for 'Read Subscriber Resource Details'. |
4. |
CRM |
Call readSubscriberResource API |
CRM System calls Read Subscriber’s Resource API exposed by OCS.io. |
5. |
OCS.io |
Request Validation |
OCS.io validates Request whether all mandatory attributes are populated, all data types are valid, ENUMs match with definition, etc. Additionally, OCS.io validates Request against Business Logic. This typically includes, that referenced entity exists in the system, entity has proper state, etc. |
6. |
OCS.io |
Perform Business Logic |
OCS.io performs Business Logic implemented for the Use-Case. |
7. |
OCS.io |
Return readSubscriberResource Response |
OCS.io returns Response to the CRM System. |
8. |
CRM |
Result of Read Subscriber Resource Details |
CRM system displays result of 'Read Subscriber Resource Details' to the User. |
Request Validations
The following validations are performed when reading Subscriber Resource(s):
-
Subscriber must exist in the system.