Setting up Password Expiration in Maximo

Security; Password Expiration; Groups; TPAESECURITY

How to set up password expiration in Maximo.

Answer

Password Expiration can be set in a few places in Maximo. The default setting is set In the Security Groups application, in the Select Action menu, using the Security Controls option.
All new groups created after this setting is made will inherit this value, however any groups that existed prior to this setting being in place will not get updated.
This value only gets referenced when a new group is created.
If a group is created and has inherited the value, then the value is changed in the Security Controls option, the groups that existed prior to this change will not be updated.
For this reason, when setting up Maximo for the first time, it may be better to decide on a default password expiration value and have that value in place prior to creating your groups.
Once the value for a group has been set, or if no value has been set prior to creating the group, you can update the password expiration setting by using the Override Password Duration option in the Select Action menu of Security Groups.
This also allows you set a specific password duration at a group level different from the default.
Here is a breakdown of how the password expiration is handled by Maximo:
Each group has a password expiration value.
If a user belongs to more than one group, the longest expiration period is the one inherited.
For example, if a user belongs to one group that has a setting of 90 days and another that has a value of 30 days, the user inherits a 90 day expiration setting.
In the case of a user belonging to any groups not containing a password expiration, the user's password will never expire.
You would need to use the Override Password Duration option to set an expiration value for each group the user belongs to.
Once the password expiration settings are set, the clock starts to count down after the password is changed with the expiration settings in place.
NOTE:
If the user existed before the password expiration is set, the password will not expire because the timer does not start until the next password change after the password expiration has been set.
The remedy is to change the user's password after setting the password expiration.
Removing the user from the group the expiration date is set on and adding them back will also work.

Creating summary or detail Query-Based Reports in cloned (duplicated) applications

Question

From Maximo 7.1.1.6 onwards, you can create Summary or Detail Query-Based-Report (QBR). But in cloned applications, the option to select the type of QBR is disabled. How can you enable that option?

Answer

The steps below will show how to create the Summary or Detail QBR in cloned applications with an example:

1. Go to Application Designer - Open the WOTRACK application.

2. Select Action - Duplicate Application Definition - Create WOTRACK2 application with the description 'Work Order Tracking 2'.

3. Go to Security Group - Give adequate privileges for the WOTRACK2 application to the security group, for example MAXADMIN.

4. Login again and open the WOTRACK2 application.

5. Click on the 'Create Report' toolbar button to create the Query-Based-Report.

As you can see below, the option to be able to select the style of report ( Summary or Detail Report) is not enabled.

By default, all cloned (duplicated) applications have the same problem.

In order to enable the option above, please follow the steps below:

When the WOTRACK2 application is cloned from WOTRACK , the WOTRACK2 application has the same report object as the original application WOTRACK.

For example:

1. Create the report object for the cloned application (WOTRACK2).

Go to the Integration / Object Structures application - Find 'REP_WORKORDER' .

Based on 'REP_WORKORDER', create the new report object for WOTRACK2 called 'REP_WO2' (you can also duplicate 'REP_WORKORDER' to create 'REP_WO2' )

-- Object Structure : REP_WO2

-- Description : Work Order Details 2

-- Consumed By : REPORTING

-- Application : WOTRACK2

2. Save the record.

3. Go to the Report Administration application.

4. Run Select Action / Set Report Object Structure Security.

5. Filter application with the value 'Work Order Tracking 2' . You can see the newly-created report object 'REP_WO2' for WOTRACK2 application.

P.S. : the WOTRACK2 application's description is 'Work Order Tracking 2'.

The REP_WO2 report object's description is 'Work Order Details 2'.

6. Now you need to define any security groups who can access the newly-created report object .

- Click New Row

- Add the 'MAXADMIN' group.

7. Go to the 'Work Order Tracking 2' application (WOTRACK2)

Try to run 'Create Report'. Now you can select the style for the QBR report (Summary or Detail).

