Versions 1.29.x

In the equipment module, actions have been added that allow you to add devices/machines without having to go through the ordering and delivery acceptance procedure. This allows you to enter devices into the system directly from the desktop view and not necessarily using the delivery module.

The device rental management module has been expanded to include the possibility of additional system configuration in such a way that it performs both the functions of a module for managing small equipment that is rented from external suppliers and settled with them, but also as a module for managing equipment in industrial plants that have their own database of devices that require additional management.

Therefore, during implementation, we can decide to implement one of two module configuration variants:

Additional actions have been added to the Equipment Details View that allow you to request an inspection/check directly from the details view.

The ability to manage device rentals has been added to the desktop application view. This allows the person responsible for managing device rentals to request a device rental directly from the rental details view. Previously, this operation could only be performed by a given user from their own mobile view.

In the desktop view, it is now possible to order a given type of device from an external supplier. Previously, this operation could only be performed by a given user from their own mobile view.

Added the ability to close a rental of a given device in the desktop view without having to do it by the person who was the current renter. In the rental details view, additional actions have been added that will allow you to end the rental of a device.

For resources whose type does not have the 'is equipment' flag enabled, we do not allow orders to be fulfilled from an external supplier by the equipment module.

Added the ability to rent a device directly from the details view. Previously, this operation could only be performed by a given user from their own mobile view.

Additional context actions have been added between individual elements of the lease view, allowing you to switch between contexts and edit elements.

The Equipment module will not show additional information regarding work orders/contracts and cost assignment for these areas if the Work Order module is not implemented.

The type and resource importer has been expanded to include import of additional fields defining equipment devices. This includes information on the expiration date, people responsible for this process, owners, current lessors, and information on the end of the lease.

Attachment REST operations have been expanded to include the ability to import attachments to supervision history records. More details are available in the REST API documentation.

When reporting the history of a work order and selecting materials for expenditure, information about the current state of expenditure has been added. It appears both in the form for selecting materials from the material plan and in the form for creating expenditure. This allows the user to check whether a given material has already been expendited within the work order.

In the work order view for the mobile interface, the ability to search for work orders based on related items in delivery, order, warehouse or material plan documents has been added. This allows you to search for all orders that have documents with items with the specified type names.

When binding resources, it is no longer possible to bind a resource to itself. Previously, this was possible, which created a loop in the resource bindings and prevented their removal.

In the material plan view for work orders, a view summary has been added in the form of information about the value and quantity of plan elements.

In the lease details view, added information about the value of all lease plan items.

In the material plan view for leases, information about the price of individual plan elements has been added.

The lease view now allows you to store information about transportation costs and transportation values for individual construction elements/orders.

In the definition of the inspection round, the option of enabling the option of recalling the value of the last measurement for the inspection round has been added. After enabling it, during the inspection round, the value of the last measurement appears in the measurement field as a hint. The user can use it as a hint or enter their own value.

W przypadku zdarzeń serwisowych, które nie mogą być zrealizowane w danym momencie, istnieje możliwość oznaczenia ich jako odłożone. W takim przypadku zdarzenie nie jest usuwane z systemu, ale jest oznaczone jako odłożone i jest domyślnie ukrywane. W celu wyświetlenia takich zdarzeń serwisowych dostępny jest dodatkowy filtr, który pozwala na wyświetlenie tylko zdarzeń odłożonych.

When you postpone an event, you specify a date until which the event will be postponed and not visible in the default view.

During the inspection round, an additional action "Chart" has appeared in the menu of individual elements, which allows you to display a chart for the last measurements. The function is available only for measurements.

The service event details display a list of entries in each tab. This allows the user to quickly check which tabs contain entries.

The AMAGE Shell application has been expanded to include the ability to work offline. For instances with offline mode enabled, an additional Offline button appears in the user interface. The architecture allows for data synchronization on mobile devices and work without a network connection. The main mechanisms allow for data synchronization, logging in, and viewing basic offline mode functions. Successively, depending on the needs, additional functional areas working in offline mode will be added.

