In this tutorial, you will learn how to use App Engine Studio to build a departmental request app in your Personal Developer Instance (PDI) through step by step instructions and video.
You can find a completed version of this app on GitHub: departmental-request-app
You can watch a 10-minute video of the app being built and tested, and each of the exercises in this tutorial has a more detailed video of someone working through the exercise.
<iframe id="video" width="560" height="315" src="https://www.youtube.com/embed/fy3RWHhlr0k/" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen=""></iframe>You will need a Rome PDI with the latest version of App Engine Studio installed. You can follow the instructions at the bottom of the Rome AES blog post to upgrade AES to version 20.0.1 or to check the version.
The use case that you will work through in this app tutorial is a generic departmental request app. Many departments in an organization need a way to handle requests for something from outside of their department. This usually starts with a shared mailbox and a spreadsheet to track these requests, but that type of solution doesn't scale and can't be automated very well. In this use case, you will be building an app that transitions from the old email/spreadsheet to a catalog form on the portal, a dedicated experience for fulfillers, approval and email automation, and data security.
In this tutorial, you will use App Engine Studio to build:
- A data model with request and request type tables.
- A catalog experience for requesters.
- A workspace experience for approvers.
- An approval flow.
- A completed email flow.
- A security model with fulfiller and admin roles.