R&S® CeLo Central Logistics
R&S® CeLo Central Logistics
The user can log in with their login name or email address and password. The account must exist in CeLo.
The user is logged in directly without having to enter any login data.
The tab "SingleSignOn" in the system information dialog allows the sysadmin to activate the Single Sign-On feature by selecting the applied protocol OpenID Connect.
An additional button has been placed at the bottom for configuration, which opens a new dialog where the following metadata values can be defined:
| Column | Metadata |
|---|---|
| 1 | Realm URL |
| 2 | Authorization Endpoint |
| 3 | Token Endpoint |
| 4 | User Info Endpoint |
| Column | Metadata |
|---|---|
| 1 | Client ID |
| 2 | Client Password |
| 3 | Host Name |
Note:
The user must first log in with their login name or email address and password.
If the login is successful, the user will receive a PIN by email to confirm registration.
The sysadmin can activate this function and set the number of possible attempts in the '2-factor authentication' tab in the system information dialog.
sysadmin has entered the PIN sent to his email.
sysadmin can reactivate the account by changing the password.
Following terms are used in this software:
For the analysis, the following values are displayed or calculated:
| Value | Calculation |
|---|---|
| MTBF [h] | = Lifetime / Cycles * (Operating hours) |
| Lifetime [d] | = Sum of the times during items of this type were built in |
| Cycles | = Number of built-in-cycles. The number of built-in-cycles is incremented when the item is removed with a status that is MTBF relevant. |
| TARGET | = (Number of items built-in) * (Operating hours) * (In-service life) / MTBF |
| ACTUAL | = (Number of items not built-in) = (Number of Items in depots and other folders/projects) |
Under some circumstances the Drag & Drop function in the tree view is disabled. These circumstances are listed below:
* for any number of characters and ? for exactly one character can be used.> 01.01.2014 or < 01.01.2014 14:00 can be used to narrow periods of time (from or to). If only one date without comparison and time is specified, the filter is considered from this day up to 0:00 of the next day.2014-05-01 or 2014-05-01-14-00>, <, >=, <=, = and <> or != can be used. Alternatively, a range (e.g. 20-50) can be entered.| Source type | Required settings | Key restrictions |
|---|---|---|
| Excel (.xlsx) | Save in native .xlsx format | No embedded newlines in cells (Alt + Enter). In the first row, the last column must not be empty |
Unicode text (.txt /.csv) | UTF-8 or UTF-16 without BOM | No newline characters inside fields |
| Identification | Meaning or content of the following data lines |
|---|---|
Level | Hierarchy level of the structured parts list starting with 1: 2 is subordinated to 1, 3 is subordinated to 2, ...(optional) |
MFC | 5 digit manufacturer code |
TypeID | Part number |
TypeName | Name/description of the type |
TypeComm | Comment of the type (optional) |
TypeMeta | Content of the meta data of the type matching to row 1 (optional) |
Group | Name of type's group definition. The import settings allow to specify whether new groups should be created. (optional) |
ItemSN | Serial number of the item |
ItemComm | Comment of the item (optional) |
ItemMeta | Content of the meta data of the item matching to row 1 (optional) |
Weight |
Color |
||||||||
|---|---|---|---|---|---|---|---|---|---|
Level |
MFC |
TypeID |
TypeName |
TypeComm |
TypeMeta |
Group |
ItemSN |
ItemComm |
ItemMeta |
| 1 | D0894 | abc123 | typeName1 | comment type1 | 12 Kg | System | 123-123 | comment item1 | red |
| 1 | D0894 | xyz001 | typeName2 | comment type2 | 5 Kg | LRU | 001-001 | comment item2 | green |
Level, Seq, TypeID, MFC, TypeName, Group, followed by the names of the meta data to be imported.| Column | Meaning or content of the data lines |
|---|---|
| 1 | Hierarchy level of the structured parts list: 1 is subordinated to 0, 2 is subordinated to 1, ... Level = 0 means Top-Level-Type Level can start at any value |
| 2 | Order of types at the current hierarchy level starting with 1. Multiple specification of the same order creates an OR-type. |
| 3 | Part number |
| 4 | 5 digit manufacturer code |
| 5 | Name/description of the type |
| 6 | Name of type's group definition. The import settings allow to specify whether new groups should be created. (optional) |
| 7... | Content of the meta data matching to row 1 (optional) |
TypeID).MFC, TypeID.Name, Group, TypeComm.| Identification | Meaning or content of the data lines |
|---|---|
MFC | 5 digit manufacturer code |
TypeID | Part number |
TypeName | Name/description of the type (optional) |
Group | Name of type's group definition. The import settings allow to specify whether new groups should be created. (optional) |
TypeComm | Comment of the type (optional) |
| Identification | Meaning or content of the following data lines |
|---|---|
MFC | 5 digit manufacturer code |
TypeID | Part number |
ItemSN | Serial number of the item (optional) |
TypeMeta | Content of the meta data of the type matching to row 1 (optional) |
ItemMeta | Content of the meta data of the item matching to row 1 (optional) |
| Identification | Meaning or content of the following data lines |
|---|---|
ItemSN | Serial number of the item (optional) |
ItemMeta | Content of the meta data of the item matching to row 1 (optional) |
Tkz, HSTK, Anzahl.| Column | Meaning or content of the data lines |
|---|---|
| 1 | Part number |
| 2 | 5 digit manufacturer code |
| 3 | Amount of items of this type |
| Column | Meaning or content of the data lines |
|---|---|
| 1 | NCAGE (manufacturer code) |
| 2 | Name of the manufacturer |
| 3 | City |
| 4 | Contact data (optional) |
| 5 | Phone number (optional) |
Each CeLo instance features a special user named sysadmin. This user has access to all projects
and is the only one that can alter the CeLo configuration. System administrator rights cannot be changed and thus
sysadmin is not visible in the users or project right dialogues.
In a new CeLo sysadmin has a default password that can be found in the installation manual or is provided
by your vendor.
It is highly recommended to change this password as soon as possible to avoid security risks. All users
with admin rights will be shown a warning on login as long as this is not done.
Newly created users get a temporary password by the administrator which must be changed on the first login.
There are two types of user rights:
The global rights can be set under the menu item Configuration / User Administration and control access to project-independent settings such as editing manufacturers, group definition, creating projects and the user administration itself.
The project-related rights can be set under the menu item Configuration / Project Rights and define for each project, which actions an assigned user may perform.
| Topic | Operation | administrate | edit | external | move | read |
|---|---|---|---|---|---|---|
| Project | view | |||||
| create | ||||||
| edit | ||||||
| delete | ||||||
| activate/deactivate features | ||||||
| Folder | create | |||||
| move | ||||||
| rename | ||||||
| delete | ||||||
| Depot | create | |||||
| move | ||||||
| rename | ||||||
| delete | ||||||
| Items | create | |||||
| edit | ||||||
| move | ||||||
| delete own | ||||||
| delete others | ||||||
| change transit state | ||||||
| change operability | ||||||
| add to / remove from equipment | ||||||
| built in / out | ||||||
| create / edit manual history entries | ||||||
| delete manual history entries | ||||||
| edit built in/out states | ||||||
| delete manual states | ||||||
| Item Attachments | attach to own items | |||||
| attach to others items | ||||||
| edit own attachments (category/comment) | ||||||
| delete own attachments | ||||||
| edit others attachments (category/comment) | ||||||
| delete others attachments | ||||||
| view and download item attachments | ||||||
| edit attachment categories | ||||||
| Item Metadata | create new metadata rows | |||||
| edit rows | ||||||
| delete rows | ||||||
| edit metadata values | ||||||
| Types | view type list | |||||
| create | ||||||
| edit | ||||||
| delete own | ||||||
| delete others | ||||||
| edit equipment | ||||||
| type analysis (MTBF, actual, target, etc) | ||||||
| recalculate MTBF | ||||||
| view structured parts list | ||||||
| view urgency status | ||||||
| edit urgency status | ||||||
| Type Attachments | attach to own types | |||||
| attach to others types | ||||||
| edit own attachments (category/comment) | ||||||
| delete own attachments | ||||||
| edit others attachments (category/comment) | ||||||
| delete others attachments | ||||||
| view and download type attachments | ||||||
| edit attachment categories | ||||||
| Type Metadata | create new rows | |||||
| edit rows | ||||||
| delete rows | ||||||
| edit metadata values | ||||||
| Import | text file, POP | |||||
| types | ||||||
| metadata | ||||||
| actual item values | ||||||
| Alarms | view own alarms | |||||
| view others alarms | ||||||
| create/edit/delete own alarms | ||||||
| create/edit/delete others alarms | ||||||
|
Exceptions:
*) Always 'No', unless the user has the global system administrator right
| ||||||
| Topic | Action | Administrate | Planning (edit operations) | Design and reservation | Design and scanning | Read |
|---|---|---|---|---|---|---|
| Operations | read | |||||
| edit | ||||||
| edit comment section | ||||||
| delete | ||||||
| import | ||||||
| create new / clone | ||||||
| Design | read | |||||
| edit | ||||||
| finish state | ||||||
| return to previous state | ||||||
| Reservation | read | |||||
| edit | ||||||
| finish state | ||||||
| return to previous state | ||||||
| Packing | read | |||||
| edit (via Scan-Tool) | ||||||
| edit (via Scanner/Input) | ||||||
| edit (manually set 'not scanned') | ||||||
| edit (set scan state manually) | ||||||
| create export list | ||||||
| finish packing state | ||||||
| return to reservation state | ||||||
| Return | read | |||||
| edit (via Scan-Tool) | ||||||
| edit (via Scanner/Input) | ||||||
| edit (manually set 'not scanned') | ||||||
| edit (set scan state manually) | ||||||
| create export list | ||||||
| finish return state | ||||||
| return to packing state |
Data sources allow for automatic or manual updates of item and type data fields.
The usage of data sources must be activated in the configuration file with the parameter UpdateViaSrcIsActive set to true and the parameter SchedulerIntervalInSec set to a value greater than 0.
Users with administrator rights can access the source dialogue via 'settings'. All sources have the following settings in common:
| Name | Description |
|---|---|
| Sequence | Is used in context menu for manual update and during automatic runs, meaning that sources with higher sequence number run first. These numbers must be unique. |
| Project | Defines for which project items are updated. |
| Name | The name is seen in the history and in the manual update buttons, according to the selected language. |
| Mode | The mode defines how the source can be used. Valid options are off, only manual, only automatic or both. |
| Start and end time | Defines the time frame when the source can get activated automatically. There is always one source active at most. This time frame should be preferably set to night time and outside server maintenance windows. |
| Last call | Time of last successful processing. Automatic activation only proceeds if the last call was not today. |
| Description | The description is used only in this dialogue for comments. |
These sources start an executable file and process its output. The following settings apply:
| Name | Description |
|---|---|
| Working directory | Directory where the executable file is located. |
| Process | Name of the executable file. |
| Request | Structure of the parameters for the process, including placeholders. Allowed placeholders: [omitt], [name], [partnum], [mfc], [comT], [ser], [comI], [metaT], [metaI], [date], [due], [inter], [status], [cert]. Metadata fields need a number. Example: partnum='[partnum]';sdnum='[ser]';nsn='[metaI3]' |
| Response | Expected structure of a successful response from the process (on standard out). Example: Success: caldate='[date]' caldue='[due]' calint='[inter]' cert='[cert]' calstatus='[status]' |
| Error | Expected structure of an error message from the process (on standard out). This is needed to detect erroneous responses. Example: Error: Item not found: |
| Example | Example for a valid request. Can be used in the test routine. |
| Timeout in ms | Defines how long the process may run until it is terminated.. |
| Retries | Number of retries if the process returns with an error or gets terminated. |
| Items per run | Defines the number of items that will be processed per automatic run. If the value is = 1, all items are processed. For values less than 1 this fraction will be processed (oldest first). Values above 1 denote the actual number of items processed. |
These data sources read a CSV file and update the referenced items and types. After processing the input file, an output file is written. They can be identical. The following settings apply:
| Name | Description |
|---|---|
| Last input file change | The input file is processed only if there had been a change since the last run. |
| Input file path | Absolute path to the CSV file read by the source. |
| Output file path | Absolute path to the CSV file written by the source. |
| Output parameters | Order of output columns in the output and input file. The input and output parameters must be from the following list: omitt, name, partnum, mfc, comT, ser, comI, metaT, metaI, date, due, inter, status, cert. The entries metaT and metaI must be followed by a number. CeLo fills these according to the items. The output file also contains the input parameters in its header, but these columns are not filled by CeLo. Delimiter is ; |
| Input parameters | Order of input columns in the output and input file. These columns are expected to be filled in the input file. |
| Header | Header of both files. The amount of delimiters must be the number of delimiters of the input and output parameters plus 1. |
| Items per run | Defines the number of items that will be processed per automatic run. If the value is = 1, all items are processed. For values less than 1 this fraction will be processed (oldest first). Values above 1 denote the actual number of items processed. |
| Write all data | Writes all data into the output file if active, not only the data defined as output. This is needed when input and output files are identical in order to not loose data in unchanged fields. |
| Example | Example for a valid request. Can be used in the test routine. |
| Test output | Directly writes an output file. |
| Test input | Directly tries to read the input file and gives a summary of how many items and types would be changed. Does not perform any changes though. |
| Process input | Directly tries to read the input file and modifies the affected items and types. |
| ID | Topic | Description |
|---|---|---|
| New features | ||
| 228 | History for containers |
It is now possible to view what happened in depots, folders and projects.
The history tab is accessible by right clicking a depot, folder or project in the navigation tree and selecting 'Show history'.
There are two major ways to filter the history entries:
1. The 'Status' column. Users can select which events are shown. Default is 'items moved here' and 'items moved from here'. Other examples are 'own history', 'items created', 'items built out here'.
2. The checkbox 'show history for subfolders'. This allows to view all history events of underlying folders and depots. This is particularly interesting for project history.
|
| 222 | History for slots |
There is a new tab in the details section in the main view: Slot history. It shows all built in and built out operations for the selected slot (work for both filled and empty slots).
The built in dialogue also shows for each eligible item if and when it was built in at this particular slot.
|
| 227 | Last built-in items |
It is now possible to see information about the last items that were built in at empty slots. If active, the empty slots have a grey instead of a red icon and show the serial number and item meta data of the last item that was built in at this slot, if eligible.
This last item information is also used during exports, if active.
This feature is activated in the user settings via 'empty slots behaviour' with the following options:
'always show empty slots': identical behaviour as before version 8.0.0: empty slots always just show the corresponding type(s).
'show empty slots as default': identical behaviour as before, but the 'Equipment' Tab and the 'Reservation', 'Packing' and 'Return' Lists in the planning view have a new button to toggle the last item information
'show last item as default': this option sets the default to show the last item information instead of the empty slot.
|
| 231 | Minimum stock warnings for depots |
Administrators can now define minimum and maximum stock limits for depots.
This option can be accessed by right clicking a depot and selecting the 'Manage stock limits'. The default settings for minimum and maximum is '-1' which means no limit.
The field labelled 'user' defines which users shall be informed if the limits are triggered. The first time a maximum limit is exceeded or a minimum limit is undercut, an email with the corresponding comment is send to the predefined users.
In addition, a red downward or upward facing graph icon is shown next to the depot. All stock limits can be viewed in the new 'events' view.
|
| Improvements and bug fixes | ||
| 246 | Headers in corporate identity |
The headers have been redesigned to better structure crucial information and clearer represent the company brand.
The headers now show the following information:
Product Name
Server name
Information about the current view (e.g. Items, Planning, OM)
Name of current project, if available
Project comment, if available
|
| 232 | Input sanitation everywhere |
User inputs are now always sanitized according to
OWASP rules. |
| 242 | New update import for basic type data |
A new update import can modify type names, comments and groups. Details can be found in the 'Import' section.
|
| 245 | Button to delete unused types |
Types without items are not delete automatically.
In order to avoid manual labour to delete them one by one, there is a new option in the 'administrate' dialogue of projects.
|
| ID | Topic | Description |
|---|---|---|
| 224 | User comments in planning view for reservation and design |
Users can now write light weight comments for all entries in the design, reservation, packing and return state.
There is a new column with a "plus" button to write new comments. Moving from one phase to the next, the comments are copied but independent afterwards. This means that comments in earlier phases don't change when the comment in the current phase gets edited or deleted.
Comment changes are not tracked in the operation history. Cloning an operation also clones its comments.
Displaying the comments is deactivated per default and can be changed in 'user settings'. Valid display options are 'front', 'end' and 'off'.
|
| 223 | Import rework |
The text import dialogue has been overhauled. Most importantly, it is now possible to import excel files directly. Further details are described in the above section "imports".
|
| 221 | External sources: Update Item and Type information via CSV file |
Sources can now be created and edited in a new dialogue in "Settings" under "data sources".
It is now possible to create input sources that write item information into a CSV file and later read a similar file, enriched by data updates. See the section sources for more details.
|
| -- | Additional 'OK' button in the scan dialogue |
The scan dialogue now has another 'OK' and 'Cancel' button at the top left to make it easier to use on smaller screens.
|
| ID | Topic | Description |
|---|---|---|
| 212 | Scanning foreign devices |
Until now, scanning devices in CeLo scanning dialogue only considered devices listed in the selected operation. From this version on, every scan action checks if the scanned item is part of an operation in return mode.
If this is the case, the item state in that operation is set to 'returned'. With this change it is now possible to scan devices only once when they return: they are either scanned onto the next operation in packing state or via CeLo scan tool back to the depot.
History is maintained correctly and a summary is shown when the scanning action is finished.
|
| ID | Topic | Description |
|---|---|---|
| 210 | Better distinction of calendar weeks |
The calendar week information is now separated by a vertical line from the date in the timeline.
|
| 209 | CeLo Scan Tool less strict while matching depot names |
Until now, the CeLo Scan Tool expected scanned depot names to match exactly with the depot names in CeLo. From now on, it is sufficient that the scanned name is contained in the CeLo depot name.
|
| 207 | Bulk add equipment |
Up to now, adding several identical slots to the equipment had to be performed one by one. From now on, this can be done in one step. The field 'count' can be used to set the number of new, identical slots.
|
| 204 | Move to depot context menu for free items |
Until now, the only way to move an item to a different depot was via drag and drop. From now on, a context menu entry in the navigation tree and main view opens a dialogue with a filter- and sortable list of all available target depots.
|
| 201 | Comment plus colour for conflicts |
The conflicts list features a new column for comments.
User can create new comments by clicking the plus icon in the new column. In addition to text the comment can have a colour. Filtering is possible on comment text as well as colour. Only the text gets exported.
|
| 199 | Extension of scan packing dialogue by field 'box' |
The scan dialogue features a new optional field for items named box.
User can set the box value at the beginning of a scan session. All scanned items will be labelled with this value. Users can change this label via context menu for one or several selected items. The box label is shown in the packing and return list and gets exported.
|
| 198 | Reminder before license expiration added |
The login screen shows a reminder if the license is due in 21 or less days.
|
| 184 | Technology update |
Primefaces 14, Java 24, Tomcat 10.1.39 |
| ID | Topic | Description |
|---|---|---|
| 196 | Empty slots can now be shown in packing list and scan dialogue |
An icon in the packing list enables all empty slots to be shown. This option is used in the scan dialogue es well. It is disabled per default.
|
| 195 | manual history entries repaired |
A technology update disabled this feature
|
| 193 | Planning right 'design' extended to 'design and scan' |
The role 'design' is now able to scan devices.
|
| 190 | Calibration conflicts computed correctly |
Problems occurred sometimes when the reason for a conflict got resolved, resulting in left over conflicts.
|
| 167 | Timeline shows weeks |
The timeline now shows weeks or months and weeks, depending on the zoom level.
|
| -- | Display of item reservations in timeline repaired |
The item timeline showed wrong reservation durations at times.
|
| ID | Topic | Description |
|---|---|---|
| 163 | Improved Planning View |
In the planning view, the table headers are fixed and remain visible at the top of the screen, regardless of the scroll position.
The timelines have been moved to the left and are now closer to the serial numbers of the items to achieve better visibility.
Vertical scrolling behaves identically when hovering over the timeline and the table. Additionally, the timelines can be zoomed in and out using the new zoom buttons or the Ctrl + mouse wheel shortcut.
|
| 78 | PrimeFaces update to 13.0 |
CeLo has been upgraded to the latest released version of PrimeFaces, enabling access to new features, improved performance and better stability.
While the overall appearance may seem unchanged at first, a closer look reveals that certain features, such as the layout toggle, calendar, and colour picker, have undergone a significant redesign.
|
| -- | Direct selection of singleton project after login |
Should the user be allowed to see exactly one project then this project will be selected automatically after login.
|
| -- | Date filter repaired |
The date filter in the operations tab has been repaired. They find all date entries that contain the searched text. Example: The input
09 will find the dates 09/01/25 and 12/09/25. |
| ID | Topic | Description |
|---|---|---|
| 172 | Filter by Enter |
The sysadmin can enable this option in the 'System Information' dialogue, on the tab 'Filter Delay'.
If this option is active, the filter delay is ignored, and the filter is applied only after pressing the enter key.
This setting applies to all tables with filter option.
|
| 171 | Improved clear filters in planning view |
The filters in the main items table in planning view are now retained.
The user can interact with the planning view without losing their filter settings, even when activating/deactivating checkboxes, switching tabs, or changing operations.
The filters can be deleted all at once using the eraser button in the top bar on the right or manually one by one.
|
| 162 | Export available for tables in planning view |
The export function was included for the conflicts, design, reservation, packing, return and history tables.
|
| 161 | Quick search: items are searchable by serial number |
the input field on top of the tree in the main view is now available for searching items by their serial number.
If the QR code feature is enabled for the project, the field will search for items by their ID; otherwise, it will search by serial number.
The search is performed on a per-project basis, therefore, a project must be selected.
|
| ID | Topic | Description |
|---|---|---|
| 153 | Email settings extension |
The email settings dialog has been changed. Now email server settings like host, port, username and password can only be changed in the system information dialog.
However, in the email settings dialog it is now possible to change project-specific emails for alarms and operations as well as general emails for new users, 2FA and 2FA users blocked
As before, the sender, subject and content can be changed for each of these emails.
|
| ID | Topic | Description |
|---|---|---|
| 151 | 2-factor authentication |
The sysadmin can activate 2-factor authentication via the 'System Information' dialogue.
After logging in, the user receives a 5-digit PIN by email, which must be entered into a small dialog in order to confirm the registration
E-mail and password changes must also be confirmed by the PIN.
The sysadmin can specify how many attempts are possible. If this limit is exceeded, the user will be blocked. The account can be reactivated by sysadmin changing the password.
Newly registered users will receive an automatic email with their login information.
|
| ID | Topic | Description |
|---|---|---|
| -- | Update installation guide and added import examples |
The installation files now come with a guide in
_ReadMe_/CeLo_installation_guide_for_MSSQL.pdfThere, the installation with
MSSQL is described, the global parameters are explained and two tutorials show how to import data via text and excel file. |
| ID | Topic | Description |
|---|---|---|
| 152 | Improved selection of visible columns |
From now on, when users change the column visibility their selection is persisted across views.
Changing the visibility in item view, main view and planning view affect all other views.
These settings still are user specific and can be reset by the 'delete' button in main view.
|
| ID | Topic | Description |
|---|---|---|
| 113 | SingleSignOn via OpenID |
The sysadmin can activate single sign on via the 'system information' dialogue.
Right now, OpenID is the first technology supported. You can set the
realm URL, endpoints, credentials, host name and other in the settings tab. |
| 108 | Introducing new project right 'move' and planning rights |
A new right is introduced named 'move' that allows only for changing location and building in/out for items.
In addition, a detailed rights concept is introduced for the planning view. See section above for details.
|
| ID | Topic | Description |
|---|---|---|
| 137 | Visibility of columns changeable for all users |
Up to now, changing visibility in the dialogue edit columns did not influence user specific views.
From now on, a check box allows to force the visibility change onto all user views.
|
| 132 | Planning view: Changing scan status |
From now on, the scan status of items can be reset to missing or not scanned, even if it was already set to scanned.
|
| 136 | Planning view: finished operations could block item packing |
Closing an operation manually could have led to a situation where items were still marked as packed in the closed operations.
This affected other operations because they could not pack these items for themselves.
|
| 135 | Planning view: Bugs fixed in design phase |
Doing lots of changes in the planning view simultaneously could have led to inconsistent states.
|
| 104 | Planning view: Deleting items was blocked by finished operations |
Deleting an item that is still used in an operation is not allowed.
However, deleting items mentioned in finished operations was blocked as well.
|
| ID | Topic | Description |
|---|---|---|
| 2 | Planning view |
CeLo now features a planning view to support service operations.
This feature must be activated via a special license. Further information can be found in the corresponding user manual.
|
| 35 | Detailed import options |
Importing a text file can be configured in many ways now, for example by changing the delimiter or by removing specific characters.
In addition, it is now possible to import the group definitions.
A new import menu named text import (with options) has pre-configured settings for files exported from excel.
|
| 59 | Scan dialogue for depots |
There is a new option to move multiple items to a depot.
Right click a depot and select the option scan items. Enter the serial number into the select box or use a scanner device.
The entry will be coloured green if the item is already in the depot. A new entry in yellow will be shown if the item can be moved into this depot
Unknown items will be listed in a separate table below. The data column used for the search can be changed to any item specific data column. Clicking Ok moves these items.
|
| 77 | automatically generated links |
Until now, automatically generated links were visible in the type search only.
From now on, most tables showing items will make use of them.
|
| 98 | Performance improvements |
Items are now cached globally, so that already fetched items do not have to be looked up in the database again.
The Cache has an adjustable size. As soon as it is filled, further items replace the oldest ones in the cache.
The configuration parameter
ItemCacheSize defines its size.The configuration parameter
ItemCachePreload enables a thread at server start up that fills the cache. |
| 98 | Performance measurement |
A performance logging has been added to several time critical sections. This is only active when the configuration parameter
UseProfiler is set to true. The results are printed by the logger. Logging can be activated with the parametersLoggerWriteStdOut and LoggerWriteToFile. |
| 129 | New server option: Increase size of metadata fields |
The default length of existing and new metadata fields is 255 characters. A new option in the system information dialogue allows for an increase. This option is not available if access is used as database system.
|
| 123 | New project option: Making group names optional in navigation tree |
There is a new project option to hide group names in navigation.
The option is accessible via project, administer.
|
| 85 | New column option: Show metadata in navigation |
The edit columns dialogue has a new feature: Show in navigation.
With this, the column data is shown in front of items in the navigation tree.
Only one column at a time can have this feature activated.
|
| 106 | Metadata ordering corrected |
Sometimes the metadata ordering was wrong when creating a new item.
|
| 122 | Error message while editing types |
Sometimes an
Index out of Bounds error message occurred while editing a type. |
| ID | Topic | Description |
|---|---|---|
| 31 | Direct editing of fixed metadata |
Columns with fixed metadata can be directly in item view edited.
Changes are saved immediately and without further prompting.
This feature can be activated by the user in the header of the item view using a button.
|
| 30 | Improved history of item and type data changes |
The history table for both items and types provides a detail view showing all data changes in a before/after comparison.
The details dialog can be accessed by clicking the button in the details column of the history table, or via the context menu, selecting the "History Details" option.
|
| ID | Topic | Description |
|---|---|---|
| 29 | Multiple users per alarm |
Only a single user was informed by an alarm up to now. From now on, several users can be selected to receive an alarm.
This change has the following implications:
|
| 2 | Additional module planning has been added |
A preliminary version of the new module planning has been added. A special license is needed to access it.
Further details will be included in the manual as soon as the new module is operational.
|
| 21 | Wrong metadata order solved |
Sometimes the ordering of metadata input field was wrong when creating new types.
|