The AMAGE Shell application supports the work of maintenance systems in offline mode without access to the network. Synchronization of maintenance data allows data to be sent to the device and work without connecting to the network. After completing tasks and obtaining access to the network, the application sends all completed maintenance to the central system.

In the material plan of the work order, we can use the option Combine deliveries to also display elements that come from deliveries and were not defined in the material plan. This allows us to detect elements that are redundant with respect to the plan. Additionally, the column of material quantity from deliveries is highlighted when the quantity of material delivered is greater than the plan.

In production data, a record was added in the element events regarding the locking/unlocking of values. With each such operation, a record regarding the operation performed appears. Additionally, the way descriptive data is displayed in the event/history tables has been changed. Data is displayed in several lines, and the full text of the message is available in a tooltip available for a given cell.

When entering values in the production parameter editor, it is not possible to enter a value with greater precision than that specified in the parameter. Additionally, information about the maximum number of decimal places that can be entered appears as a hint.

Tabs with information about parameters and attachments have been added to the equipment details view.

The logic of handling a measurement that is unavailable has been changed. It is now possible to mark a measurement in an inspection round as unavailable even for measurements that are marked as required. This entry does not block the end of the round. However, such a status, i.e. measurement required but not performed, is displayed appropriately in the list of inspection round elements and in the analysis of the round performance.

For inspection rounds, the ability to display the history of entered data has been added. The history is available from the context menu of the inspection round during its execution in the mobile version (online) and in the inspection round view in the main view of the application.

The method of generating information on the status of an inspection round has been changed. Previously, data was generated on an ongoing basis, which caused a long waiting time for the information on the status of an inspection round to be displayed. Now, information on the status of an inspection round is saved in the database, which shortens the waiting time. Status data is saved when the inspection is completed.

The way information is handled and generated in the dashboard view of service requests has been changed. The mechanism always calculated MTBF statistics, even if they were excluded from the analysis. This caused delays in displaying the view for a large number of requests (several thousand).

Added the ability to export data from the warehouse view and warehouse item history to an XLS file. To generate the file, select the appropriate button in each view.

Due to the possibility of receiving information from the BAAN system both via SFTP systems and via email channel, the method of handling EDI integration with the ULMA IT system has been changed. Messages from these systems are correctly identified and processed regardless of the way files are encoded and marked.

The mechanism for integrating return documents in PERI CSV format has been improved. In the case of automatic resolution of the target account search, the system does not generate incorrect information about the required user response.

An additional configuration option has been introduced for the integration of delivery documents from ULMA. In the integration configuration, you can indicate which documents are to be treated as informational (i.e. not changing stock levels).

The mechanism for integrating warehouse documents from the Asseco Merit/Xpertis system has been modified to verify prices and quantities of previously imported documents during integration and update them in the event of a change. This is due to the possibility of changing prices in the Merit system during the financial circulation, e.g. updating prices only after receiving an invoice.

For the automation rules for changing the status of service events, the ability to assign an event to a person or people from the selected department and add a comment has been introduced in addition to the previously present event status change mechanism.

See more: Automation Definition

A new automaton (scheduler) has been added, which allows you to operate on events that have been postponed. This means that they are not visible in the notification view by default. The automaton allows you to specify the time at which it should operate in relation to the postponement date of the service event. Then, at the time of activation, it can automatically restore the notification to active and generate a reminder for people using notifications in the system or email. Details in the automaton configuration.

See more: Automation Definition

The mechanism for granting additional permissions and event views has been changed in the service module. An additional option has appeared in the context menu in the service event view, which allows access to the module configuration. In the module configuration, we can define and change the application behavior flags that have been moved from the system configuration section. Additionally, options have appeared that allow you to enable access restrictions. After enabling them, we can define lists of people who have access to service requests, which determines the visibility of these requests.

