Design decisions - HxGN EAM - 12.1.1 - Feature Briefs - Hexagon

HxGN EAM Digital Work
Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
12.1.1

  • HxGN OS integration:

    Digital Work does not go through IONAPI but follows direct SSO integration like base EAM. This means it cannot be added as a QR Code icon under the Desktop and Mobile Applications menu inside the Ming.le application. However, the user can go into the base EAM QR Codes Setup screen to setup QR code for easy login by providing the tenant and server information.

  • Login Install Parameters:

    Digital Work uses the LGNEAM install parameter rather than LGNMOB.

  • User Defined Fields – Quick Filter:

    For UDFs to be visible in the quick filter of Digital Work, they must be available in the base EAM layout.

  • Layout of cards:

    Screens that have multiple tabs have a fixed layout of tabs and cannot be moved. Fields and section headers within a tab can be screen designed using the special Screen Designer for Digital Work screen in base EAM.

  • Section headers:

    In base EAM, the section headers can be collapsed or expanded. This is not the case with Digital Work. The section headers can either be made available or hidden using the Screen Designer for Digital Work screen in base EAM.

  • Filtering Custom Fields:

    Custom fields are always available in the quick filter, unlike in base, where the user must load them by pressing Click here. Custom fields are displayed below the --Custom Fields-- label.

  • Summary Grid:

    The fields displayed in the list view are always the Mixed view fields (Split View Display = Mixed), as set on the Screens screen in base EAM, i.e., the Code field followed by Description will always display as the first two fields in the summary grid, along with three other fields, determined by the grid field order set in base EAM. The Date and Date/Time fields can also be displayed in the list view but will not be searchable. So, a total of five fields will be displayed in the list view summary grid.

  • Color Icons:

    Color icons are supported on the list and record view based on the setup performed on the System codes screen in base EAM. The following entities have color icons show up in the list and record view. In the record view, it appears at the field level in card view:

    • EVST (Status) – Work Order status – On the Work Order screen

    • JBPR (Code) – WO Priority – On the Work Order screen

    • PWRS (Code) – Risk – On the Permit to Work screen

    • WLST (Status) – Workflow Event Step Status – On the ‘Approval Steps’ of the Workflow Approval screen

    Color icons for classes are also supported for the following screens currently in Digital Work. If a Color icon is configured for classes on the Classes screen in base EAM it shows in Digital Work:

    • OBJ (Equipment): On the Assets/Systems/Positions screen

    • PART (Part): On the Parts screen

  • Language Settings:

    The device’s language is set in Digital Work when the user logs in (i.e., after a fresh install or update of the app). The Login and Settings forms' labels will be presented in the language set on the device. English will be set if the device language is not a supported language in base EAM.

    • For iOS, language is set separately from locale (called 'Region' in Settings)

    • For Android, locale and language settings are the same (i.e., locale is determined by the selected language)

      After logging in, the EAM locale (server) language will always be used in all places, including the login and settings form

  • Locale Settings:

    • Date and Number fields on detail screens are always displayed in the EAM locale coming back from the server.

    • Number and Date fields on insert and edit forms and data spies (or anywhere numbers and dates are entered or inserted by a user) are displayed in device format. This means:

      • Decimal separator from device locale.

      • Group separator from device locale.

      • Negative symbol "- ".

      • Group digits 3.

    • When entering a number, the following keyboards are shown in their respective operating systems:

      • iOS: Numbers and punctuation keyboard with numbers across the top and symbols below

        There is no number pad in iOS with both decimal and negative symbols.

      • Android: Full keyboard with numbers on the top

  • Show Toolbar on Load and Extras Toolbar:

    Selecting the Show Toolbar on Load check box on the Settings menu always shows the Extras toolbar when loading a screen. This toolbar is visible in the device wherever a dataspy or search bar exists, such as list views, lookups, and tab list views. This is always turned on by default at the user level for the device but can be turned off if needed.

    This Extras toolbar can be expanded or collapsed by pressing the Caret icon, next to the search bar.

  • Barcode Icon:

    This is used to scan a QR code or bar code with the device’s camera. When scanning, the value is returned within the dataspy search bar and the results are queried automatically (if any). This is a standard search done within the dataspy. For example, it contains the search on the summary grid fields if no filter is applied. If a filter is applied on the dataspy search and the Filter field type is Date/Time, Checkbox, or Drop-down, then the Barcode icon is not available, indicating that the search can only be done by manually typing in the values inside the search bar.

    This is the list of supported bar code types:

    iOS and Android

    CODE_39

    CODE_93

    CODE_128

    DATA_MATRIX

    EAN_8

    EAN_13

    ITF (also known as ITF14)

    PDF_417 (on Android only when passed in explicitly via formats)

    QR_CODE

    UPC_A

    UPC_E

    When either UPC_A or EAN_13 or both are specified, both can be returned.

    Android only

    CODABAR

    MAXICODE

    RSS_14

    iOS only

    AZTEC

    CODE_39_MOD_43

    INTERLEAVED_2_OF_5

  • HTML Comments:

    Comments that are entered in base EAM, with the HTML editor turned on (i.e., HTMLCOMM = ON), will be displayed in Digital Work, as read-only anywhere comments are supported. The user can only view or delete the comment and close the pop-up. Embedded videos within the comments pop-up will play inside the pop-up. If an external link is opened, like a video or a web page, it will render within this comments pop-up or tab. The HTML editor is not supported. All Hyperlink – Source Types are supported except KB Article.

  • Inline Comments:

    The Comments text box (HTML editor) will be hidden for tabs that have inline comments, for example, Parts | Suppliers – Comments (HTML Editor). This has been done because a mechanism for supporting rich text comments for the inline comment editor has not been developed. The user can still enter comments using Add/Edit Comments.

  • Lookups:

    In all lookups across the system, the first 3 fields as per base layout will be displayed. In cases where there are only 1 or 2 fields within the lookup, those will also be displayed as per the layout. When a search is performed inside a lookup, the system will honor the settings of install parameter QUICKLOV. This install parameter determines whether the quick filter inside the lookup will default to show the first field in the grid or Code/Primary key.

    If set to YES, the quick filter will default to the first field in the grid, as set in the lookups dataspy layout in base EAM.

    If set to NO, the quick filter will default to ‘Code’ or Primary key of that lookup.

  • Multi factor Authentication:

    Third party multi-factor authentication is supported when entered on an external website. This means the internal EAM MFA flow is not supported (i.e., the MUTLIFAC install parameter).

  • Custom Tabs with URL:

    When a custom tab is added on the Screens screen in base EAM with a URL specified (i.e., Tab type = HTML), opening this tab will pass the value of the URL in the device’s default web browser and load the web page. The user can always close the browser and return to the app anytime.

  • Custom screens with URL path:

    When a custom screen is created on the Screens screen in base EAM with an URL path, Digital Work will :

  1. Open this screen within the app in a Web View if Open URL in New Window is cleared on the Screens screen in base EAM. The user can access the main menus to go to another screen from here. Or,

  2. Open this screen in a new window using the device’s default browser if Open URL in New Window is selected on the Screens screen in base EAM. The user can go back to Digital Work from this browser window.

    This custom screen can be configured to open either as a:

    1. Screen on the menu

    2. Hyperlink at the field level (The Open URL in New Window check box will be ignored at this level, as in base EAM, and the screen will open in a Web View at all times.)

    3. Inbox hyperlink