Why am I unable to create a new inspection form in the Work Center? Most likely, you are not granting access to integration objects that are related to the Work Center Yes, in order to use the Work Center, specific integration objects must be created (by default when Maximo is installed) or you must manually create them yourself If it is the first time the Work Center is being used, it is necessary to check if all integration objects related to it are created and if they have access grant But back to the specific problem of not being able to create a new inspection form, please take a look at the steps below: (Detail: You must be logged in as MAXADMIN to perform these steps) 1) Go to Integration > Object Structures application and make sure you have the following objects: MXAPIINSPFORM MXAPIINSPFORMSTATUS MXAPIINSPRESULT 2) Go to Security Groups application and bring up the group for work center - To manager the Inspection Forms, I believe that the user is in the BIZANALYST - Business Analyst group 3) Go to Applications tab > seach for Manage Inspection Forms (in the Description column) Give the grant access Access to Manage Inspection Forms -> Grant Access? checked 4) Go to Object Structures tab > search for MXAPIINSPFORM and give the grant access for all options bellow: Delete MXAPIINSPFORM Insert MXAPIINSPFORM Read MXAPIINSPFORM Save MXAPIINSPFORM Please perform the same steps to MXAPIINSPFORMSTATUS and MXAPIINSPRESULT objects Save and try to create the new form in the Work Center. I hope this tip helps you

Maximo Asset Management 7.6.0.7 Interim Fix 004 released The Interim Fix (IFIX) is available at Fix Central. As with all IFIXes, MAM 7607 IFIX 004 is cumulative and includes all fixes provided with Maximo Asset Management 7.6.0.7 Interim Fix 003, with these additions: APAR Application Name Description IV94884 System User Interface After you change the vertical label value to 0, radio buttons shift. IV97283 Application Designer In the Application Designer, in the Create Work Order with Appointment window, an invalid binding occurs. IV97448 Work Order Tracking In the Assets application, when an asset meter has a datetime value and you enter an identical value in the field, the meter has varying results. IV96894 Assignment Manager In the Assignment Manager, availability is displayed after vacation hours have been allocated. IV96610 Invoices In the Invoices application, when you use large currency exchanges, an error occurs. IV91405 Receiving In the Receiving application, when a vendor on a purchase order has a different exchange rate than the purchase order, you cannot return a rotating asset. IV97236 Receiving In the Receiving application, you cannot return rotating assets. To install the IFIX, see Installing an Interim Fix in Maximo 7.6.

Maximo Asset Management 7.6.0.8 Interim Fix 001 released The Interim Fix (IFIX) is available at Fix Central. APAR Application Name Description IV95250 Work Order Tracking After you attach a job plan to a work order, the scheduled started and finish dates are read-only. IV96829 System Object Security Scans See CVE-2017-5644, CVSS Base Score: 5.3 and IBM X-Force Exchange: CVE-2017-5644 for the current CVSS Temporal Score. IV97448 Work Order Tracking In the Assets application, when an asset meter has a datetime value and you enter an identical value in the field, the meter has varying results. IV97391 Assets In the Assets application, when you create a duplicate asset, spare parts are not duplicated. IV97196 Graphical Assignment In the Graphical Assignment application, when you execute the Run Optimization action, an exception occurs. IV96724 Graphical Scheduling In the Graphical Scheduling application, when you assign work, a null pointer exception occurs. IV97261 Graphical Scheduling In the Graphical Scheduling application, when you create a schedule, constraints disappear after you commit the schedule. IV97261 Graphical Scheduling In the Graphical Scheduling application, when you create a schedule, constraints disappear after you commit the schedule. IV97237 Graphical Scheduling In the Graphical Scheduling application, when you duplicate a work order, the duration in the schedule is incorrect. IV97132 Graphical Scheduling In the Graphical Scheduling application, when you hide the navigation menu, the Resource section is no longer in sync. IV97416 Graphical Scheduling - Large Project In the Graphical Scheduling-Large Project application, on the GANTT View tab, no data is loaded. IV95428 Invoices In the Invoices application, you cannot approve a multi-line invoice that is associated to a repair if a rotating asset is in the repair location. IV96609 KPI Manager In the KPI Manager application, when you duplicate a record, the Created By field retains the ID of the user who created the original record. IV97453 Labor Reporting In the Labor Reporting application, when a Labor record has multiple crafts associated to it and you create a new row on the Labor record, the Craft field is not populated. IV96188 Work Order Tracking In the Work Order Tracking application, the Actual Material Cost attribute on the work order table is calculated incorrectly. IV96965 Work Order Tracking In the Work Order Tracking application, you can create constraints that allow circular values to be entered. IV97026 Work Order Tracking The map persistence is not kept in either the Work Order or Location application. IV94523 Work Order Tracking When a work order has multiple activities and you change the status of one of the activities to completed, the status' for all activities are changed to complete. IV95042 System Properties When creating a new change record, you attempt to select a value from a field. Instead of retrieving the record, you receive the following message: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 1795.  The record could not be retrieved from the database. IV97583 Integration Modules When you delete an application authorization record with the Maximo Integration Framework, an error occurs. IV96511 System User Interface You can attach files files that do not have file extension types. IV96781 Graphical Scheduling In the Graphical Scheduling application, when you create a new schedule or work list, an error occurs. IV96422 Communication Template Security defect To install the IFIX, see Installing an Interim Fix in Maximo 7.6.