Changed the handling of offline device synchronization for the tour mechanism in case there are differences in the synchronized data and the data in the system. The change concerns the case when the mobile device sends the data of the performed tour for questions/measurements/tasks that have been deleted in the main system in the meantime. In such a case, this data will be ignored and will not be saved in the main system. This will allow the given tour to be saved in the main system and will skip the records from the mobile device that no longer exist in the main system. This applies to both questions/measurements/tasks and additional actions performed in the tour.

Added option to delete an inspection round regardless of its status. Previously, only inspection round sent to the central system could be deleted. Now it is possible to delete an inspection round that has not yet been sent to the central system. This option is available as an additional button at the bottom of the screen for performing an inspection round.

Offline inspection rounds have the same functionality as the online version. If the inspection round has the option of suggesting recently entered values enabled, the offline application also displays the recently entered values from the history of inspection rounds from the local data store. Thanks to this, the user has the option to select one of the proposed values, which significantly speeds up the data entry process.

Added the ability to display graphs from measurements of the last inspection rounds in the local data store. Graphs are available from the context menu of the individual measurement. The graph icon allows you to display measurements for a given inspection round that were recorded in local inspection round executions.

The offline version of the inspection rounds has been extended to include the ability to accept measurements marked as required when the answer is N/A. In such a case, after selecting the N/A answer, the measurement will be marked as completed, and after approving the inspection round, it will be counted as completed. The functionality is identical to the online version of the inspection rounds module.

In the offline version of the inspection rounds, the ability to display the last values of the entered round point has been added. Data comes from the local history of inspection round performance. Data is available for each type of inspection round element - question, measurement and task. The list displays the last values entered for a given round element. In the case of questions, answers to questions are displayed, for measurements - measurement values, and for tasks - task statuses.

Added additional REST API operations for resources. We have the ability to view, edit, and create new resources directly through the REST API.

For more information, see: API Assets.

Added the ability to specify additional file extensions that will be treated as a given file type. Depending on the file type, we can browse files internally using a text, image, multimedia, 3D model browser or use external browsers natively installed on a given device. Using the definition available in the settings, we can specify the type of data that each browser supports.

In the equipment view, the expiration/calibration and legalisation dates of devices are highlighted in yellow or red depending on the approaching date. If the due date is within 30 days, the date is highlighted in yellow, if the due date is exceeded, the date is highlighted in red.

Actions have been added to the equipment view that allow you to print and preview equipment identifier labels directly from this view.

An additional tab has appeared in the equipment detail views to display inspection plans for equipment. This tab allows you to display information about inspection plans, as well as add a new inspection plan for equipment or equipment item type.

The inspection template definition view has been modified to allow you to specify options for updating the calibration/legal date of the equipment after the inspection has been performed. This allows you to update all three expiration dates for the equipment.

Added option to delete local database. The option is available in the application settings menu in online mode. It allows to completely delete the local database in case the database contains errors that cannot be fixed by synchronization.

The AMAGE Starter helper application has gained the ability to force login via the AMAGE Auth server, i.e. via AD/Azure OAuth2 domain login or other OAuth2 providers for initial user authorization. This allows you to protect access to the application from unauthorized users. Only users who are authorized by the central authorization server will be allowed to the list of instances available at a given Client.

The position of the filter and scan buttons in the offline view of the tour has been changed to make the most of the available screen by allocating it to the list of items.

New versions of Mikrotik’s Bluetooth beacon firmware (since version 2.40) have changed the data transfer format, which is compatible with what is sent in the notification area (advertising). The way of handling has been changed to enable support for the new data format and maintain compatibility with previous versions of the beacon.

Additional options have been added to the equipment module, allowing for local recording of inspection, calibration and legalization history. A simplified method allows for recording information about completed activities directly in the module, without the need to implement integration with the Inspection module. This makes it easier to maintain history for cases that do not require advanced capabilities of the inspection module.

