Note: The risk app presented in this article has been created based on the default app template of the app generator. The apps created with the app generator can be customized to meet individual requirements. This guide describes the basic functions of the standard app template.
Aim of the app
The internal projects app is intended to provide an overview of all planned, ongoing and completed projects in the company. The individual project phases can be viewed and the associated tasks can be controlled.
Ideas for projects can be proposed in the app. The project idea is either approved or rejected. The project is moved to the status in implementation if approved. Milestones can then be defined. Associated tasks and resolutions can be assigned via the milestone overview. Once all tasks and milestones have been achieved, the project can be archived with all associated data upon successful completion by moving it to the Project Completed status. In addition, if required, the project can be moved to the status on hold and from there deleted directly or moved back to the status in implementation.
An app element is divided into 3 sections:
Details of the framework data regarding the costs, the team and the progress of the project.
Overview and task management of the milestones
Project documentation and attachments
In the project details, general info is maintained, which allows to classify the effort and relevance of the project. If a new project idea is proposed, the creator must provide the basic framework data about the project, team, processes and costs. In the running project, the project progress can be documented, justified and evaluated.
Milestones are defined via the overview and relevant tasks are delegated to the project team via the task management. Decisions, processes and deadlines can be anchored in the tasks.
In the third section, the project is documented via the free text field and the attachment overview.
In the configuration mode under the tab Roles it is defined which users or groups are authorized to view and control the overview of all projects. These role owners are authorized to edit the requests in the respective release stages and to move them to the next status. They can also be used to determine viewing rights to specific projects and the entire application. It is essential to define these roles before launching the app.
In the Internal Projects app, in addition to the mandatory adjustments to rights management just described above, optional adjustments to project frame data and the overview of projects are possible. Furthermore, additional workflow jams can be defined for the project status. The application is then ready for use.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article