Release Notes Ver 2.4 Nov 2019
How to use these Release Notes
The release notes are organized by solution area. The UC identifier refers to a specific Use Case within the AssetOptics software development lifecycle (SDLC). An explanation of the Use Case and delivered functionality follow. If there are any configuration requirements, they will be listed in the Setup Requirements following the use case explanation. The setup requirements should be used by your system administrator to plan and execute the AssetOptics managed package upgrade.
WARNING! – This release requires post upgrade configuration changes for PM Group Scheduling. Please read carefully.
Asset Management
UC-0237 Added vertical height design parameters to Building, Location and Asset Hierarchies
Added a design parameter controlling the vertical height on the Building, Location and Asset Hierarchies. The parameter can be set for each instantiation of the lightning component on a lightning page.
Setup: None
UC-0282 Deprecation System and Position recordtypes for Asset Tag object
With the release of the Location object & hierarchy, and the release of Systems, System Components & a System Hierarchy, the use of a System or Position recordtype on an Asset is now deprecated. Locations and Systems provide greater functional capabilities to organize assets.
Setup: If you have created Assets and placed in the hierarchy as a collection point for lower level equipment and/or components, it is recommended that you replace these Asset records with Location or System records. Please refer to the Locations cheat sheet and the Systems cheat sheet for further details.
UC-0266 Meter Cumulative Reading Update, Counter recordtype
Bug Fix – The Cumulative Meter Reading was not properly updated for a Counter Record Type. Removed redundant code in trigger handlers. Updated the MeterReadingTriggerHandler class to contain all logic for updates on the Meter to include; Last Meter Reading Value, Last Meter Reading Date, Cumulative Meter Reading. Removed redundant APEX code from the MeterTriggerHandler class.
Setup: None
UC-0265 Systems & Systems Hierarchies
Systems, System Components and System Hierarchies have been introduced to serve as a supplement to the Asset Hierarchy. The Asset Hierarchy enables a user to organize Equipment/Asset records in a parent/child relationship and subsequently view equipment in a tree, or hierarchical view. An asset can have only one parent and thus an asset can be in only one Asset Hierarchy. The single hierarchy forces the user to make a key organizational decision; do I organize the asset by physical position, or do I organize the assets by functional positions (assets working together to support a process). With the introduction of Systems, an asset can be represented as a System Component in one or many different systems. The System Components are organized in hierarchical manner thus enabling a single asset to be part of multiple hierarchies.
To learn more about using Systems, please refer to the AssetOptics Systems cheat sheet.
Setup: If you are using the standard AssetOptics profiles (and mapped security profile configurations correctly during the upgrade install) or standard AssetOptics permission sets (which upgrade automatically), then no update is required. If you are using custom profiles or permission sets, you will need to grant access to the System and System Component objects and fields consistent with your access requirements.
Inventory Management
UC-0256 Inventory Revaluation Variance Expense Account
An inventory revaluation variance occurs when a Stock Item is received on a Purchase Order and the purchase price differs from the current Stock Item Unit Cost AND the Valuation Method is Last-In or Standard.
Previously, this revaluation variance was booked to the Inventory Write Off GL Account for the Stock Item’s related Storeroom. The associated GL Detail record has a Type of Revaluation Variance.
So as to provide the user a greater ability to isolate revaluation variances, a new account lookup has been added to the Storeroom labeled Inventory Revaluation Variance GL Account.
Setup: If you are using AssetOptics to track general ledger transactions, update the Storeroom page layout to display the Inventory Revaluation Variance GL Account. Enter an expense GL Account in this new field.
UC-0255 Updated APEX Code to select Asset Status from custom setting when performing a Gain or Shrink Adjustment Inventory Transaction on a Serialized Stock Item.
If a Stock Item is under serialization control (Serialized = Yes) and Serialization Control Point = At Inventory Receipt, then there must be a unique Asset for each unit recorded in On Hand Qty.
If a user performs a cycle count or physical inventory check and identifies that the actual On Hand Qty is greater than AssetOptics reflects, the user will enter a Gain type Inventory Transaction to thus increase the On Hand Qty. Since each unit reflected in the On Hand Qty has a unique Asset, the user must specify the Asset when recording the Inventory Transaction; i.e. the user identify WHICH specific serial number is to be added to inventory. The Status of the selected Asset will be updated to the value entered in to the Serialized Inventory Parameters custom setting labeled Asset Tag Status for Gain/Shrink.
The APEX code updating the Asset Status was previously “hard coded” with a value of Shrink. This APEX has been updated to select the value entered in the custom setting.
Please refer to the Serialized Inventory Management Cheat Sheet for further details on managing serialized Stock Items.
Setup: None
UC-0251 Transfer Out Transfer Order record owner
When a Transfer Order of type Transfer In is Approved, a corresponding Transfer Out Transfer Order is created and related to the Transfer In order. The APEX that creates the Transfer Out order has been updated to so that the record owner follows the same business logic as the Transfer In order and Purchase Orders associated with that Storeroom.
This rule is as follows. When a Purchase Order or Transfer Order is created, the Storeroom Default Buyer will be set as the record owner. If this user is not active, then the record will be owned by the Storeroom record owner. If this user is not active, then the record will be owned by the running user.
Setup: None
UC-0254 Default Value for New Transaction on a Transfer In order line
When receiving a Stock Item to inventory from a Transfer In order line, the default value on the New Transaction line has been updated to reflect the “Shipped Not Received” value in lieu of the Open Qty.
This update ensures the user does not have to edit the received quantity when a partial transfer is performed.
Setup: None
UC-0286 Validation rule added requiring a Storeroom on a Stock Item record.
A new validation rule has been added that ensures the user enters a Storeroom on a Stock Item record. This was previously being enforced only as a required field on the page layout. It is now enforced as a validation rule and thus via the API.
Setup: Ensure that a Storeroom is entered for all Stock Item records. You may temporarily deactivate this validation rule if needed.
Preventive Maintenance Scheduling
UC-0270 Updated PM Due Date formula on PM Schedule object to reduce character count
The PM Due Date formula on the PM Schedule object was updated to reduce the compiled character count.
Setup: None
UC-0272 Updated PM Group Schedule AutoRelease SOQL to include Active Status value.
Updated the SOQL on the batch APEX class that selects PM Group Schedules eligible for Next Due Date recalculation to include only PM Group Schedules where Status = Active.
Previously, the SOQL selected records where Recalculation Required = True. This update was made to resolve potential errors in an edge case wherein a Work Order is manually released and then the PM Group Schedule Status was set to Inactive. When the Status is Inactive, further changes can be made to the PM Group Schedule that would result in the Next Due Date recalculation APEX class failing.
Setup: None.
UC-0274 Update PM Group Schedule AutoRelease field help text
Updated the help text on the PM Group Schedule AutoRelease field to provide greater clarity.
Setup: Since field level help text can be updated in a production org, managed package updates do not automatically apply. Thus, you should copy/paste the field Description text into the help field text.
UC-0275 Update PM Schedule AutoRelease field help text
Updated the help text on the PM Schedule AutoRelease field to provide greater clarity.
Setup: Since field level help text can be updated in a production org, managed package updates do not automatically apply. Thus, you should copy/paste the field Description text into the help field text.
UC-0276 Updated PM Group Schedule Next Due Dates Recalculation APEX
The APEX class that calculates Next Due Dates on PM Group Details (the child line items to a PM Group Schedule) has been refactored so as to resolve an edge case error during the end of cycle rollover process; i.e., once you release the Preventive Work Order for the PM Group Detail with the Maximum Monthly Interval.
Three new fields have been added to the PM Group Schedule to accommodate this change.
- Current Cycle
- Cycle Start Month
- Cycle End Month
The Current Cycle value will increment by one (1) each time the Next Due Dates for the PM Group Detail with the Maximum Monthly Interval is performed; i.e. when you get to month 36 in a PM Group Schedule with a Monthly, Quarterly, Annual, 3-Yr cycle (Monthly Intervals of 1-3-12-36).
Do NOT put these fields on a page layout. Do NOT enable edit rights on these fields thru either Profile Security or Permission Sets. These values are updated via APEX code. Manually editing these values will produce unexpected results. The System Administrator profile does require Edit access to these fields which will be enabled upon package upgrade.
Setup: WARNING! – A new custom setting, PMGS Testing Parameters, requires an entry of zero (0) at the Org wide level. All PM Group Schedules will need to be set to Inactive prior to applying the upgrade and returned to Active after applying the upgrade. To maintain accuracy in Next Due Date calculations, the Starting Month on the PM Group Schedule will require review and likely update prior to returning the Status to Active. This task can be accomplished manually thru the user interface or via Dataloader. Should you require assistance, please contact support@assetoptics.com
UC-0280 PM Routes Validation Rule – 99 Route Stops Maximum
A validation rule has been added to the PM Route Stops object ensuring that a maximum number of 99 Route Stops. Should your PM Route require more than 99 stops, it is recommended that you create a second PM Route with same scheduling logic to thus release a second Route Work Order.
Setup: None.
UC-0284 PM Group Schedule Starting Month Validation Rule
A validation rule that precludes the user from entering a Starting Month greater than the Maximum Monthly Interval found on the related PM Group Details was added.
A new field on the PM Group Schedule object labeled MaxMIRollUp was created to support this validation rule.
Setup: If you are using the standard AssetOptics profiles (and mapped security profile configurations correctly during the upgrade install) or standard AssetOptics permission sets (which upgrade automatically), then no update is required. If you are using custom profiles or permission sets, grant Read access to the MaxMIRollUp field.
Purchasing
UC-0253 Update Serialized Inventory Asset Status on PO Stock Receipt
When receiving a Stock Item on a Purchase Order and the Stock Item under serialization control (Serialized = Yes) and the Serialization Control Point = At Inventory Receipt, an Asset record is created and placed in the Primary Bin Location. The Status of this Asset was previously set to “Stored” via APEX code.
The APEX code has been updated to use the Status value defined in the Serialized Inventory Parameters custom setting labeled, Asset Tag Status at Receipt. This change enables an org specific setting and thus your process can be further configured to your unique requirements.
Setup: The default value for this custom setting is “Stock Inventory”. Should you require a different value, please update the custom setting. You MUST add any user defined Status value to the Asset Tag Status field and enable for all recordtypes used for Serialized Inventory.
Work Management
UC-0262 Work Order Hierarchy Lightning Component
A new Lightning Component has been created that will display Work Orders in a parent/child relationship. By default, this Lightning Component is displayed on the Route Work Order page layout. The component can be displayed on any Work Order Lightning page.
Setup Requirement: None
Installation URL
Please submit a case via the AssetOptics customer community or submit an email requires to help@assetoptics.com to request the managed package installation URL.