The ability to selectively edit entered measurements for already completed inspection rounds has been added. In the event of an incorrect recording of a given parameter, we can edit its value in the main system interface. This is done using options from the new context menu available for the general view and measurements. After saving a change to the parameter value, the history of this change will be saved, which will allow tracking changes in the parameter value over time.

After a change is made, the parameter value in a given inspection round additionally has an icon indicating that a modification of that value has been made.

The context menu also provides an option to display the parameter edit history, which allows you to clearly identify the time and author of the change.

Due to the introduction of additional actions and functions for individual entries of an inspection round or inspection, the available actions have been moved to the context menu. The previously available buttons History, Chart and Resource have been moved to the context menu of the element, which allows for adding other functions in this area.

The equipment module has been extended with additional functionality, identical to that recently introduced to the service events module, which allows you to specify the visibility of equipment records depending on the granted permissions. The dialog is available in the equipment view in the context menu.

Using this window we can enable the activity of these restrictions and select people who are placed in three groups:

Additional logging of transmissions between offline devices and the main system has been implemented. All records transferred from the mobile system to the main system are saved in logs, which allows tracking of transferred data and identification of events and data transferred from offline mode.

The Equipment module has been expanded with new functionalities and data, allowing for the recording of history and data concerning performed tests (legalization, calibration) directly in the module. The interface has been changed and the functionality has been expanded. Additionally, the possibility of direct integration with the inspection/inspection plan and service notification modules has been left.

The changes include: - adding new fields to the equipment (e.g. calibration name, internal verification, external verification, calibration certificate, legalization certificate, type of metrological supervision, date of the last metrological examination, frequency of metrological supervision, date of the next metrological examination), - adding new tabs to the equipment (e.g. study notes, additional dates, responsible, history), - adding new buttons to the equipment allowing editing of schedules and events - adding new views to the equipment (e.g. calendar, details, history), - adding new fields to schedules (e.g. planned date, execution date, status), - adding new buttons to schedules allowing editing of schedules and events

A calendar view has been added to the equipment view, allowing you to view the equipment inspection schedule. The calendar shows all history records for the equipment, i.e. calibrations, legalizations and internal checks. Additionally, information about planned dates for checking the above tests is also displayed.

The equipment inspection reminder machine has been expanded. From now on, we can specify which date (legalization, calibration, internal inspection) is to be taken into account in the event of an equipment inspection reminder. Additionally, people who are the owners or responsible for the equipment can be included in the email notification.

More: Equipment Validity Reminder

The equipment importer has been expanded/updated to include the ability to import new fields resulting from changes to the equipment module structure. All additional fields available in the equipment module are now available in the import sheet.

Additionally, the ability to import a resource’s state has been added to the import of its resource.

The ability to import equipment history records from external files has been added to the system. Using the fields in the sheet, we can specify the resource/equipment to which the history applies and import all necessary information.

Resources have the ability to specify a state that is displayed in the main resource lists/trees. Added the ability to display and change the state directly from the resource details view. A bar with all available states appears at the top of the window with appropriate coloring of the information contained there.

In the inspection round, when editing an existing inspection round, the possibility of controlled removal of a inspection round element has been added. In the case when a inspection round element was never saved during the inspection round execution, the given definition can be removed without consequences. However, if a inspection round element was saved during any of inspection round executions, the user will be informed about it and will be able to remove the inspection round element, remove inspection round records of this element or cancel the operation.

If an element is removed from the inspection round definition, but the inspection round records of this element are left, the user will receive information that the element has been removed from the inspection round definition, but the inspection round records of this element remain in the system. This is visible in the inspection round execution view, where the description of a given element has a red background and is located at the end of the inspection round list.

The ability to filter the calendar view by completed/planned inspection rounds has been added to the inspection rounds module. Two additional options have appeared in the filter bar: Show planned and Show completed. By default, both options are displayed.

When trying to log out, the system checks if there are any active inspection rounds for the user. If so, a message is displayed informing about this. The user can return to the application and end the active inspection rounds or log out of the application.

