D.1 List of limits applicable to all JP1/IM - Service Support products
The following table shows the limits applicable to all JP1/IM - Service Support products.
No. |
Element |
Limit |
---|---|---|
1 |
Number of process work boards that can be created in a system |
4 |
2 |
Total number of processes |
4 |
3 |
Number of users who can log in at one time |
100#1 |
4 |
Number of users and roles that can be set for one access permission specified in a process work board |
1,000#2 |
5 |
Number of Items that can be created manually or automatically in JP1/IM - Service Support |
2,147,483,647#3 |
6 |
Number of times escalation can be performed for a related Item serial number |
98 times#4 |
7 |
Number of times an Item can be edited |
5,000 times#3, #5 |
8 |
Number of files that can be attached to one Item |
5 |
9 |
Size of a file that can be attached to one Item |
5 megabytes#6 |
10 |
Number of related information elements that can be specified for one Item |
20 |
11 |
Number of times an Item form can be changed |
255 times#7 |
12 |
Number of choices that can be specified for one selection element |
30 |
13 |
Number of statuses that can be created |
40 |
14 |
Number of users that can be created |
1,000#8 (including jp1admin users) |
15 |
Number of roles that can be created |
1,000 (including system roles)#8 |
16 |
Number of users that can belong to one role |
1,000#9 |
17 |
Number of Items that can be displayed in a list of Items per page |
255 |
18 |
Number of search result elements that can be displayed in a list |
100 |
19 |
Number of JP1/IM - Manager servers that can link with one instance of JP1/IM - Service Support |
1 |
20 |
Number of JP1/AIM servers that can link with one instance of JP1/IM - Service Support |
255 |
21 |
Number of JP1/AO servers that can link with one instance of JP1/IM - Service Support |
1 |
- #1
-
A maximum of 100 users can log in at one time, but the maximum number of simultaneous accesses to the Item management database is 10. Therefore, if 11 or more users simultaneously access the Item management database, response might become slow.
- #2
-
It is assumed that an average of 20 users and roles are registered for one permission. If the Item management database reaches the maximum size, it might become impossible to set access permissions even if the limit is not exceeded.
- #3
-
If the Item management database reaches the maximum size, it might become impossible to create or edit Items even if the limit is not exceeded.
- #4
-
If the number of times an Item was edited reaches the limit (5,000 times), or if the Item management database reaches the maximum size, Items cannot be escalated even if the escalation limit is not exceeded.
- #5
-
This value includes the number of times an Item is escalated.
- #6
-
It is assumed that the average size of files attached to an Item is 256 kilobytes. If the Item management database for storing attached files reaches the maximum size, it might become impossible to create Items with attached files even if the file size limit is not exceeded.
- #7
-
It is assumed that one process uses an average of 20 Item forms. If the Item management database reaches the maximum size, it might become impossible to change an Item form even if the limit is not exceeded.
- #8
-
If the Item management database reaches the maximum size, it might become impossible to create users or roles even if the limit is not exceeded.
- #9
-
It is assumed that an average of 100 users are registered for one role. If the Item management database reaches the maximum size, it might become impossible to register users for a role even if the limit is not exceeded.