The following describes the steps required to perform some of the operations most common.
Sign in
- Call login service by sending the required parameters.
- Get the response from the service.
- Store data such as user ID and authorization token as they will be required for subsequent services.
Renew Session
- Call the session renewal service by sending the authorization token that is stored.
- If the service’s response is successful, the token is still valid.
- If the service’s response is unsuccessful, it is necessary to obtain a new token according to what is indicated in the login scenario.
Create a case
- Obtain an authentication token as indicated in the sign-in or renew session scenarios, as appropriate.
- Consume the authoring service by sending authentication header and request body with the corresponding data for the case as appropriate.
- To manage, as appropriate, the data obtained as a result of consumption of the service.
Get Case Detail
- Obtain an authentication token as indicated in the sign-in or renew session scenarios, as appropriate.
- Consume service of obtaining case detail by sending the data corresponding to the case to be consulted.
- To manage, as appropriate, the response obtained from consuming the service.
Update a case
- Obtain an authentication token as indicated in the sign-in or renew session scenarios, as appropriate.
- Consume the case editing service by sending authentication header and request body with the data to be edited.
- To manage, as appropriate, the data obtained as a result of consumption of the service.