If the user disables the location service on their mobile device, they will not be able to start an inspection round that includes beacon identification tasks in its path. A message will appear informing them about this.

If you attempt to end an inspection round, the user will be presented with a dialog box confirming that the inspection round can been closed.

In the calendar view, the ability to show the real time of the inspection round in the timeline has been added. To enable this function, select the appropriate option in the calendar filter settings, i.e. the 'Real time' option. By default, it is disabled.

In the inspection round execution list, additional icons have been added to indicate the occurrence of comments/attachments/notes recorded during the inspection round execution. Depending on the occurrence:

The action of editing values already introduced in the inspection round has been expanded. The action Edit value has been renamed to Edit/Confirm value and for tasks such as scanning identifiers it will be possible to confirm the execution of a tag/beacon scan in the inspection round after it has been executed.

The ability to display the last inspection rounds of a given person has been added to the mobile application. After selecting the Hourglass button in the upper right corner of the screen, the user will be presented with a list of the last inspection rounds of a given person. The user can return to performing a given inspection round. Saving the execution will also change the end date of the round!

In mobile executions, the ability to display already performed inspection rounds has been added. The user can start editing them and save changes. This also allows the ability to add an attachment/action to an already executed inspection round.

Added the ability to add an attachment/action to an already closed inspection round. After entering the inspection round, in the "Notes" or "Actions" tab, the attachment editing buttons do not disappear. This function disappears when the inspection round is sent to the central system.

The way buttons are presented in a yes/no question during its reporting has been changed. Button colors are activated only after the appropriate option is selected. By default, the buttons are gray.

Slightly changed the offline comment window for completing the inspection rounds. The comment window now scales correctly when the large virtual keyboard is enabled, which can cover the text window for smaller screen sizes.

Information about the logged-in person has been added to the mobile view. It is available in the Tools menu. After displaying the menu, information about the logged-in person is displayed at the top of the screen.

The notification module has been expanded to include the ability to manually create notifications for any number of users. Up until now, the function was mainly used in the system to create automatic notifications about events generated automatically, i.e. reminders, integration information, etc. Now, using an additional action, we can create a notification with the option of selecting users or departments to which a given message should be sent.

More: Notifications Documentation

Added ability to display notifications in the system in full screen mode. Instead of in the notification bar and the bell button, these notifications appear in full screen and the user has to review all notifications waiting for him.

In the AMAGE Shell application, in the Current Controls module, the ability to add an attachment to a comment to a current control point has been added. The context menu for adding a comment has been expanded to include the ability to add an attachment to an existing note option. After selecting this action, a new window is displayed, which allows you to enter a comment and attach any number of attachments.

This data is synchronized to the central system from offline work and available in the tour execution overview.

In the AMAGE Shell application, the module Inspection Round and offline work, the ability to attach attachments has been added when registering additional actions/activities during the inspection round. The interface has been changed so that it can be done in one step by selecting an action, adding a comment, and adding attachments.

Data is synchronized with the central system.

In the mobile application (online part) the ability to add an attachment/s to an inspection round point has been added. This is enabled by an additional icon in the context menu of a given inspection round point.

Attached attachments are visible in the inspection round execution preview in the main system.

In the structure and supervision resource view, the ability to filter by manufacturer and contractor has been added.

In tree views (Location, Groups, Departments) an additional question has been added during the drag and drop operation. The question allows you to interrupt the element transfer in case of an incorrect selection. Additionally, the operation has been secured against moving the element onto itself.

Added the ability to import the Manufacturer field to resources. Additionally, added the ability to specify the manufacturer field as a resource uniqueness search field to detect resource updates.

Importers have been extended to include the ability to import an inspection round template (inspection round points) from XLSX/CSV sources. Using this mechanism, you can quickly import inspection round points and additionally create resources/locations accompanying inspection round points.