Clone screens created on the Screens screen are also supported.

  • Action Item permissions:

    When the user opens a form by pressing an action item, and if the user does not have permissions to open the action item (by rules set in base EAM), the form will open with all the fields protected. The error message will be displayed, only when the user presses Save. This is by design, and is different from base, wherein an error message will be displayed when the user presses on the action item. When the checklist form is opened from the record view using the Checklist icon, the standard permissions error will display.

  • Swiping on the list view:

    The user can delete a record from the list view by swiping left. This swipe motion will show the Delete icon. The user can cancel this action by swiping right. But if the user wants to delete this record, pressing the Delete icon will show the standard message for deletion. This option is available only in list views (not tabs that have lists).

  • Captions:

    When a tab or a pop-up has a caption, it will be displayed when the user presses the additional Information icon Information icon next to the title. Long-pressing will open a small pop-up window with the captions. The user can close the captions pop-up by pressing the OK button.

  • Server time offset:

    Server time offset will be honored as set in base EAM. If the date/time field is cleared, the system will default the current system date/time without server offset.

  • Push Notification:

    Digital Work supports Push Notification when setup and enabled in base EAM. This is the required setup in base EAM for the app to receive push notifications with the following exceptions:

    • Attaching reports is not supported

    • The SMTPSEV install parameter is not needed for push notifications

    • All tables in base EAM can be configured to send push notifications to the app

    • The user to whom the push notification will be sent must have a value specified in the Digital Work App drop-down on the Users screen

  1. The notification will appear, both on the Notification Center and on the App icon. The App icon notification will differ for Android and iOS. Android will show the total count of notifications on the App icon, while iOS will only show the number ‘1’ to indicate that notifications exist.

  2. Tapping or clearing the notification from the Notification Center will make the App icon notification go away, this means the user acknowledged the notification.

  3. Tapping on the notification from the Notification Center will open the application. It will be like opening the app, in that:

    • If the app is already ‘Open/logged in’, this will open the last opened screen when last minimized

    • If logged out, this will open the login page

  • Screen and Folder icons:

    The main menus will display Folder icons next to them to indicate that there are more screens/reports within that menu. A maximum of 10 folders are possible at the main menu level. If a single main menu folder exists on this tab without any sub-menu folders, the screens/reports will be displayed with a Page icon.

  • User Defined Grids (Grid Designer):

    User-defined grids that are setup either as a tab or list view is supported. When hyperlinks are configured at the field level (Grid Designer | Fields tab) they will be available as hyperlinks. When no hyperlinks are configured, pressing on a record on this list will direct the user to the Details view. If one or more hyperlinks are configured, pressing the touch points will show the list of configured hyperlinks, along with the option to drill-down to the details.

  • User Defined Screens:

    User-defined screens created in base EAM either as a tab or a standalone screen is supported. This feature is not available for Mobile Requestor users.

  • NFC Scanning Capability:

    The following steps must be taken to ensure that the user experience is seamless, when scanning an NFC tag using Digital Work:

    1. The device must support NFC scanning in the first place (i.e., NFC chip enabled device)

    2. The device is within scanning vicinity of the tag

    3. The tag is configured as per NDEF protocols – If no data exists on the tag, the system will return the tag ID in search bar upon scanning.

    4. If NDEF data exits on the tag, then:

    • The data must be of type STRING or flat JSON. If the data configured on the tag is of either of these types, 2 new install parameters have been created in base EAM to enhance and customize the data being read:

      DWNFCTYP: This install parameter determines the allowed data format while performing an NFC scan. Valid values are STRING and JSON. If this install parameter is invalid/NULL, it will behave like it's set to STRING. If set to STRING, it will just populate the data on the tag as is, on the dataspy search bar. If set to JSON, the system will honor the install parameter.

      DWNFCKEY: This install parameter determines the value to be used as the key when populating data after performing an NFC scan in Digital Work. When using JSON format for an NFC tag and a key/value pair like "AssetID": 32132, “Zip”: 29607 exists, specifying a value of AssetID in this install parameter indicates that the system will populate 32132 in the dataspy search bar. If this install parameter is invalid/NULL, the system will not yield any results on the scan.

  • Favorites:

    When the 12.1 version of Digital Work is connected to a base 12.1 server – the user need not rely on screen cache as setup on base EAM to set their favorites on the device.

    The user can simply press/depress the Star icon at the top of a screen/report (next to the screen/report name) to favorite/un-favorite a screen/report.

    If a screen/report has the star selected, it indicates that it's part of the Favorites list.

    The Favorites screen available as default in the menus, is where the user can:

    • Search existing favorites – By using the search bar on the top.

    • Add new favorites - By pressing the ‘+’ button on the top, will display the list of screens/reports available for the user as per the User Groups | Digital Work menus.

    • Remove existing favorites – By pressing the Edit button on the top.

    • Navigate to the screen/report by pressing anywhere on this list.

    When the 12.1 version of Digital Work is connected to a base server which is BEFORE 12.1 – All screens added to screen cache in base EAM will show as part of this favorites list. The user cannot add or edit favorites in this scenario.

  • eSignature support:

    Digital Work supports the eSignature pop-up and honors the setting of install parameters ESGATHSL and JWTEXPRY when SSO is enabled. For eSignature to authenticate via SSO by employing SAML methodology, the following install parameters must be set to:

    • LGNEAM = EXTERN

    • ESGATHSL = YES

    • JWTEXPRY - The value for the lifespan of the JSON web token. The maximum value will be 1800 seconds. If the value of this parameter is invalid or less than the system configured default value (from the YML configuration), the default value will be utilized.

    • DXESNRPC = NO

  • Multi Factor Authentication (MFA):

    Third party multi-factor authentication is supported when entered on an external website. The MULTIFAC install parameter is not supported – i.e., the install parameter which is set in base EAM.

    We have yet to perform comprehensive tests for Hexagon cloud SSO configured build + MFA supported via Hexagon (post Hexagon migration). MFA support is available for Infor/Hexagon cloud SSO configured build + MFA supported via Ming.le (Infor).