Solution enhancements - HxGN EAM - 12.1 - Release Notes/Bulletin

The following is a list of enhancements that are included with this release of EAM:

Module	Product Enhancements
Administration	Several new options were added to the Documents record view; supporting the ability for a user to lock a document to prevent the associated document file from being updated by other users (i.e. only the user who has locked a document may either upload a document file, or may unlock the document). In addition to the Lock Document and Unlock Document buttons; the system administrator may configure the Break Document Lock button (delivered as hidden) to provide the ability for a document lock to be removed by a user other than the user who holds the lock.
Administration	A new tab was added to the Documents screen to display the historical record of uploaded document files. The tab displays a list of files uploaded for the document record prior to the current document file; as attributes of the document record as they were at the time the file was uploaded. The tab supports viewing of previous document files; as well as the ability to revert to a previous document file, which replaces the current file with a prior file version.
Administration	For Mobile (Transit) users, The Token End Point Mobile field will be used in association with QR Code generation. By using this field (and not the ROPC Token End Point field), segregation between the Authorization Code grant flow and ROPC grant flow can be maintained.
Administration	The DFSCID install parameter will store the ClientID for the HXGN-DFS Partner to support usage of web services by the Dataflow Studio utility. EAM will harvest this value to enforce security of these web services.
Administration	A new system user, DFSINTERNALUSER, has been created to support the implementation of the Dataflow Studio utility to EAM for integration purposes.
Administration	If the Logout URL field on the SSO Configuration screen is blank, the sso logout (LGNEAM=EXTERN) will redirect the user to the logout URL configured in the config.yml file. If the Logout URL field is filled in with a valid value, the sso logout (LGNEAM=EXTERN) will redirect the user to the URL specified in the Logout URL field.
Administration	The ability to use custom fields for searching (i.e. in either the dataspy, and/or quick filter) was added to this tab.
Administration	EAM Mobile Offline - License is not required for EAM Mobile Offline if the user has the Digital Work app field populated at the user setup with 'Advanced Mobile', as this is a separate license that includes EAM Mobile Offline.
Administration	MS Project Interface - A Security Token header will be added to the communication of data to EAM to further secure the information being exchanged. This removes the requirement for the user to be designated as a connector in EAM.
Administration	View Log Files - Added the ability to sort the list by clicking the column header.
Administration	Reports - All Hexagon delivered reports are Basic reports and will not consume a Report Consumer seat. Additionally, any user not marked as a Consumer will be able to run any Hexagon EAM delivered report. Custom created reports will require and consume a Consumer Report license seat.
Administration	The system was updated to provide support for Hexagon Cloud environments configured with Amazon S3 storage to have thumbnail images automatically generated for several common file types, when a documents of these types are uploaded and no user-defined thumbnail has been specified. Unless a user-specified thumbnail is provided by the user when a file is uploaded, thumbnails will now be automatically generated when Amazon S3 storage is used for the following file types: .jpg, .png, .pdf, .ppt, and *.pptx. Automatic thumbnail generation does not occur for Infor Cloud environments or on-prem installations of HxGN EAM. Customers with Infor Cloud or on-prem environments should continue to upload user-specified thumbnails when uploading documents.
Administration	A sidebar was added to the system to support the ability for a user to view a list of documents related to the selected header record, as well as the total count of all documents directly associated to the selected header record. The list displays thumbnails of each document, and provides the user the ability to either view or download the document file without leaving the screen.
Administration	Base - Stylesheet additions (theme-hex and theme-hex-dark) have been added to support Hexagon color themes throughout EAM.
Administration	All documentation, including the HxGN EAM Help resources, will be made available on the Hexagon PPM documentation site (https://docs.hexagonppm.com) starting with the HxGN EAM 12.0 release. The URL to which all Help entry points in the system are directed has now been updated to reflect this change.
Administration	With the introduction of the SSO Configuration screen in EAM, customers can integrate their IDP with Ping Federate. Additionally, external customer contractors may need to access EAM without usage of SSO.To prevent environment or usage issues, the authenticationmode parameter can be passed in the URL of the login screen. Usage of an authenticationmode parameter value of internal will ensure the user can login to EAM as is the standard system behavior when the install parameter LGNEAM is set to STD. If authenticationmode is specified in the URL, it will override the setting of the install parameter LGNEAM. Note, upon logout, the user will be navigated to the login screen with the parameter authenticationmode=internal set in the URL.
Administration	Added a Type field to the Menu Structure and Permissions screen allowing users to easily differentiate the screens/tabs/permissions associated with Digital Work, Mobile Offline, and Base elements.
Administration	All .NET applications including the HxGN EAM Import Utility, HxGN EAM Upload Utility and the HxGN EAM Add-In for ArcGIS Pro were updated to support API Key authentication.
Administration	API Key Management \| Integration Configuration - This tab will assist administrators in creating and managing API Keys for users against various integration partners in an organized fashion. Organizing EAM API Key users against different applications assists in creating and/or revoking API keys for an EAM user for one integration, while continuing to support a different API key for that user for another. To support backwards compatibility, the Revoke API web service the warning message will not show by default. The client will to have to call MP6585_RevokeAPIKey_001 with revoke_warning =prompt to use this feature.
Approval Workflow	Workflow Approval \| All Supported Screens - Workflow Approval screen is where users can review a workflow event that has been assigned to them to ultimately approve or reject the request. A workflow event is created when an active Approval Workflow Setup record exists and a source record's activation status and activation conditions are met. When multiple approvers are designated to a workflow event, this screen will show all of eligible approvers and their current status. There is a standalone Workflow Approval screen that will show workflow events across all supported screens. Additionally, there is a tabbed version on the Work Orders, Requisitions, Purchase Orders, and Case Management screens. This tabbed version will show the most recently created workflow event for the header record. This feature is only available for HxGN EAM Smart Cloud and On Premise deployments. For full details of this module, see the HxGN EAM Approval Workflows feature brief.
Approval Workflow	Approval Workflow Setup - Approval Workflows systematically routes a record in HxGN EAM to a specific user, or group of users, for review. An administrator can configure the criteria for when a source record should undergo an approval workflow and for whom should be responsible for reviewing and approving (or rejecting) the request. Once an Approval Workflow Setup record is made active, HxGN EAM will begin monitoring records specified against the entity to automatically create and systematically route the workflow events to the appropriate individual(s) for review. Approval Workflows are supported by the Work Orders, Requisitions, Purchase Orders, and Case Management entities. This feature is only available for HxGN EAM Smart Cloud and On Premise deployments. For full details of this module, see the HxGN EAM Approval Workflows feature brief.
Checklists	Task Plans \| Checklist - Changed how the system handles translations for newly created checklist items. New items will only get one translation record for the default language of the system (the DEFLANG install parameter), instead of creating one translation record for each installed language. If translations are required, these can now be added manually on an as-needed basis. This enhancement was done to prevent adding an abundance of translation records to the database, that are often not even translated, meaning the original description and the translation are the same. This enhancement only applies to checklist items. None of the other entities were changed at this time.
Customer Contracts	Customer Contracts - Contract items associated with the contract will now be flagged to use a fixed exchange rate and have the exchange rate set if you select to use fixed exchange rates on the Record View of the contract. And vice versa if you select to not use fixed exchange rates, both field on the contract items will be cleared.
Data Lake	The DLVWCR job (for Datalake) will check if partner tables can be truncated. This verification will be done when all records in a partner table have been processed (i.e., column lastupdatedat of table datalake_table equals the maximum value of column dl_lastsaved of the partner table).
Dynamic Checklist	Task Plans \| Dynamic Checklist Conditions - Added a new tab where you can define a condition that must be met before one or more dynamic checklist items will be displayed. With this new feature, you can ask for the pressure in a tank, but only if the pressure gauge indicates it is in the red. In other words, do not show the pressure question if the gauge is in the green or the answer has not been provided yet. On this tab, you first select a checklist item from the list of checklist items attached to the task plan already. Once selected the system will, depending on the type of item, show the appropriate checkboxes and or fields relevant to define the condition for that item. For example, you may see the Yes and No checkbox, the Good and Poor checkbox, the Finding field, the Severity field, or the Value field. The condition for a nonconformity measurement may have (1) Nonconformity selected, (2) a Severity of High, and (3) a measurement Value greater than 5. Or the condition for an inspection may have (1) a Finding of Bad, and (3) a Value between 10 and 20. This tab is not available on the Job Plans screen.
Dynamic Checklist	Equipment (A/P/S/L) \| Checklists - Added a new check box called Conditional. This checkbox is related to the new Dynamic Checklist functionality. If unselected, the checklist item was either not conditional or the item was conditional and the condition for it to be displayed was met. Otherwise, if selected, the checklist item was conditional and the condition for displaying it was not met. Note that these checklist items may still show an entered result. This is because the user may have answered the triggering checklist item such that the condition was met. The system then showed this dynamic checklist item (Conditional is set to unselected), and the user entered a result. Then the user changed the result on the triggering checklist item so that the condition was not met anymore. The dynamic checklist item will then be hidden again (Conditional is set to selected), but the system will not clear any entered results on this item. The pre-delivered Dataspy is adjusted to only select the items where Conditional is unselected. This checkbox was also added to the checklist popup on the Work Order Checklist tab, and Operator Checklist tab on the equipment screens, and the Review Operator Checklist screen.
Dynamic Checklist	Work Orders \| Checklist - Added the new Dynamic Checklist functionality. The system will only show the checklist items that are not conditional and will show all conditional items for which the condition was met. Once a checklist item is answered and you click save, it may trigger other items to show now if a condition was attached to the answered item and the answer met the condition. For example, ask for the pressure in a tank, but only if the pressure gauge indicates it is in the red. If you answered Yes, the gauge is in the red, and you click save, then the checklist item about the pressure will show. This checklist item may disappear again if you change your answer about the gauge in the red to no. Note that when a checklist item is removed from the list because the condition is not met, the system will not clear the answer on this removed line, it will only hide it. The same functionality was added to the Operator Checklist screen and the Checklist tabs of the Case Management, the Nonconformities, and the Permit to Work screen.
Dynamic Checklist	Task Plans \| Dynamic Checklist - Added a new tab where you can define which checklist items should be displayed when a condition associated with another checklist item is met. With this new feature, you can ask for the pressure in a tank, but only if the pressure gauge indicates it is in the red. In other words, do not bother showing and asking the pressure question if the gauge is in the green. On this tab, you first select a dynamic checklist condition and then one or more dynamic checklist items that depend on the selected condition. Once this setup is complete, dynamic checklist items will be hidden on the Operator Checklist screen and the Checklist tabs of the Work Orders, the Case Management, the Nonconformities, and the Permit to Work screen, until the checklist item to which the condition is associated is answered and the provided answer meets the condition, at which time the dynamic checklist items will be unhidden. This tab is not available on the Job Plans screen.
Equipment	Sensor - The intention of this screen is to be able to enter and track IoT devices (sensors) from the Equipment perspective. This would allow the user to monitor environments or specific assets based on the sensor associated with an area of assets or directly to an asset. This is not fully functional in this release, but as a start to allow for further IoT usage within EAM.
GIS	HxGN EAM 12.1 will support ESRI's ArcGIS Enterprise v11.1. See the HxGN EAM Product Family Software Requirements for more details.
GIS	The scheduled task for the 'autosync' process that is generated by the HxGN EAM Add-In for ArcGIS Pro was updated such that all GIS map layers that are configured for synchronization are handled in one, single autosync task. This is a change from the previous behavior, in which autosync tasks were generated separately for each layer individually.
GIS	The scheduled task for the 'autosync' process that is generated by the HxGN EAM Add-In for ArcGIS Pro was updated such that scheduled synchronization of secured ArcGIS Online hosted feature layers is supported.
GIS	Support was added to the GIS Map Search screen, the GIS WO Dispatch screen and all map-based popups, lookups and dropdowns in the system to support display and interacting with ArcGIS Online hosted content; such as ArcGIS Online hosted feature layers. Users will now be able to specify a portal Item ID for an ArcGIS Online hosted feature layer as a valid value for the GISSERV install parameter, as an alternative to an ArcGIS Server-hosted map service URL.
GIS	The HxGN EAM Add-In for ArcGIS Pro was updated to support the ability for a user to both export and import a list of previously-defined field mappings between GIS and EAM equipment attributes. This enhancement allows users of the HxGN EAM Add-In for ArcGIS Pro to more quickly and easily configure mapped fields, especially for scenarios when the similar fieldnames are used repeatedly in multiple GIS layers.
GIS	The scheduled task for the 'autosync' process that is generated by the HxGN EAM Add-In for ArcGIS Pro was updated such that synchronization of map layers that have a layer name specified differently than the corresponding table in the geodatabase are now supported (i.e. layer is named as "GrateInlet" on a map within an ArcGIS Pro project; but the supporting table for the layer exists as "GISDB1.DBO.GrateInlet" in the geodatabase).
GIS	Ahead of Esri's retirement of ArcGIS API for JavaScript 3.x in July 2024; all map-based screens and popups in the system have been updated to support the newer ArcGIS Maps SDK for Javascript 4.x. No changes or differences in setup/configuration of map-based screens will be required from HxGN EAM users to support this change, in comparison to past releases.
Overview 360	Equipment Overview 360 - Added a new widget called Custom URL. This widget lets you select any URL that is configured as a custom tab of Type HTML on any of the EAM screens. See the Custom Tabs tab on the Screens screen. The widget supports using the following parameters in the URL: (1) equipmentno and (2) organization. With these, the widget becomes equipment sensitive, providing the URL supports this. The widget also has support for the DEPLOY_OCADSVG.jsp and DEPLOY_OCADBIM.jsp from OpenCAD.
Permit to Work	Work Orders \| Plan Tools - When a tool is added on this tab and a safety record is found in the Safety Matrix for this tool and for the equipment of the work order, the system will add this safety record to the Safety tab of the work order. Nothing will happen when the planned tool is removed. The same functionality was added to the Schedule Tools tab of the Work orders screen.
Permit to Work	Permit to Work \| Safety \| Remove Duplicates - Added a new button that will remove duplicate combinations of the same hazard, precaution, and timing. The system will preserve the combination with the most recent hazard and precaution revisions and with the most recent date updated or created. The system will also preserve unique comments and documents from deleted duplicates and save them on the preserved safety record. Additionally, two new fields, Safety Matrix Type and Safety Matrix Code, were added to make it easier to identify the source on the safety record. These two fields were also added to the Safety tab of the Work Orders screen.
Permit to Work	Permit to Work \| Tools - Added a new Tools tab where required tools can be selected and added to the permit to work. Any hazards and precautions associated with this tool in the Safety Matrix may also be added to the permit to work if the Equipment, Category, or Class from the Safety Matrix matches the permit to work header data. This tab allows the same tool to be selected more than once. Tool records may also be created automatically from the new Safety Scope tab of the permit to work. If the tool record is created automatically from this tab, then duplicates can be prevented based on the setting of Organization Option PTWTLDUP.
Permit to Work	Permit to Work \| Safety Scope - Added a new Safety Scope tab where typical work order content can be selected and added to the permit to work. This content can be a PM Schedule, a Standard WO, a Task Plan, or a Job Plan. You can select multiple of each and in any combination, as required. By selecting this content, you indirectly select related safety records and tool records. And by adding tools, any tool related safety records are also added to the permit to work. Without an actual work order this will allow you to quickly specify what kind of work is needed and what the hazards and related precautions are. Or alternatively, if there is a work order out there already, you can use the Import from Work Order button on this tab. Once you select the work order and click submit on the popup, the system will load the Safety Scope tab, the Safety tab, and the Tools tab on the permit to work with data from the imported work order. Note that this Safety Scope tab, and the Tools tab, will also be populated from the Permits tab of the Work Orders screen when you click Create PTW.
Permit to Work	Safety Matrix - Added a Tool field in the Activity Details section. With this enhancement, tools can now also be associated with hazards and precautions.
Permit to Work	Permit to Work \| Copy/Replace PTW - Added a Safety Scope and a Tools checkbox to the popup. If selected, the new safety scope and tool records associated with the permit to work will be included in the copy and replace process.
Voice of the Customer	Screen Designer for Digital Work - A new Save Layout button has been added to this screen to replace the save toolbar button. The Copy from Group field has been moved to the top of the screen for easy usability
Voice of the Customer	Screen Designer for Digital Work - Changes have been made to this screen, so that the user can now save the layout to multiple user groups at the same time, using the Available Group(s) & Save to Group(s) list boxes.
Voice of the Customer	Work Orders - Added the ability to update the Standard WO field of a work order that was created as a follow-up from a checklist. The originating checklist line references the follow-up work order and the follow-up activity that was created for this checklist line. This follow-up activity reference is what disallowed the update in the previous versions. This constraint has been removed and once the new Standard WO is selected and saved, the system will remove the follow-up activity reference from the originating checklist line, only leaving the reference to the follow-up work order.
Voice of the Customer	Login - When a user resets their password via the Password Reset option, the system, the system will also unlock the user if the user is locked.
Voice of the Customer	Alert Management - Added a History Retention (Months) field, which controls the number of months alert history records are kept. A job called Alert Management History Cleanup, will delete the history records older than the setting of History Retention (Months). This job can be started on the Job Setup screen. Alerts where this field is blank are not affected.
Voice of the Customer	Work Orders \| Checklist \| Reviewed By - As part of the checklist review process and depending on the setting on the Nonconformities Setup screen, the system may create nonconformities based on the entered checklist results. An integral part of this process is the creation of the observation. When the observations are created, the system will now also copy the documents associated with the source checklist item to the nonconformity observation. A picture is worth a thousand words!
Voice of the Customer	Work Orders \| Checklist - Added a new dropdown called Follow-up Group. With a Follow-up Group entered, all checklist items that require mechanical follow-up are grouped together in one work order and are separated from those that require electrical follow-up, for example, if you click the Create Follow-up WO button. Create follow-up groups on the System Codes screen by selecting Setup Codes and then Entity Checklist Follow-up Groups (CFUG). Note that there are two different System Codes for this entity: (1) Group follow-up work orders (GR) and (2) Individual follow-up work orders (IN). If you use a group code, the system will create one follow-up work order for all checklist items that require follow-up and that have the same group. This work order will have as many activities as there are checklist items with that group. If you use an individual code instead, the system will create one follow-up work order for each checklist item that requires follow-up. This work order will only have one activity created from the checklist item. On this tab, your group is prepopulated based on the selections made on the Checklist tab of the Task Plans or Job Plans screen. But you can overwrite it here. Also added a Standard WO, although not visible in the grid. This Standard WO must be prepopulated on the Checklist tab of the Task Plans or Job Plans screen and will be used here to create one follow-up work order for the checklist item based on this Standard WO. The same functionality was added to the Operator Checklist and the Review Operator Checklist screens. The Follow-up Group field was also added to the Checklist tab of the equipment screens, and the created follow-up work order will have a new field called Originating Follow-up Group populated.
Voice of the Customer	Task Plans \| Checklist - Added a new dropdown called Follow-up Group. With a Follow-up Group, all checklist items that require mechanical follow-up are grouped together in one work order and are separated from those that require electrical follow-up, for example. Create follow-up groups on the System Codes screen by selecting Setup Codes and then Entity Checklist Follow-up Groups (CFUG). Note that there are two different System Codes for this entity: (1) Group follow-up work orders (GR) and (2) Individual follow-up work orders (IN). If you use a group code, the system will create one follow-up work order for all checklist items that require follow-up and that have the same group. This work order will have as many activities as there are checklist items with that group. If you use an individual code instead, the system will create one follow-up work order for each checklist item that requires follow-up. This work order will only have one activity created from the checklist item. On this tab, your group selection is the default setting for the checklist item. But you can still overwrite this on the actual checklist on the Work Orders screen or the Operator Checklist and the Review Operator Checklist screen. Also added a Standard WO lookup. This Standard WO is also used to create a follow-up work order. The Follow-up Group is not used in that case. Checklist items where Follow-up is selected, and that reference a Standard WO, will always create one follow-up work order which will be based on the Standard WO. Note that, unlike the Follow-up Group, the Standard WO cannot be overwritten on the actual checklist on the Work Orders screen or the Operator Checklist and the Review Operator Checklist screen. Both fields were also added to the Checklist tab of the Job Plans screen.
Voice of the Customer	Work Orders \| Checklist - Added a new checkbox called Defer Follow-up. If selected and you click the Create Follow-up WO button, the follow-up of the checklist item will become deferred maintenance instead of a follow-up work order. This checkbox is only relevant if the organization options are set to create follow-up work orders. If the options are set to create deferred maintenance records, i.e., the Create Deferred Maintenance button is the only option displayed on the screen, then the value of this checkbox is ignored, and the system will always create deferred maintenance records only. The checkbox was also added to the Operator Checklist screen, the Review Operator Checklist screen, and the Checklist tab of the equipment screens.
Voice of the Customer	Task Plans \| Checklist - Added a new checkbox called Defer Follow-up. If selected, the follow-up of the checklist item will become deferred maintenance instead of a follow-up work order. On this tab, it is the default setting for the checklist item. But you can still overwrite this on the actual checklist on the Work Orders screen or on the Operator Checklist and the Review Operator Checklist screen. The checkbox was also added to the Checklist tab of the Job Plans screen.
Voice of the Customer	Work Orders \| Document Lists - Added documents collected on checklists to the grid. There are three different source types for these records. (1) The documents that are directly attached to checklist items of the work order. The source type for these records is 'Work Order Checklist'. The source code for these includes the work order, the activity, the checklist item code (unique sequence number assigned to every checklist item), and the checklist sequence between parentheses. (2) On the follow-up work order, the documents that are attached to checklist items of the work order that caused the follow-up. The source type for these records is 'From Checklist Follow-up'. The source code for these includes the originating work order, the originating activity, the originating checklist item code, and the originating checklist sequence between parentheses. (3) On the follow-up work order, the documents that are attached to the operator checklist items that caused the follow-up. The source type for these records is 'Operator Checklist'. The source code for these includes the originating operator checklist code, the originating checklist item code, and the originating checklist sequence between parentheses.
Voice of the Customer	User Defined Screens - Added the Date Created, Created By, Date Updated, and the Updated By fields to the detail and the grid of the generated user defined screen. When you click the Generate button on the User Defined Screens screen, these 4 fields will automatically be added to the generated screen or tab, and they will also be added at that time to the Fields tab. You can use screen designer to make them visible on the generated screen or tab. Note that this will not impact any existing user defined screens or tabs. Only newly generated screens and tabs will have these four fields added from now on.
Voice of the Customer	PM Schedules - Added a new Copy PM Schedule button to the screen. Depending on the selection that you make on the Copy PM Schedule popup, the data from the respective tabs will be copied to the new PM Schedule. With the following notes: (1) The Comments and Documents selection only refers to the data from the Comments and the Documents tab, respectively. Comments and documents that are associated with safety or permit records are copied based on the selection made for those specific tabs. (2) If activities are not copied, the activity will be removed from any copied permit records, and tools will not be copied at all. (3) The default to copy records from the Equipment tab is to deactivate the copied records and not copy due data. You can change this by unselecting the Deactivate checkbox or selecting the Include Due Data checkbox respectively. Date Deactivated will remain blank then, and the due date and readings will be filled in and, if in the past, recalculated. (4) Equipment records that are deactivated on the source PM Schedule will not be copied, even if the Date Deactivated is in the future.
Voice of the Customer	Permit to Work \| Comments and Documents - Added an organization option (PTWUPDCD) that controls at which status comments and documents can still be added, updated, and deleted. (1) If set to BOTH, comments and documents can be inserted, updated, or deleted until the permit to work is canceled or closed. (2) If set to COM, only comments can be inserted, updated, or deleted. (3) If set to DOC, only documents can be inserted, updated, or deleted. (4) If set to NO, the default, both can only be inserted, updated, or deleted if the permit to work is unfinished.
Voice of the Customer	Hazards and Precautions - Extended the length of the hazard and precaution description to 255 characters. This extended length is used on the Hazards screen, the Precautions screen, and throughout the system on all Safety tabs.
Voice of the Customer	E-mail Templates - Support for HTML editing can be enabled for the Body field when creating new e-mail templates. This is done through the Install Parameter HTMLMAIL being enabled. When enabled ('ON') this parameter will give the user access to the HTML toolbar. When disabled ('OFF') this will prevent access to the HTML toolbar.
Voice of the Customer	Print Requisition (SZREQF) - Ability to print images is included in the parameter for this report now.
Voice of the Customer	An update was made to single sign-on (SSO) behavior for base EAM, such that when the BRSOFATH install parameter is set to 'YES' and a user logs out of the system, the existing token is immediately made invalid. With this change, the user will need to authenticate again upon next login. A similar change was made related to the install parameter that controls SSO behavior in Digital Work. When DXSOFATH is set to 'YES' and a user logs out of Digital Work, the existing token is made invalid and the user will need to authenticate upon next login.
Voice of the Customer	PM Schedules \| Equipment - Added a new Deactivate All Equipment button to the tab. This button will deactivate all equipment records where the Date Deactivated is still blank. Records, where the Date Deactivated is already entered, will not be updated. For all records that will be deactivated, the system will: (1) Set the Date Deactivated equal to the system date, (2) delete the associated awaiting release or bypassed PM work order, and (3) clear the Set Id (linear equipment only). PM work orders that are already released or completed will not be affected by this process.

Solution enhancements - HxGN EAM - 12.1 - Release Notes/Bulletin - Hexagon

HxGN EAM Release Notes for 12.1