Attribute can be deleted with active Launch Point associated

Maximo will allow an Attribute to be deleted from Database Configuration while there is an active Launch Point that references it. 

Steps to reproduce:
1. In Database Configuration application, add a new attribute to ASSET or some other object.
1.1. Turn on Admin Mode and Apply Configuration Changes.
2. In Automation Scripts application, Create a Script with an Attribute Launch Point.
2.1. The Object and Attribute should be the one you added in step 1.
2.2. Name the launch point and script something valid, and make the source code something simple, like print "Hello world!".
3. Go back to Database Configuration and delete the new attribute.
3.1. Apply Configuration Changes.

An error should be thrown at step 3, but it isn't.

Integrity Checker should catch the resulting anomaly, but it doesn't.

When you go to an application based on the object from step 1, now, you will get an error that the attribute is missing. 

Development mentioned this is working by design, but could be considered as an enhancement on the product (not a bug), which means that this functionality is not currently present in Maximo, and that this cannot be fixed on the current version since the fix would require changes to the product architecture.

There is no Automated Scripting (or any other MIF) awareness designed and coded into Database Configuration application. Therefore this is working as designed. 

BMXAA3279E and BMXAA3344E errors while trying to approve a Revised PO 0 people like this

Problem:

After closing a work order associated with a PO that is revised while trying to approve the PO revision, the following error is displayed:

BMXAA3279E - Could not change PO XXXX status to APPR.
BMXAA3344E - The purchase order cannot be approved. Line 1 contains a work order that is either closed, canceled, or waiting on approval.

Steps to replicate:

1. Go to Work Order Tracking application.

2. Create a new work order against any valid GL Account.

3. Save, approve the work order and take note of its number.

4. Go to the Purchase Orders application.

5. Create a new PO against any valid vendor and with just 01 PO line as the following:
    Line Type = Service
    Description = Test1
    Quantity = 1.00
    Order Unit = EACH
    Unit Cost = 1.00
    Charge To > Work Order = the WO above

6. Save, approve PO and take note of its number.

7. Go to the Work Order Tracking application.

8. Bring up the work order in question and close it.

    Note:
    The system warns user of the following but closes the work order anyway:
    "BMXAA4577W - Open purchase orders exist here or at some point below in the hierarchy. Would you still like to change the status to Closed?".

9. Go to the Purchase Orders application.

10. Bring up the PO and create a revision.

11. In the PO Revision 1, add a new PO Line as the following:
      Line Type = Service
      Description = Test2
      Quantity = 1.00
      Order Unit = EACH
      Unit Cost = 1.00
      Charge To > GL Debit Account = any valid GL Account

12. Save the PO and try to approve it.

At this point, system throws:

"BMXAA3279E - Could not change PO XXXX status to APPR.
BMXAA3344E - The purchase order cannot be approved. Line 1 contains a work order that is either closed, canceled, or waiting on approval."

Resolving the problem 

The workaround is:

Cancel the PO Revision 1, close the PO Revision 0 and create a new PO corresponding to the second PO Line you've tried to add in step #11.

If the suggested workaround does not apply to your case, please contact IBM Maximo Support.