The table view of the inspection round has changed the way fields with the result of a given point are highlighted. If the question/measurement definition contains information about the correct answer, the field will be colored green (correct answer) or red (incorrect answer). In the absence of information about the correct answer, the field will not be highlighted.

The view of the inspection round has been unified to the offline view on mobile devices. A YES/NO question will color the buttons only when they are selected. The color will correspond to the correctness of the answer.

A button to access process automation actions has been added to the template and inspection plan views, just like in the inspection execution view.

An additional field explaining the inspection round point has been added. If completed, it will be displayed during the inspection round as an additional description field in the inspection round point context menu instead of the general description of the question/measurement template.

An additional check has been added when adding a resource. If a resource has a specific type and serial number, before adding it, we check if a resource with the same type and serial number already exists in the database. If so, the resource will not be added.

Mobile devices that do not have a current token that they receive during pairing in the system will be asked to re-pair with the system. The message will appear when trying to load a given instance on a mobile device that does not have a current token.

In the definition of the inspection round point, the possibility of defining a verification condition for a selected measurement has been added. It is treated as superior if the measurement definition itself has one. This allows for quick introduction of a measurement verification condition, e.g. whether it is within the measurement range.

In the Orders for dangerous work module, the mechanism for defining the conditions for starting work has been expanded. Additional dictionary data has been added, which allows for creating a list of elements required to prepare the work site, defining the parameters for starting the device (replacing the inactive LOTO module) and defining the tools and activities required to perform the work.

Through the new transport module we have the ability to group deliveries into transport packages and monitor their execution/implementation.

The transport module allows you to monitor and manage transports that include multiple deliveries. It allows you to define transport routes and paths, which allows you to effectively plan and optimize transport processes. With the transport monitor, you can track the status of transports, manage deliveries, and analyze transport data.

The new transport module allows you to monitor transport data. Transport contains information from the related Supply module or can have information about transported materials on its own. This allows you to track information about transports, customers, routes and the implementation of transport stages.

The Delivery and Transport modules (new module) have a link that allows for the definition of a transport that combines multiple deliveries. Using this link, we can track the number of transports carried out within a given project and monitor their status.

The transport module has an additional view in the mobile version, which allows you to track and manage transport statuses. Using the visual representation of transports and transport stages, you can easily manage transports and their statuses. The interface is adapted to mobile screens.

The EDI integration with PERI (leases) has been expanded with a new data format sent by this formwork supplier. The format supports multiple objects/components sent in one delivery document as well as transport elements. With the new Transport module, this enables additional tracking of transports of multiple deliveries simultaneously. The new format is supported in parallel to the old format to ensure maximum compatibility with the integrated documents.

For the integration of leased elements with the Palisander company, support for documents sent periodically by this formwork manufacturer has been added. The document contains information about the generated documents. The system automatically checks the completeness of documents in the system and creates a notification for administrators when it detects inconsistencies. This facilitates possible diagnostics of documents that have not been sent or have not been correctly registered in the system.

The attachment importer has been expanded to include the ability to import attachments to the history of resource equipment. This allows for mass import of documents confirming the validation of a given equipment, e.g. certificates, attestations, test results.

An additional type of authorization has been added for the inspection module, which allows for the execution/visibility of inspections assigned only to themselves. This action is active only in the mobile section of the system. It allows for the definition of authorizations so that the user who will log into the system, e.g. a subcontractor company, will have access only to inspections that have been assigned to them.

An action has been added directly from the resource or type view, which allows you to create an inspection plan for selected items from the list. This allows you to quickly define inspection plans (schedule) in addition to the actions already available, which allow you to order immediate execution of inspections for selected items.

An additional action has been added that allows you to reassign the inspection execution to another user without having to modify other parameters and data.

Added the ability to copy an inspection round to a new one with a full list of items. This allows for quick copying of the inspection round and, for example, the ability to split the tour into smaller inspection rounds.

The internal method of recording data in the supervision module has been changed. The operation concerns the database structure and is intended to simplify connections between objects and facilitate changes and adjustments to the system in the event of changes in resource parameters, e.g. their type. The system will automatically convert all information to the new format. Full documentation of changes is available in the database documentation (on request).

Extended and added additional REST API operations for orders. We have the ability to view, work orders directly through the REST API interface.

For more information, see: Work Orders API.

Extended and added additional REST API operations for supervision operations. We have the ability to browse supervisions directly via the REST API and create/delete operations for individual supervised elements.

For more information, see: Supervision API.

W trybie online dla wykonywanych obchodów dodano przycisk umożliwiający usunięcie obchodu, który jest aktualne wykonywany. Opcja ta jest możliwa, tylko dla obchodów, które nie są jeszcze zakończone.

W przypadku zakończonych obchodu pojawia się komunikat informujący o tym, że nie można usunąć zakończonego obchodu. W przypadku otwartego obchodu, po kliknięciu przycisku, użytkownik zostanie poproszony o potwierdzenie usunięcia obchodu. Po potwierdzeniu obchód zostanie usunięty z systemu.

W aplikacji AMAGE Shell Electron dodano opcję konfiguracji umożliwiającą określenie źródłowego systemu AMAGE, do którego ma podłączyć się dana aplikacja. Możemy wybrać z ogólnej instancji systemów AMAGE24 lub wpisać dowolny adres własnej instancji systemu.

Aplikacja AMAGE Shell Electron pamięta rozmiar i pozycję okna. Przy kolejnym uruchomieniu zostanie umieszczona dokładnie w tym samym miejscu ekranu.

W konfiguracji aplikacji AMAGE Shell Electron dodano możliwość identyfikacji typu aplikacji. Za jego pomocą możemy przesłać do systemu AMAGE informację o typie urządzenia. W takim przypadku możemy wymusić włączenie określonego interfejsu aplikacji od razu po zalogowaniu. Ułatwia to np. włączenie trybu mobilnego na komputerach stacjonarnych lub wizualizacji dashboardów w trybie pełnego ekranu.

Dodano w raporcie poleceń na prace niebezpieczne rozszerzenie o możliwość wyświetlania reguł bezpieczeństwa w formie list, które zostały wybrane w edytorze.

Do aplikacji Electron (aplikacja na komputery Desktop) dodano możliwość uruchamiania aplikacji razem z systemem operacyjnym. Opcja ta dostępna jest w ustawieniach aplikacji. Po jej włączeniu aplikacja uruchomi się automatycznie po zalogowaniu do systemu operacyjnego. Kompatybilna z systemami rodziny Microsoft Windows oraz Linux.

Aplikacja AMAGE Shell Electron (wersja na komputery Windows/Linux) została uzupełniona o dodatkowe funkcje, które pozwalają aplikacji Web na wywołanie określonych czynności bezpośrednio z uruchomionej aplikacji Electron. Funkcje te są dostępne w obiekcie window.electron i są następujące:

Funkcje te są szczególnie przydatne, gdy aplikacja pracuje w trybie kiosku (pełny ekran, bez elementów sterujących). Aplikacje AMAGE Software suite zostaną rozbudowane o opcje umożliwiające wywoływanie tych funkcji.

Dodano dodatkową obsługę przypadków błędnej konfiguracji lub braku połączenia z docelową stroną internetową. W przypadku, gdy istnieje problem z ładowaniem docelowej strony internetowej lub jesteśmy w trakcie początkowego ładowania strony, to wyświetlane jest animowane tło w głównym widoku. Tło sygnalizuje poprawne działanie aplikacji.

Dodatkowo okno zawiera dwa przyciski:

Ułatwia to zarządzanie i konfigurację aplikacji w przypadku, gdy ustawimy pracę aplikacji jako kiosk - w pełnym ekranie, bez menu głównego i dekoracji okna. W takim przypadku nie ma możliwości zamknięcia aplikacji, a jedynie wyjście z aplikacji przez menedżera zadań systemu Windows/Linux.