Technical Reference
This article contains technical reference information for Empower PPM solution components.
Note
This information is subject to change.
Software Boundaries and limits
The software boundaries and limits for Empower PPM are inherited from the relevant underlying Microsoft platforms:
Project Online
| Data Item | Limit | Consequence |
|---|---|---|
| Projects | 30,000 | New projects will fail to create |
Power Apps
The following section details the known upper limits for capacity of data processing of the following Empower PPM Power Apps:
Risks, Issues, Change Requests, Deliverables, Lessons Learned
| Data Item | Limit | Consequence |
|---|---|---|
| Register items | 2000 per register per project | New item creation disabled until item(s) are deleted |
Risks & Issues (Team member app)
| Data Item | Limit | Consequence |
|---|---|---|
| Risks | 2000 risks assigned to user | New item creation disabled until item(s) are deleted |
| Issues | 2000 issues assigned to user | New item creation disabled until item(s) are deleted |
| Projects | 2000 projects | Search must be used to refine list |
Ideas
| Data Item | Limit | Consequence |
|---|---|---|
| Idea items | 5000 items | New ideas will save but won't be visible on idea list view |
Workflow
| Data Item | Limit | Consequence |
|---|---|---|
| Approvals | 500 actions per workflow instance (reset on workflow restart) | Workflow log displays only the latest updates |
Workflow Administration
| Data Item | Limit | Consequence |
|---|---|---|
| Projects | 2000 projects | Search must be used to refine project list |
Financials and Benefits
| Data Item | Limit | Consequence |
|---|---|---|
| Project list | 2000 projects displayed | Search must be used to refine list |
| Costs | 2000 per project | New item creation disabled until item(s) are deleted |
| Cost Items | 2000 per cost | New item creation disabled until item(s) are deleted |
| Budgets | 2000 per project | New item creation disabled until item(s) are deleted |
| Budget Items | 2000 per budget | New item creation disabled until item(s) are deleted |
| Benefits | 2000 per project | New item creation disabled until item(s) are deleted |
| Benefit Items | 2000 per benefit | New item creation disabled until item(s) are deleted |
| Dates | 5 years previous and 12 years ahead of the current year | Dates will persist once saved, this limit applies to new item date selection |
General limits
| Data Item | Limit |
|---|---|
| Dates | 100 years in future and past |
| Currencies | Maximum value supported by the UI is $999,999,999 |
| Single line of text | 256 characters |
| multiline text | 63,999 characters |
| Approval maximum duration | 30 days |
| External guest users | Supported |
| Start month of Financial Year | Any month can be selected as start of fiscal year |
| Active approvals | No known upper limit, however recommended to stay under 50 active approvals per recipient |
Concurrent record editing
No hot-reload measures are currently implemented, meaning that while concurrent usage of the Power Apps by multiple users within a project is supported, there is limited protection against overwriting another user's update.
The state of protection implemented across the suite of apps can be summarised by the following three definitions.
Register apps: If a record is opened by multiple users and a field is modified, that field will be locked in other sessions until refreshing the record. If the locked field is modified before refresh, the form will refuse to save. If a record is deleted while open in other sessions, modifications will refuse to save.
This behaviour applies to the following apps: Risks, Issues, Change Requests, Deliverables, Lessons Learned and Project Progress.
Finance and Benefits: No record protection methods are implemented. If a record is deleted while open in other sessions, modifications will refuse to save. If a budget is submitted for approval by multiple users, the last actioned approval will be applied.
Workflow approvals: If a workflow app is opened by multiple users before approval submission, they each will have the option to submit. If multiple users submit, the workflow will corrupt and require a restart via Workflow Administration.