Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

City services example mobile app

Updated on April 5, 2022

In this example, the city services mobile app allows city residents to report issues such as potholes, graffiti, or damaged signs. For example: As you drive through the city, you encounter a big pothole in the street. You pull over, pick up your phone, open the app, and report the pothole.

The city services application is implemented using the following APIs to submit and view a report:

  1. Log in to the app (call the Pega API GET /authenticate).
  2. View the list of possible issues to report (call the Pega API GET /casetypes).
  3. View the list of city regions (call the Pega API GET /data/D_CityRegionList).
  4. Select an issue and region.
  5. Submit the report (call the Pega API POST /cases).
  6. View all submitted reports (call Pega API GET/cases).
  7. Open a specific report to view details (call Pega API GET /cases/ID).

The following diagram shows the problem report workflow for the city services mobile app.

Problem report workflow for city services mobile app

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us