Configuring eSignature keys
Use eSignature keys in your web browser or your mobile device to confirm that a status change or attribute value update is complete and valid.
About this task
Every object and attribute in Maximo® Manage can be configured to require an eSignature key. For example, you could require an eSignature for a change in the PRIORITY attribute for an asset or when the status of a work order is updated. Any attributes at the top-level of the data relation structure are supported. For example, ASSETNUM, PRIORITY, and DESCRIPTION. Attributes at the child level, for example attributes for the work log associated with a work order, cannot be validated with an eSignature.
The eSignature key is tracked by using the logintracking object, which validates the change and associates the user, date, time, the originator record, and the reason for the change.
The eSignature keys must be enabled in the Maximo Manage system properties before you can use them.
| Property | Summary |
|---|---|
| maximo.mobile.esignatureenabled | Set to true to enable eSignatures to be used to:
Starting in 9.2, this is the primary system property that the mobile platform checks on the client side to determine if eSignature validation is enforced on the device. In versions before 9.2, the mobile platform checked both this property and mxe.allownativeesig. |
| maximo.mobile.wostatusforesig | Set to a work order status that requires an eSignature. For example, COMP. This property enables eSignatures to be used for work order status changes on mobile devices only. |
| mxe.allownativeesig | Set to true to require a native key for Maximo Asset Management actions that
require eSignature validation. Starting in 9.2, the mobile platform no longer checks this property on the client side. However, the server continues to use this property during eSignature validation in combination with other system properties such as mxe.usemasforesig to control the validation flow. For example, whether validation is based on the eSignature key, user Maximo Application Suite password, or user LDAP credentials. |
When you change the status of a work order or update an attribute value, and then you enter an eSignature key, the change transaction is sent to the Maximo Manage server. The eSignature verification request is sent to the Maximo Manage server after the change transaction is completed. If you lose your connection to the Maximo Manage server before the eSignature key is sent, it is sent when you reconnect. Due to many factors, it might take an extended amount of time for the status change transaction to be completed.
Starting in 9.2, the mobile platform no longer performs eSignature validation on the device. Instead, when you enter an eSignature key on your mobile device, the mobile application encrypts the value using a public key and sends it to the Maximo Manage server for validation. The server performs all e-signature verification. During onboarding or data refresh, the mobile device downloads or updates the public key used for encryption, but you are no longer prompted to create or validate your eSignature key on the device.
In versions before 9.2, an eSignature key was stored both on the server and the mobile device. The mobile application verified the e-signature locally against the key stored on the device when in online or offline mode. If the e-signature key changed on the server, you had to log out and log back in, or refresh your data, to update the key on your device.
E-signature keys are created and stored on the Maximo Manage server in the user profile. The eSignature keys can be changed only on the Maximo Manage server.
IBM® Maximo Asset Management and IBM Maximo Application Suite both require eSignature keys to sign off on work order status changes and attribute value updates. When you switch from Maximo Asset Management to IBM Maximo Application Suite, you must enable eSignature system properties and create an eSignature key in each user profile.