Maximo Quest

  IBM Maximo 7.6.0.8 onwards provides a new application – “Time Zone Rules”. This application can be accessed from Administration > Time Zone Rules. In the Time Zone Rules application, users can create rules on different processes on which time zone shall be applied from the process rule. Records will show the local date and time of the user who is accessing the record even if the record was created in a different time zone. Time zone rules can be associated with a process at the system, organization, or site level. Let us see how time zone rules work in Maximo with the example of PM Work Order generation. Following are the steps to be followed in this example- 1.First create a rule for PM Work Order Generation where Time Zone will be picked from the Asset record on the PM. 2.The current user that I am using has Time Zone set to Asia/Kolkata as shown below- 3.Maximo Application Servers are in EST time zones in the US. Now, let’s select an asset and associate Time Zone to America/Los

Maximo 7.6.0.9 provides capability to integrate Maximo with Identity Providers (IdP) like Azure AD, Open Connect etc., using SAML. Security Assertion Markup Language (SAML) is an open standard that allows identity providers (IdP) to pass authorization credentials to service providers (SP). As this integration worked properly on Maximo UI application, Browser less connection for Maximo REST, OSLC APIs was not supported and needed direct local active directory connection. Maximo has added this feature of API Key from Maximo 7.6.0.9 which can be used to overcome the unseen limitation. In the earlier versions of Maximo, creation of API for specific user and management of the key was not user friendly and it needed MAXAUTH to be passed to generate the API Key from REST/OSLC API call. With Maximo 7.6.1.2, API Key feature has been improved and now administrators can generate the API keys for users from Maximo UI and revoke them on the go. Once users have integrated Maximo with SAML authentica