Templates & Methodology project - This project is used to store the.The downfall to doing this is that the related user accounts for the dummy users won't be deleted and will still be on the user list. Important: If you have re-used the demo employee records, the only way to keep them is to request the support team to calculate the Employee Code field to something other than DEMO or Dummy as they are currently specified.Important: If you have re-used demo projects by renaming them, the data will still be deleted and you would need to re-capture your projects.ĭemo employees and their associated users accounts. Important: If you have re-used the demo programme by renaming it, the data will still be deleted and you would need to re-capture your Programme and also update the Projects where the Programme was linked.ĭemo projects and their related entity's data (Risks, issues, costs etc.). Important: If you have re-used demo demand records by renaming them, the data will still be deleted and you would need to re-capture your records.Yes, but we suggest to clients that we only do this once you already have real data loaded so that you still have use of the reporting outputs. The main purpose for having the demo data is to give clients / users an idea of the data structure in PPO and most importantly to support the reporting outputs. When provisioning an instance of PPO you will notice that there is demo data already captured for Demand, Programmes, Projects, Employees, Users as well as the underlying project-related entities such as Risks, Issues, Costs, Resource Allocation records etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |