IBM Support

Updates for Maximo Asset Management 7.6.0 feature packs

Fix Readme


Abstract

Each feature pack contains resolved defects, behavior changes, and new platform supports. A complete list of updates for all Maximo Asset Management 7.6.0 feature packs can be found in this tech note.

Content

The Maximo_v7.6.0_information spreadsheet contains a complete list of defects, security defects, behavior changes, and new platform supports for all Maximo Asset Management 7.6.0 releases. All of the information in this tech note is included in the attached file.

Maximo_v7.6.0_information_1.xlsx

 

New platform supports for Maximo Asset Management 7.6.0

Feature pack New platform support Notes
7.6.0.10 No new platform supports were added in this feature pack  
     
7.6.0.9 Cognos 11 For more details on this certification, please access the Maximo supported product matrix - Reporting & Archiving tab.
     
7.6.0.8 Windows 2016  
  SQL Server 2016  
  Chrome 57  
  FireFox ESR 52  
     
7.6.0.7 No new support  
     
7.6.0.6  DB2 11.1  
  Oracle JRE 1.8.0_102  
  JDK 8 (server side)  
  USGCB  
     
7.6.0.5 RHEL 7.1 LE  
  JRE 1.8.0.77  
  JDK 8 (server side)  
  FireFox 45  
     
7.6.0.4 JRE 1.8.0_66  
  Oracle ebs 12.2.5  
  Dojo 1.10  
     
7.6.0.3 JRE 18.8.0_60  
  Edge Browser  
  Firefox ESR version 38.3.0  
     
7.6.0.2 JRE 1.8_51  
     
7.6.0.1 JRE 1.8_45  
  SQL server 2014  

Maximo Linear Asset Management updates

Fix packs for Maximo Linear Asset Management are included in Maximo Asset Management feature packs.

Maximo Linear Asset Management version Maximo Asset Management fix pack
7.6.0.2 7.6.0.9
7.6.0.1 7.6.0.8

Release dates for Maximo Asset Management by version

Release Release Date
7.6.0.10 14-Dec-2018
7.6.0.9 1-Dec-2017
7.6.0.8 19-May-2017
7.6.0.7 17-Feb-2017
7.6.0.6 21-Oct-2016
7.6.0.5 23-Jun-2016
7.6.0.4 18-Mar-2016
7.6.0.3 22-Jan-2016
7.6.0.2 11-Sep-2015
7.6.0.1 19-Jun-2015
7.6.0.0 15-Dec-2014

Resolved security defects for Maximo Asset Management 7.6.0 feature packs

Version CVE Score APAR Number Short Description CVSS Base Score CVSS Temporal Score
7.6.0.10 CVE-2018-1414 IJ02495 SQL injection vulnerability 5 See https://exchange.xforce.ibmcloud.com/vulnerabilities/138820 for the current score.
7.6.0.10 CVE-2018-1686 IJ07526 Reflected XSS Attack 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/145505 for more information.
7.6.0.10 CVE-2018-1584 IJ03986 Cross site scripting vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/143497 for more information.
7.6.0.10 CVE-2018-1415 IJ02532 Reflected XSS Attack 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/138821 for more information.
7.6.0.10 CVE-2018-1415 IJ07551 Reflected XSS Attack 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/138821 for more information.
7.6.0.10 CVE-2018-1697 IJ07799 Authentication vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/145966 for more information.
7.6.0.10 CVE-2018-1715 IJ07770 File Upload XSS Attack 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/147003 for more information.
7.6.0.10 CVE-2018-1699 IJ07458 SQL Injection 6.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/145968 for the current score.
7.6.0.10 CVE-2018-1528 IJ06122 API Leak 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/142290 for the current score.
7.6.0.10 CVE-2018-1872 IJ07795 Cross site scripting vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/151330 for the current score.
7.6.0.10 CVE-2018-1698 IJ07455 Detailed error messages revealed 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/145967 for the current score.
7.6.0.10 CVE-2017-5662 IJ00575 Open source Apache vulnerability 6.5 See https://exchange.xforce.ibmcloud.com/vulnerabilities/125198 for the current score.
7.6.0.10 CVE-2017-12626 IJ04348 Open source Apache vulnerability 5.5 See https://exchange.xforce.ibmcloud.com/vulnerabilities/138361 for more information.
7.6.0.10 CVE-2016-1000031 IJ04373 Open source Apache vulnerability 7.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/117957 for more information.
7.6.0.10 CVE-2018-1554 IJ05640 Cross site scripting vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/142891 for the current score.
7.6.0.9 CVE-2017-1352 IV96409 Formula injection 5.5 See https://exchange.xforce.ibmcloud.com/vulnerabilities/126538 for the current score.
7.6.0.9 CVE-2017-1357 IV96422 E-mail vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/126684 for the current score.
7.6.0.9 CVE-2017-1499 IV96511 Security misconfiguration vulnerability 6.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/129106 for the current score.
7.6.0.9 CVE-2017-5644 IV96829 Open source Apache security defect 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/123699 for the current score.
7.6.0.9 CVE-2017-5662 IV97987 Open source Apache security defect 6.5 See https://exchange.xforce.ibmcloud.com/vulnerabilities/125198 for the current score.
7.6.0.9 CVE-2016-10006 IV97988 Backporting vulnerability 4.3 See http://www.cvedetails.com/cve/CVE-2016-10006/ for the current score.
7.6.0.9 CVE-2017-1558 IV98201 Cross site scripting vulnerability 7.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/131548 for the current score.
7.6.0.8 CVE-2016-8987 IV90527 Invalid permissions 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/119039 for the current score.
7.6.0.8 CVE-2017-1124 IV91546 Host header injection 2.9 See https://exchange.xforce.ibmcloud.com/vulnerabilities/121253 for the current score.
7.6.0.8 CVE-2017-1208 IV94320 XSS vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/123788 for the current score.
7.6.0.8 CVE-2017-1175 IV93630 SQL injection 6.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/123297 for the current score.
7.6.0.8 CVE-2017-1291 IV92968 Cross-site scripting 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/125152 for the current score.
7.6.0.8 CVE-2017-1292 IV93278 Backporting vulnerability 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/125153 for the current score.
7.6.0.8 CVE-2016-9976 IV91455 Backporting vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/120252 for the current score.
7.6.0.8 CVE-2016-8924 IV90310 Session highjacking vulnerability 5.6 See https://exchange.xforce.ibmcloud.com/vulnerabilities/118537 for the current score.
7.6.0.7 CVE-2013-4016 IV41871 SQL Injection 6.5 For more information on this fix, see this technote.
7.6.0.6 CVE-2016-5000
CVE-2014-9527
CVE-2014-3529
CVE-2014-3574
CVE-2012-0213
IV88002 Apache security defects 5.4 For more information on all of the CVSS scores, see this technote.
7.6.0.6 CVE-2016-5896 IV86986 Stack Trace Disclosure 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/115339 for the current score.
7.6.0.6 CVE-2016-6072 IV89097 Stack trace disclosure 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/117443 for the current score.
7.6.0.6 CVE-2016-5905 IV87109 Cross site scripting 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/115522 for the current score.
7.6.0.6 CVE-2016-5987 IV88845 Backporting vulnerability 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/116557 for the current score.
7.6.0.6 CVE-2016-5902 IV87115 Cross site scripting vulnerability 6.1 See https://exchange.xforce.ibmcloud.com/vulnerabilities/115512 for the current score.
7.6.0.5 CVE-2016-0393 IV83719 Stack trace vulnerability 5.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/112642 for the current score.
7.6.0.5 CVE-2016-0399 IV83853 Cross site scripting vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/112648 for the current score.
7.6.0.4 CVE-2015-5016 IV76198 Privilege escalation 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/106460 for the current score.
7.6.0.4 CVE-2015-7448 IV78202 SQL injection vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/108203 for the current score.
7.6.0.4 CVE-2015-7487 IV79220 Login vulnerability 4.1 See https://exchange.xforce.ibmcloud.com/vulnerabilities/108634 for the current score.
7.6.0.4 CVE-2016-0222 IV80376 Backporting vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/110004 for the current score.
7.6.0.4 CVE-2016-0262 IV81205 Cross site scripting vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/110605 for the current score.
7.6.0.4 CVE-2016-0289 IV81211 Privilege escalation 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/111298 for the current score.
7.6.0.3 CVE-2016-0399 IV83853 XSS vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/112648 for the current score.
7.6.0.2 CVE-2015-4944 IV74220 Cross-site scripting vulnerability 3.5 See http://xforce.iss.net/xforce/xfdb/104517 for the current score.
7.6.0.2 CVE-2015-4965 IV75595 Security misconfiguration vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/105641 for the current score.
7.6.0.2 CVE-2015-4965 IV75597 Security misconfiguration vulnerability 4.3 See https://exchange.xforce.ibmcloud.com/vulnerabilities/105641 for the current score.
7.6.0.2 CVE-2015-4967 IV75595 SQL injection vulnerability 5.4 See https://exchange.xforce.ibmcloud.com/vulnerabilities/105643 for the current score.
7.6.0.1 CVE-2015-0104 IV68500 Cross-site scripting vulnerability 4.9 See http://xforce.iss.net/xforce/xfdb/99582 for the current score.
7.6.0.1 CVE-2015-0108 IV68506 Cross-site scripting vulnerability 3.5 See http://xforce.iss.net/xforce/xfdb/99605 for the current score.
7.6.0.1 CVE-2014-6194 IV65948 Directory traversal 4 See http://xforce.iss.net/xforce/xfdb/98605 for the current score.

Behavior changes for Maximo Asset Management 7.6.0 feature packs

7.6.0.10 IJ02044 A new system property, mxe.app.asset.restrictAssetMoveModify, was added. When this property is set to 1, the user can only filter with statuses specified for the user's org or with non-specified statuses in the Move/Modify Assets > Select More Assets dialog. The default of this property is 0; to apply the IJ02044 fix, set the property to 1.
7.6.0.10 IJ01117

The new system property mxe.doclink.printURLAttachments was added to allow the user to edit the value of the Print attached document with report if printable type" checkbox on the Attachment Properties dialog for URL-type attachments. If the property is set to 1, the checkbox will be editable. If the property is 0, it will be read-only. This change affects URL-type attachments only. For file-type attachments, the checkbox will continue to be editable or read-only based on whether the file extension is supported for printing.

On the Create a URL Attachment dialog, the Print attached document with report if printable type?"checkbox has been made read-only via a change to the presentation xml. To make that checkbox editable, so that the user can select the print feature at the time the attachment is created, make the following change. In library.xml, remove inputmode="readonly" in the this tag:
<checkbox id="addnewattachments_www_2_1" label="Print attached document with report if printable type" dataattribute="printthrulink" inputmode="readonly" />

7.6.0.10 IJ02600 A system property was added to enable autocomplete on forms within Maximo. The property is called mxe.webclient.enableautocomplete. The default value is true, which meaning that autocomplete is enabled. To disable autocomplete, set the property's value to false.
7.6.0.10 IJ10051 A new property, webclient.statictext.sanitize, was added  to protect static text content against cross site scripting attacks. You can set the value to true to enable protection.
7.6.0.10 IJ04236

Manual changes are required for this fix.
Manual changes:
1. Navigate to <maximo_root>\tools\maximo\en\script and create a new script file named IJ04236.dbc
2. Open the new script in a file editor and paste the following:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE script SYSTEM "script.dtd">
<script author="VATTERB" scriptname="IJ04236">
  <description>Set Inspection table same-as attributes.</description>
  <statements>
      <modify_attribute attribute="ORGID" object="INSPECTIONFORM" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPECTIONFORM" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="ORIGINALFORMNUM" object="INSPECTIONFORM" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="CREATEDBY" object="INSPECTIONFORM" sameasattribute="PERSONID" sameasobject="PERSON"/>
      <modify_attribute attribute="CHANGEBY" object="INSPECTIONFORM" sameasattribute="PERSONID" sameasobject="PERSON"/>
 
      <modify_attribute attribute="ORGID" object="INSPECTIONFORMSTATUS" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPECTIONFORMSTATUS" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPECTIONFORMSTATUS" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="CHANGEBY" object="INSPECTIONFORMSTATUS" sameasattribute="PERSONID" sameasobject="PERSON"/>
  <modify_attribute attribute="REVISION" object="INSPECTIONFORMSTATUS" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>
 
      <modify_attribute attribute="ORGID" object="INSPQUESTION" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPQUESTION" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPQUESTION" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="LDKEY" object="INSPQUESTION" sameasattribute="LDKEY" sameasobject="LONGDESCRIPTION"/>
      <modify_attribute attribute="REVISION" object="INSPQUESTION" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>
 
      <modify_attribute attribute="ORGID" object="INSPFIELD" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPFIELD" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPFIELD" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="INSPQUESTIONNUM" object="INSPFIELD" sameasattribute="INSPQUESTIONNUM" sameasobject="INSPQUESTION"/>  
      <modify_attribute attribute="METERNAME" object="INSPFIELD" sameasattribute="METERNAME" sameasobject="METER"/>
      <modify_attribute attribute="REVISION" object="INSPFIELD" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>
 
      <modify_attribute attribute="ORGID" object="INSPFIELDOPTION" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPFIELDOPTION" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPFIELDOPTION" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="INSPQUESTIONNUM" object="INSPFIELDOPTION" sameasattribute="INSPQUESTIONNUM" sameasobject="INSPQUESTION"/>  
      <modify_attribute attribute="INSPFIELDNUM" object="INSPFIELDOPTION" sameasattribute="INSPFIELDNUM" sameasobject="INSPFIELD"/>
      <modify_attribute attribute="REVISION" object="INSPFIELDOPTION" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>  
 
      <modify_attribute attribute="ORGID" object="INSPECTIONRESULT" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPECTIONRESULT" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPECTIONRESULT" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="CREATEDBY" object="INSPECTIONRESULT" sameasattribute="PERSONID" sameasobject="PERSON"/>  
      <modify_attribute attribute="REVISION" object="INSPECTIONRESULT" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="ASSET" object="INSPECTIONRESULT" sameasattribute="ASSETNUM" sameasobject="ASSET"/>
      <modify_attribute attribute="LOCATION" object="INSPECTIONRESULT" sameasattribute="LOCATION" sameasobject="LOCATIONS"/>      
 
      <modify_attribute attribute="ORGID" object="INSPRESULTSTATUS" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPRESULTSTATUS" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="RESULTNUM" object="INSPRESULTSTATUS" sameasattribute="RESULTNUM" sameasobject="INSPECTIONRESULT"/>
      <modify_attribute attribute="CHANGEBY" object="INSPRESULTSTATUS" sameasattribute="PERSONID" sameasobject="PERSON"/>  
 
      <modify_attribute attribute="ORGID" object="INSPFIELDRESULT" sameasattribute="ORGID" sameasobject="ORGANIZATION"/>
      <modify_attribute attribute="SITEID" object="INSPFIELDRESULT" sameasattribute="SITEID" sameasobject="SITE"/>
      <modify_attribute attribute="INSPFORMNUM" object="INSPFIELDRESULT" sameasattribute="INSPFORMNUM" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="INSPFIELDNUM" object="INSPFIELDRESULT" sameasattribute="INSPFIELDNUM" sameasobject="INSPFIELD"/>  
      <modify_attribute attribute="REVISION" object="INSPFIELDRESULT" sameasattribute="REVISION" sameasobject="INSPECTIONFORM"/>
      <modify_attribute attribute="RESULTNUM" object="INSPFIELDRESULT" sameasattribute="RESULTNUM" sameasobject="INSPECTIONRESULT"/>
      <modify_attribute attribute="INSPQUESTIONNUM" object="INSPFIELDRESULT" sameasattribute="INSPQUESTIONNUM" sameasobject="INSPQUESTION"/>  
      <modify_attribute attribute="ENTEREDBY" object="INSPFIELDRESULT" sameasattribute="PERSONID" sameasobject="PERSON"/>  
  </statements>
</script>

3. Navigate to <maximo_root>/tools/maximo/internal
4. Manually run the script using the command: runscriptfi -fIJ04236

-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236
-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236
-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236
-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236
-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236
-Navigate to <maximo_root>/tools/maximo/internal
-Manually run the script using the command: runscriptfile -fIJ04236

7.6.0.9 224568 You can delete Maximo Linear record information directly from any map that displays a layer of Linear data.  Use the Identify tool to locate and select a Linear feature on the map, and then delete the Linear segment. The Maximo record will be updated to reflect your changes.
7.6.0.9 IV97910 A new max message was added:Message Group: reports
Message Key: exceptionOnServer
Message ID: BMXAA9536E
Message: There was an exception on the server. Check your report parameter values, or contact your system administrator, who can find additional details in the server log.
To add this message manually, use the following steps:
1. Go to Database Configuration
2. Action Messages. Click New Row; Message Group: reports; Message Key: exceptionOnServer; Message ID Prefix: BMXAA; Message ID: BMXAA9536E (enter in table window); Value: There was an exception on the server. Check your report parameter values, or contact your system administrator, who can find additional details in; the server log.  Leave the rest of the values as default.
7.6.0.9 IV96789 A new relationship for RESCHEDASSIGN from WORKORDER to the non-persistent RESCHEDASSIGN object. There is no SQL Where clause associated with this relationship. It is used by the Reschedule/Unassign Assignments dialog.
The Reschedule/Unassign Assignments functionality in Work Order Tracking now has messaging to explain the outcome of execution.
1. On the List tab, when the Reschedule the assignments property is checked, there are two possible outcomes. If all assignments on all work orders are successfully rescheduled, the following message will display in the status bar:
BMXAA9539I - All assignments have been successfully rescheduled.
If all assignments on all work orders are not successfully rescheduled, a system message dialog will display. The message will indicate partial success and will list all the assignments that were unassigned as follows:
Partial success rescheduling assignments.
BMXAA9543I - BIRD could not be rescheduled on work order 1656 and was unassigned due to insufficient availability.
BMXAA9543I - ADAMS could not be rescheduled on work order 1657 and was unassigned due to insufficient availability.
2. When on an individual record with Reschedule the assignments property checked, there are two possible outcomes. If all assignments on the work order are successfully rescheduled, the following message will display in the status bar:
BMXAA9539I - All assignments have been successfully rescheduled.
If all assignments on the work order are not successfully rescheduled, the following message will display in the status bar:
BMXAA9542I - Partial success rescheduling assignments. The number of assignments unassigned due to insufficient labor availability is 2.
3. On both the List tab and on an individual record with the Reschedule the Assignments property unchecked, the following message will display in the status bar when the all assignments have been unassigned:
BMXAA9541I - All assignments have been successfully unassigned.
7.6.0.9 IV93313 A new security option, Set Report File Export Options, was added to the Report Administration application. After the option is granted, a user can open the Report File Export Options dialog and choose to disable file types. Only file types that have the Display property set to true will appear in the Email section of the request page and the Schedules tab of the report list. The request pages must be generated after you change the available file types.
The REPORTEMAILFILE object was added to store the information displayed in the dialog.
This enhancement only applies to the file type selections included in the report dialogs generated from the Report Administration application. A manual change is required to remove file types from the View Scheduled Reports and Schedule Details dialogs. Use the following process to update those dialogs:
From Application Designer, select Export System XML. Export LIBRARY and open in a text editor.
2. Search the file for the dialog having id viewschconf. Under the Email section, modify the dialog to remove the radio buttons for the unwanted file type(s).
3. Save and reimport library.xml.
4. Open the REPORT application and repeat the steps above for dialog having id VIEWSCHREP in report.xml.
7.6.0.9 IV94667 A new system property called mxe.filter.assets.bysite is introduced.
A new system property mxe.filter.assets.bysite is added.
When the property is set to 1 - it will filter assets display only assets belonging to siteid of the ticket.
When it is set to 0 - all the assets are displayed irrespective of the siteid of the ticket.
7.6.0.9 IV88268 A new system property, mxe.dm.dbhostoverride, was added for deployment on Oracle RAC. This property should be set to a host name that will be used by regardless of which Oracle Database node is currently connected.
7.6.0.9 IV99317 A new system property, mxe.int.flatfileextension, was added that allows you to specifying the format of flatfiles exported through Application Export.
7.6.0.9 IV96293 A non-persistent attributes, ATTRIBUTEEVENT, EVCONTEXT, was added and the EVENTTYPE attribute was added to MAXINTOBJCOLS for the DMLAUNCHPOINT integration object structure's SCRIPTLAUNCHPOINT object.
7.6.0.9 IV99572 Add the system property to disable the circular dependency validation
7.6.0.9 IV95479 Added a system property mxe.app.workorder.allowHistoryWO. Default value is 0 - the old behavior. Value 1: user can manually enter a closed/cancelled wo under the related records table window.
7.6.0.9 IV95834 Added AUTHENTICATION_METHOD property to the MXCOGNOS End Point. values = (LDAP, MXCSP (default if left blank))
7.6.0.9 IV96781 Change the domain uses in order to fix the problem with the language and default value set.
7.6.0.9 IV95635 Changes were made so that the Services Receipt Total cost is consistent with the Material Receipt Total cost in the Receiving application.
1. For Services that require receipts, variances will not be included the Receiving Application, Services Receipts tab, Received Costs attribute.
2. For Services that do not require receipts, the Receiving Application, Services Receipts tab, Received Costs attribute would continue to have the total including the variances. This is because the receipt and variance both occurred at the same time, during the invoice process.
7.6.0.9 IV95258 Create system proprety mxe.db.sqlserverBracketQBE to control replacement of '[' in SQLServer QBE.
When true, replaces '[' encountered after 'like' with '[[]' in QBE. Only applicable to SQLServer. Default value true.
7.6.0.9 IV98900 Database Changes:
V7609_27.dbc was added.

A new property, mxe.po.validateCreditGLAcctApprovePO was added to validate POLine credit GL account against Vendor account and correct when PO is approved.
The default value is set to 0 to not to validate POLine credit GL account.
When the mxe.po.validateCreditGLAcctApprovePO property is set to 1, the logic will validate POLine credit GL account when PO is approved.

Manual Change:
Change mxe.po.validateCreditGLAcctApprovePO value to 1 to validate POLine credit GL account against Vendor account and correct when PO is approved.
Go To System Properties, find mxe.po.validateCreditGLAcctApprovePO, and change the global value to 1. Save the change and do a Live Refresh. After the Live Refresh, the current value is 1.
7.6.0.9 IV96965 Fixed the algorithm to check circular dependencies.
7.6.0.9 IV96422 Functionality Change:
In the Create Communications dialog, Send From can be configured via a new system property to be read-only. The 'Send From' value will default to the current user's email. If the user does not have a valid email address, 'Send From' will default to the System Administator's email address (specified in system property mxe.adminEmail).
Property Change:
Added new system property mxe.commlog.SendFromEditable to control whether or not 'Send From' is editable in the 'Create Communications' dialog. The script V7609_07 will add this property with a value of '1' so that 'Send From' will remain editable. The System Administrator will have to explicitly modify this to change behavior from what it has been previous to this fix.
User Interface Change:
In the 'Create Communications' dialog, 'Send From' will no longer be editable if the new system property mxe.commlog.SendFromEditable is set to '0'. If this vaue is set to '0' and there is not a valid email address for the current user or the System Administrator (specified in system property mxe.adminEmail), the 'Create Communications' dialog will not load. Instead the user will see an error message dialog containing the following message:
MessageID: BMXAA9507E
Value: Unable to create a communication without a 'Send From' email address.
Explanation: 'Send From' is a required field in the Create Communication dialog. If the current user does not have a valid email address, the system will use the System Administrator administered mxe.adminEmail address. If a valid email address cannot be obtained from either of these sources, a communication cannot be sent.
Response: Establish a valid email for the current user in the Users application, or ask the System Administrator to set the system property mxe.adminEmail in the System Properties application.
7.6.0.9 IV95229 Inbox portlet headers will not be clickable for related attribute columns. Sort is not supported for these columns.
7.6.0.9 IV98894 PMWoGenCronTask instances can be configured to run for any number of instances. This new functionality is controlled by the new cron task parameter siteid. This parameter can be set to one or more sites using a comma-separated list. If the parameter is left blank, the cron task runs for all sites as was the behavior prior to this change.

Additionally, PMWoGenCronTask instances can be filtered by setting the new parameter instance_pm_sqlwhere. This will further refine which PMs are processed for the site or sites specified in the siteid parameter. For example, the PMWoGenCronTask for sites BEDFORD and NASHUA can be broken into multiple cron tasks by priority:

pmwogen1 --> siteid = bedford,nashua
instance_pm_sqlwhere = 'priority<=1'
pmwogen2 --> siteid = bedford,nashua
instance_pm_sqlwhere = 'priority>1 and priority<3'
pmwogen3 --> siteid = bedford,nashua
instance_pm_sqlwhere = 'priority>3'
7.6.0.9 IV99251 Sets DOCLINKS.APP and DOCINFO.APP attribute metadata as follows:
SAMEASATTRIBUTE = 'APP'
SAMEASOBJECT = 'MAXAPPS'
Length = MAXAPPS.APP.LENGTH
7.6.0.9 IV96998 When the user navigates to the Failure Reporting tab, the work order is saved if the Problem Code field has been modified. This will insure that the Failure Report is correctly reconstructed based on the new Problem Code.
7.6.0.9 IV94430 When you configure a result set portlet, the Application must be selected before the Query. Initially, until an application is selected, the Query field is read-only. It will become editable after you select the application.
Additionally, validation has been added to the Query field, so that only a query that is associated with the selected application can be chosen. To change the query value to a query that is associated with a different application, the application must be changed first.
7.6.0.8 IV90039 A new error message, BMXAA9459E, was added to the database.
7.6.0.8 IV90730 A new property, mxe.app.sla.genEscSlaUseExists, was added. When the property is set to true or Y, will use exists when generating escalation SQL for service level agreements.
7.6.0.8 IV93428 A new property, mxe.directprint.DuplexDisplay, was added. This property displays each attachment on a new front page when duplex printing enabled. New functionality was added to attachments on the front page when duplex printing is enabled.
7.6.0.8 IV93935 A new property, mxe.report.adhoc.UserSelectDynamicQuery, was added. When this property is set to true, a new checkbox will appear on the Style tab of the Ad Hoc Report dialog box. The field is named Add Dynamic Application Query to Saved Report at Runtime and can be used to override the way the dynamic query is applied to ad hoc reports. In addition, the Report Administration application was updated to display your selection on the report details. Two new sections were created: Cognos Report Settings and Ad Hoc Report Settings. They are positioned over the existing Settings section and display conditionally based on the report type.
This functionality introduces complex scenarios. You should consult the updated Ad Hoc Reporting and ROS Guide before implementing.
7.6.0.8 IV90277 A new property, mxe.wf.novalidate.assignment, was added. When this property is set to true or Y, validation on workflow assignments is disabled.
7.6.0.8 IV90393 A new system property, mxe.db.validateMaxRows, was added with the V7608_02.dbc script. This property defines the maximum number of rows returned when validating a query.
7.6.0.8 IV92401 A new system property, mxe.int.queuefileseparator, was added to system properties. This property specifies the separator character used when creating name of view queue file. The default separator character is underscore: &quot;_&quot;. This property should be changed to a different character if the underscore character is used in external system names or interface names. The character may not be a reserved file character. https://msdn.microsoft.com/en-us/library/aa365247
7.6.0.8 IV91215 A new warning message was added. The message will be displayed when a user deselects the &quot;Public?&quot; checkbox in the View/Manage Queries dialog, if that query is being used as a default query by other users. The warning indicates that setting the query private also will delete the same query for any other users who have that query set as their default query.
7.6.0.8 IV90255 Changes previously done to the commlog relationships of parents workorders and escalations were removed. The commlog relationship of parent woactivity was removed.
7.6.0.8 IV85105 Escalation point time intervals only apply to the elapsed time interval during active shifts. Before this fix, the shifts were not considered when the elapsed time interval pushed escalations to the next day.
7.6.0.8 IV84482 If type ahead is enabled on a field, smart fill is turned off. This fix prevents you from turning on smart fill if type ahead is enabled.
7.6.0.8 IV91545 If user is logged into two or more sessions then all sessions are logged out when changing their password.
7.6.0.8 IV89162 In cases where there is a child table associated by relationship to a parent table, if the user changes the row on the parent table, the child table will be reset to display it's rows starting from the first row.
7.6.0.8 IV92171 In the Users Application, server sessions are displayed in a separate tab on the Manage Sessions dialog box. Server sessions do not appear in the same list as user sessions.
7.6.0.8 IV93427 A new property, mxe.directprint.Wait1and2Jobs, was added. The property adds a number of seconds to wait between the 1st and 2nd direct print jobs.
7.6.0.8 IV85822 Obsolete objects that interfere with upgrades were removed from the MAXINTOBJCOLS object.
7.6.0.8 IV94052 Removed a correlation feature from scripting as debug logging for scripting achieves the same results.
7.6.0.8 IV94289 The ability to configure the list of printable file attachment extensions is no longer available. The mxe.doclink.doctypes.printablefileextensions system property was removed from the product.
There are thousands of file types on the market today. Enabling the printing of each of these file types, along with its preconfigured report, within a Maximo session is not feasible and can cause numerous errors. Adding configurable file type attachments to the Direct Print with Attachment functionality causes the process to fail and consume system resources.
The reporting feature of direct print with attachments enables the printing of non-configurable file types only including: pdf, csv, txt, gif, jpg, png. Additionally, in certain circumstances, Microsoft Office file types can be printed as noted in this reference document: http://www-01.ibm.com/support/docview.wss?uid=swg21986050. Support for additional file types will need to be added via enhancement request in the future.
7.6.0.8 IV93093 The AUTHROLE table was added. The AUTHROLEUSER was dropped and added again.
7.6.0.8 IV87677 The commlog relationship for parent work order activity was removed.
7.6.0.8 IV94422 The inbound processing class, psdi.iface.app.wf.MaxWFProcess was added for MXWFPROCESS object structure.
7.6.0.8 IV90664 The mxe.db.UseSiteListInQuery property was expanded to be INTEGER and live-refresh enabled. No behavior changes for value 0 or 1. When the value is set to 2, site where clauses use an in clause with subselect.
7.6.0.8 IV89647 The Originating Record window in the Follow-Up section of the Work Order Tracking application is now compatible for records of class Incident, SR, and Problem.
7.6.0.8 IV92275 The where clause of the SPAREPART_NOSITE relationship was updated to:
itemnum=:itemnum and itemsetid=:itemsetid and assetnum in ( select assetnum from asset where ( moved=:no and siteid=sparepart.siteid and status not in (select value from synonymdomain where maxvalue in ('DECOMMISSIONED') and domainid='LOCASSETSTATUS'))) and :sitefiltering
7.6.0.8 IV93783 The where clauses for ASSETSPEC, ASSETFEATURESPEC, LOCATIONSPEC, WORKORDERSPEC, JOBPLANSPEC, and JOBTASKSPEC were updated.
7.6.0.8 IV90310 Three properties were added to support invalidating LTPA Tokens.
mxe.ltpatoken.kill - Invalidate LTPA token on logout. Default value="1"
mxe.ltpatoken.name - LTPA cookie name. Default value="LtpaToken2"
mxe.ltpatoken.timeout - LTPA timeout value in minutes. Default value="1440"

Added the ltpatoken table to database.
7.6.0.8 IV90342 Users may notice a change in the spacing of section columns. The change made for this APAR allows the control property useproportionalcols to be used to distribute column width equally across the page. use proportionalcols is true by default. It can be set to false on the section tag in the presentation HTML.
7.6.0.8 IV89195 Validation has been added to the File (URL) field on the Create Attachment dialog box. A message is now displayed when you click the OK button on the dialog box and the dialog will not close until a value is entered in that field.
7.6.0.7 IV91545 If user is logged into two or more sessions then all sessions are logged out when changing their password.
7.6.0.7 IV90310 Three properties were added to support invalidating LTPA Tokens.
mxe.ltpatoken.kill - Invalidate LTPA token on logout. Default value="1"
mxe.ltpatoken.name - LTPA cookie name. Default value="LtpaToken2"
mxe.ltpatoken.timeout - LTPA timeout value in minutes. Default value="1440"

Added the ltpatoken table to database.
7.6.0.7 IV96998 You save work orders when the Problem Code is set in the Select Failure Codes dialog on the Failure Reporting tab. Saving work orders must occur whenever the Problem Code is set for the proper display of the Failure Codes table window on the Failure Reporting tab. After implementing the manual change for this interim fix, the work order will be saved when you navigate to the Failure Reporting tab.
7.6.0.6 IV84773 1. DATABASE CHANGES
Added attribute WFONASSETGEN to non-persistent object MAXVARINPUT.

2. FUNCTIONALITY CHANGE
Workflow can now be started as assets are being created from an asset template in the Asset Templates application. The mechanism for this is the same as already exists for workflow execution on objects that are not the main object for the current application, for example, maxvars.varname WFONPMGENERATION ("Work Orders on PM Generation" in the Workflow Processes to Initiate Automatically section of the Workflow Options dialog in the Organizations application) used to route workflow for work orders created during PM work order generation.

3. PROPERTY CHANGE
Added site-level maxvar WFONASSETGEN to specify workflow to execute as assets are being created from an asset template.

4. USER-INTERFACE CHANGE
The Assets on Creation From Asset Template textbox has been added to the Workflow Processes to Initiate Automatically section of the Workflow Options dialog in the Organizations application. This is to facilitate the routing of workflow on new asset creation from within the Asset Templates application. The value is site-level and corresponds to the site that is selected in the Sites table window in the Workflow Options dialog. Each site can have its own workflow.
7.6.0.6 IV87984 A new property, mxe.int.entservicerespcontenttype, was added. This property controls whether you use the POST request's accept header to set the content type of the subsequent response.
7.6.0.6 IV87746 A new property, webclient.richtext.convertNonBreakingSpace, was added to convert non-breaking space characters (0x0A) to '&nbsp;' in rich text fields.
7.6.0.6 IV87142 A new script, V7606_31, was added to set the Same As property on Start Center name attributes to keep the field lengths consistent.
7.6.0.6 IV85371 A new setting for the DISPLAYDATE_FR property was added. By default the property uses the dd.MM.yy format to display calendar dates. For example, to use short month format, change the value to dd-MMM-yyyy
7.6.0.6 IV85212 A new system property, mxe.app.assetcat.truncateTicketDescription, was added to allow for the truncation of Service Request, Problem, and Incident descriptions that are automatically generated when a class structure is applied and the value is too long. The default behavior is to leave the description blank if the value is too long. This is consistent with behavior prior to the introduction of this new property. If this value is set to 1, the description will be truncated.

A new system property, mxe.app.assetcat.truncateTicketDescriptionUpdate, was added to allow for the truncation of Service Request, Problem, and Incident descriptions that are automatically updated when specifications on previously applied class structures are modified if the new value is too long. The default behavior is to restore the previous, pre-specification update description if the updated value is too long. This is consistent with behavior prior to the introduction of this new property. If this value is set to 1, the updated description will be truncated.

The descriptions affected by these two new properties when they are set to 1 is the value that appears in the Summary field of the Service Request Details, Problem Details, and Incident Details sections of the Service Requests, Problems, and Incidents applications.
7.6.0.6 IV85692 A new system property, mxe.webclient.leavetooltipopen was added. When this property is set to 0 (default) the tool tip dialog box opens for a few seconds, and then closes. When this property is set to 1, the tool tip dialog box remains open until you click outside of the dialog box.
7.6.0.6 IV85748 A new system property, webclient.portletwraplength was added. When this property is set to zero (default), text in portlet columns does not wrap. If the property is set to any integer greater than zero, that value will be used as the wrap length for portlet text.
7.6.0.6 IV85563 Database Changes:
V7606_07.dbc was added.

A new property, mxe.app.receiving.countOfRecordsForCommit, was added to improve the processing of large amount of receipts and transfers.

The default value for the property is set to 50 based on a typical environment/memory.
You can set the property to a smaller number if their environment/memory is smaller.

Manual Change:
Change mxe.app.receiving.countOfRecordsForCommit value to a value other than default value.
For example, change mxe.app.receiving.countOfRecordsForCommit to 20.

Go To System Properties application and search for the mxe.app.receiving.countOfRecordsForCommit. Change the global value to 20.
Save the change and do a Live Refresh for this property. After the Live Refresh, the current value of 20 will be used.
7.6.0.6 IV81803 Failed expression validation attempts against dummy_table are now logged as errors, but no longer include a stack trace. This allows notification of potentially faulty conditions without the negative impact on log readability. The presence of these error messages generally indicates that one or more attributes in the expression should be prefixed with a colon so it can be replaced with the value for the current object.  If you configure a service logger for PARSER and set it to INFO you will see a stack trace that indicates where the validation attempt was initiated.
7.6.0.6 IV87110 If you use a custom logging properties file, you must specify mxe.logging.rootfolder in the maximo.properties file.
7.6.0.6 IV86501 Put back the menu bar containing the 'Advanced Search', 'Save Query' and 'Bookmarks' menu items that was accidentally removed from the Security Groups application during the transition to 7.6.x release
7.6.0.6 IV87993 The Asset Health escalation (ASSETHEALTH) is set to run daily for all environments. It is deactivated only for environments where Asset Health Insight is not installed.
7.6.0.6 IV84870 The Asset Manufacture field is now validated. In asset.xml, Manufacture field. replace smartfilloff="true" with synchronous="true".

Manual fixed steps:

1) Go To System Configuration->Platform Configuration, Application Designer
2) Find Asset Application. Go to Asset tab.
3) Under Purchase Information section, find Manufacture field.
4) Open the Manufacture Property (right mouse click or click on Control Properties icon)
5) Go to Advanced tab.
UNCHECKED "Turn Smart Fill Off?" flag.
CHECKED "Always Synchronous? flag.
Exit the property dialog and Save.
7.6.0.6 IV84473 The Select Value dialog box for the Display By field now displays all available fields for the object/application on the Field Configuration tab. The dialog box is not limited to only those fields that are selected for display on the result set portlet.
7.6.0.6 IV87641 To address this issue, the property mxe.report.cognos.querymode has been reintroduced. Change the value to &quot;dynamic&quot; to support dynamic query mode.
7.6.0.6 IV79795 Two new relationships were added:
Name: SPLLTAGOUTS_RELASSET  Parent: SPLEXICONLINK   Child:SPLEXICONLINK
Name: SPLLTAGOUTS_RELLOC     Parent: SPLEXICONLINK   Child:SPLEXICONLINK
The SPLLTAGOUTS_RELASSET relationship gets the tagouts for the current hazard's related asset. Zero or more tagouts are returned.
The SPLLTAGOUTS_RELLOC relationship gets the tagouts for the current hazard's related location. Zero or more tagouts are returned.
7.6.0.6 IV85769 When the sigoption is deleted, the ctrlgroup record in the database is now also removed.
The sigoption is not removed from the Signature Option field in the Control Properties dialog. All instances of the sigoption will need to be removed manually from the application XML.
7.6.0.6 IV86512 When the system property webclient.richtext.sanitize is set to 1, an XML file called sanitizePolicy.xml, in the properties folder, is used to specify the policy used by the sanitizer. That XML file can be customized depending upon what restrictions you want to place on rich text input.
7.6.0.6 IV87458 You can now implement file type scanning when you upload an attached document. The class must implement com.ibm.tivoli.maximo.doclink.AbstractFileVerification and is registered with the mxe.doclink.FileValidationClass system property.
7.6.0.6 IV86990 You no longer need to set the USERNAME end point property for the MXCOGNOS end point when MXCSP is used for publishing packages.
7.6.0.5 IV83958 A new argument, -b, was added to the updateRichText script. If the script is run with -b, then both new line and carriage return characters will be converted to BR tags in the resulting rich text data. Without the -b argument, only new line characters are converted to BR tags.
7.6.0.5 IV78524 A new property, mxe.app.labor.allowMultipleActLabUpdates, was added. The default value is set to 0. To make this function work, you need to set this property to 1. Setting this property to 1 causes work order actual updates to not trigger an outbound work order integration message even though the work order Cost fields were modified.
7.6.0.5 IV83946 Previously, if the Order By value on the portlet query did not match or contain the Group By attribute, no sort order was applied to the query that returns the graph data. This change removes that logic and always uses the Group By attribute in the Order By clause. For example, if the chart is displayed by status, then it sorts by status in all cases.
7.6.0.5 IV83303 The error dialog box that appears on the List tab when you attempt to Close or Complete work orders without all Dynamic Check Points entered has been edited for clarity. The status change itself is still disallowed, both before and after error dialog change.
7.6.0.5 IV83536 The KPI name in the KPI graph and list portlets is truncated to prevent horizontal scrolling when the webclient.shortenportlettext system property is set to true.
7.6.0.5 IV83961 The To Bin field is no longer a required field in the Receiving application for LOT items.
7.6.0.5 IV83986 We no longer treat :DATE, :DATETIME and :HOSTNAME the same as &DATE&, &DATETIME& and &HOSTNAME&.  Each :<word> will properly resolve to the value of the attribute <word> in the current object.
7.6.0.5 IV81883 When a file that is a non-printable file type is attached to a record and you do not uncheck the Print Attached Document With Report if Printable Type? property, an error no longer prevents the attachment from being saved. Instead, a slightly different message is displayed that notifies you that the print option will be ignored and the attachment is saved with the print option disabled.
7.6.0.4 IV77474 A database script, V7604_03.dbc, was added for Same As attributes.
7.6.0.4 IV79335 A new database script, V7603_13.dbc, was added to improve performance.
7.6.0.4 IV81205 A new property, webclient.richtext.sanitize, was added to protect rich text content against cross site scripting attacks. You can set the value to true to enable protection.
7.6.0.4 IV76949 A new system property, webclient.allowMultipleCardinality was added. This property has a default value of 0.  If the property is set to 1 , all child objects will be included in the Object List tree regardless of cardinality.  Please note: If an attribute from a MULTIPLE cardinality child object is included in a result set portlet, the data displayed in the portlet will only display the first record in the child mboset, although the relationship to the parent is 1:n.
7.6.0.4 IV79224 A property, mxe.app.assetcat.includesDecommissioned, was created to return decommissioned assets from Attribute Searches in the Assets application. You can change the value of the property to 1 to see decommissioned assets in the list tab after Attribute Search.
7.6.0.4 IV73893 A relationship from the MAXINTOBJECT table to the MAXINTOBJALIAS table was added.  This relationship can be used to find all alias columns for a MAXINTOBJECT. The resulting set contains zero or more objects.  A system property, mxe.int.checkdupalias, was added. The property must be added and set to true to delete existing aliases.
7.6.0.4 IV79445 Added field validation class for PLUSCDSINSTR.INSTROUTRANGEEU.
7.6.0.4 IV80087 Background mode added to Change Status dialog for the Asset application in the core product.
7.6.0.4 IV80085 Background mode added to Move/Modify dialog for the Asset application in the core product.
7.6.0.4 IV80493 For SQL Server users, a new system property, mxe.app.assetcat.addAttributeforSQLServer, was created for the code to use direct insert statements for classifications that belong to a large amount of asset records. This improves performance significantly. The default value is 0. You can change the value to 1 to improve the performance.
7.6.0.4 IV80614 I added the initialize method on SelectTicketBean class.
7.6.0.4 IV79594 modified the where clause when PUBLIC filter used
7.6.0.4 IV61448 NO change in the behavior, just a normal fix.
7.6.0.4 IV81329 One field class was trying to get a mboset tha does not exit for the object it was missing do a check for know if the mbo was item or not before get the mboSet (DEPRECIATION).
7.6.0.4 IV79656 Report request page parameter lookups not configured as multiselect only allow a single value to be selected. The lookup dialog no longer contain check boxes that are part of mutiple selection functionality unless the parameter has REPORTLOOKUP.MULTILOOKUP set to true.
7.6.0.4 IV77168 Staged Balance displays on the report and is factored into the Extended Cost equation
7.6.0.4 IV80206 The MATUSETRANS.POSITIVEQUANTITY field now has SAMEASOBJECT=MATUSETRANS and SAMEASATTRIBUTE=QUANTITY.
7.6.0.4 IV78777 Two new system properties, mxe.workorder.rollbackstatus and mxe.workorder.additionalErrorHandling, were added. Both have a default value of 0.  Setting mxe.workorder.rollbackstatus to 1 causes every work order in a tree to roll back if any child work order throws an error while changing status.  Setting mxe.workorder.additionalErrorHandling to 1 causes error information from non-MXException-type exceptions to be included in a System Message.
7.6.0.4 IV78565 V7604_14.dbc
7.6.0.4 IV79802 When you select check boxes in the Data Sheet Template application, the validation and UI response is now immediate.
7.6.0.3 IV76802 A new action, Manage Commit Access, was added to the Scheduler application to define persons and groups to commit the schedule. The Manage Commit Access action is available only for the owner of the schedule project.
7.6.0.3 IV78567 A new property, mxe.skd.optimization.craftrate, was added to the database.
7.6.0.3 IV73918 A new property, mxe.webclient.proxyLoginStringCheck was added that specifies a certain string in the response that is used to indicate a redirect to the WebSEAL login page. The default value is "pkmslogin".
7.6.0.3 IV75799 A new system property, webclient.shortenportlettext, was added to the database. The default value is false. If the property is set to true, text in RESULTSETPORTLET columns are truncated. This prevents horizontal scrolling in the start center.
7.6.0.3 IV77570 Added issueunit in Matusetrans table.
7.6.0.3 IV77842 Database Change:
A persistent yorn attribute, STAYCURRENTAPP, was added to the WFINTERACTION object.
This new attribute is used in the work flow interaction node dialog to override switching to the application specified on the interaction node when the interaction node application differs from the current application. The default value is false so that by default the interaction node behaves as it did before the introduction of this attribute flag in 7.6.0.3 and 7.5.0.10.

Functionality Change:
Work flow interaction nodes can now be configured to remain in the current application when the application on an interaction node differs from the current application. The default behavior is to switch to the interaction node application but this can be overridden by selecting the Stay on Current App check box that was added to the interaction node dialog.

User Interface Change:
A new check box titled Stay on Current App was added to the interaction node dialog. This is bound to the non-persistent SHOWWFINTERACT.STAYCURRENTAPP attribute in the dialog and is stored in the persistent WFINTERACTION.STAYCURRENTAPP attribute in the database. When this box is cleared, behavior is unchanged from releases before 7.6.0.3 and 7.5.0.10. When this box is checked, the user will remain in the current application when the interaction is processed even if the interaction node application differs from the current application.
7.6.0.3 IV76294 Database Changes:
Added V7603_30.dbc.
The mxe.reorder.calculatepoqty property was added to avoid correlated updates when you calculate purchase order quantity. The default value for this property is 0 to use original update sql. If mxe.reorder.calculatepoqty property is set to 1, the logic will avoid correlated updates to calculate purchase order quantity.

Manual Change:
Change mxe.reorder.calculatepoqty value to 1 to avoid correlated update to calculate Reorder POQTY.

Go To System Properties,
find mxe.reorder.calculatepoqty.
Change Global value to 1. Save. Do Live Refresh. After Live Refresh, Current value is 1.
7.6.0.3 IV74323 Filter and sort options were removed from the Workflow Designer Select Member Node dialog.
7.6.0.3 IV76610 Functionality Change:
Inventory kit functions were enhanced. Now, when a kit is disassembled, you have the option of distributing a kit's components into the kit's bin . Previously, the kit components could only be added to each component's default bin when the kit was disassembled. If a component did not have a default bin, any existing bin for the component was used. The previous functionality remains the default functionality.

Property Change:
The new system property, mxe.app.inventor.useSourceBinForInvKitAction, was added to distribute a kit's components into the kit's bin when the kit is disassembled. This property is in the System Configuration > System Properties application.
7.6.0.3 IV74201 In the Tech Tablet application, on the Results tab in Work Log section, the Long Description field was changed from rich text to plain text.
7.6.0.3 IV76005 New error message created: "BMXAA9185E - Report filter exceeds maximum length for scheduled reports. Reduce the length of the report criteria or run the report immediately."
7.6.0.3 IV67743 On the Labor application's Extend / Renew Qualification dialog, users will now be allowed to enter a New Effective Date which is earlier than the Current Effective Date.
7.6.0.3 IV78135 Previously an inactive PM could be applied to a condition monitoring measure point. This would be caught during work order generation from the measure point. The work order would not be created due to the PM being inactive. This rule re: the addition of a PM on a measure point should be consistent with the rule re: the addition of a job plan. One should not be able to add an inactive PM to a measure point. The fix prevents inactive PMs from being added to condition monitoring measure points.
7.6.0.3 IV76910 The Custom MSGID was renamed to avoid duplicate messages.  The new processing class for the DMMAXMESSAGES object structure is called psdi.dm.procclass.DMMaxMessagesIn.
7.6.0.3 IV78490 The percentage availability was added to the Capacity Planning dialog.
7.6.0.3 IV75207 The Rich-Text Editor applies the styles from the extended.css stylesheet.
7.6.0.3 IV77628 The Where clause and the Remarks of the NOTIFICATIONS relationship in MAXRELATIONSHIP table for parent WFACTION and child WFNOTIFICATION were changed. Now when you create a revision, duplicate records are not inserted.
7.6.0.3 IV76999 When the Bill To, Ship To, or reply-to address code is updated for a PO, PR, or RFQ, the Attention field is now updated with the contact specified in the Organizations application.
7.6.0.3 IV74015 You can no longer add or delete attachments to Job Plans with an internal status of REVISED or CANCELLED.
7.6.0.2 IV71969 A link was added in MAXDOMINALINK for the PERSON.CALTYPE domain.
7.6.0.2 IV74714 A new maxmessage was added with a group of configure and a key of RelationshipAlreadyExists. Now, when this relationship occurs, the following error message is displayed: Relationship {0} already exists between base object {4} and child object {2}. As object {3} is a view, it inherits from object {4}; either a different relationship name must be used or the child object {1} must be changed to {2}.
7.6.0.2 IV72581 A new property, ALWAYSREFRESH, was added to table details to support type-ahead filter domain fields in the table details section. To activate this property, add alwaysrefresh=true to table details.
7.6.0.2 IV74220 A new property, webclient.richtext.discardTags, was added. This property is a comma delimited list of html tags that are discarded from rich text fields. By default, the following tags are discarded: script, object, embed, and iframe.
7.6.0.2 IV73278 A new system property, mxe.crontask.runonschedule, was added. When the property is set to 0, missed scheduled cron tasks are run immediately and then at the next scheduled time. When the property is set to 1, missed scheduled cron tasks are not run until the next scheduled time.
7.6.0.2 IV73843 Consignment items can now be transferred to another consignment storeroom if the consignment vendor is same for both consignment storerooms. This transfer has a CONSTRANSFER type.
7.6.0.2 IV73886 Field validation on a company branch now prevents you from adding the current company as a branch of itself.
7.6.0.2 IV72084 Functionality Change: Previously, when a user entered values on the Apply IAS dialog in the Receipts application, closed the dialog, then opened the dialog again (without closing the Receive Rotating Items dialog), the previous entered values were not displayed. Now, those previously entered values are displayed.

User Interface Change: Additionally, use of the Autonumber All button on this dialog now sets the assetnum fields to read-only after populating them. This is a User Interface Change but not a Functionality Change because previously, the autokeyed values were used in asset creation even if the user tried to edit them after they were populated.
7.6.0.2 IV70473 In communication templates, when the mxe.base calendar is set to Islamic, Maximo displays an Islamic date format instead of Gregorian date format.
7.6.0.2 IV70586 Previously: Task status was not considered during the Work Package Material Status calculation for the parent Work Order. Now: Planned materials that are associated to tasks are only considered in the parent Work Order's Work Package Material Status calculation if the task has status APPR, WMATL, INPRG, or WSCH.
7.6.0.2 IV72017 Previously: The default application restriction on the View Requisitions application only allows users to view Requisitions which were requested for or by users in the current users's supervision hierarchy.Now: Users will additionally be allowed to view Requisitions which are assigned to them by a task in Workflow.
7.6.0.2 IV71835 Previously: When an Inventory Usage record was created to transfer an Item of cost type LIFO or FIFO, the GL Debit Account autofilled with the To Storeroom's GL Control Account.

Now: The GL Debit Account autofills with that Inventory record's GL Control Account. This change reflects the behavior from the Transfer Current Item dialog in the Inventory application.
7.6.0.2 IV71994 Several parameters were introduced in V7500_700.dbc that can affect the execution of V7500_700.class. These do not need modification unless script execution time is a problem. This script needs to run on a non-multi language system to update ASSETMETER and LOCATIONMETER LASTREADING/LASTREADINGDATE values, or the wanted decimal separator for updating ASSETMETER and LOCATIONMETER LASTREADING differs from the application server Locale's decimal separator. Since the decimal separator used for LASTREADING needs to match the decimal separator of the application server's Locale, this instance exists if the application server that is used to upgrade Maximo or run the V7500_700 script differs from the application server that ultimately hosts the Maximo production environment, and the Locales of the two different application servers differ.
The parameters that were added are:
1. IV71994LANGUAGE: A language code, for example, fr or en, that is used to determine which decimal separator is used for assetmeter and locationmeter lastreading. If this parameter is empty, the application server's language code is used.
2. IV71994COUNTRY: A country code, for example, FR or US, that is used to determine which decimal separator is used for assetmeter and locationmeter lastreading. If this parameter is empty the application server's country code is used.
3. IV71994SKIPMLCHECK: If this parameter is set to 1, a script is run even if the system is not multi-language. This is so the script can be used to correct duplicate meterreading or locmeterreading readingdate or measurement measuredate values, or to update assetmeter and locationmeter lastreading and lastreadingdate values. The default value is 0 so that this script only runs in is a multi-language environment.
4. IV71994BATCHSIZE: This parameter can be modified to increase the measurement, meterreading, locmeterreading, assetmeter, and locationmeter update batch size.
The default value is set to 1000. This can be used to try to improve script execution time if 1000 is not adequate.
5. IV71994SKIPDUPLOG: When the value of this parameter is set to false, all duplicate measurement/meterreading/locmeterreadings (based on asset or location, metername and measuredate/readingdate) are logged. When this value is set to true, this logging is disabled. The default value for this property is false. Disabling this parameter can speed up script execution if needed.
6. IV71994SKIPFIXLOG: When this parameter is set to false, all duplicate fixes are logged. Set to true to disable this logging. The default value for this parameter is false. Disabling this parameter can speed up script execution if needed.
7. IV71994SKIPUPDLOG: When this parameter is set to false, all assetmeter/locationmeter LASTREADING/LASTREADINGDATE updates are logged. Set to '1' to disable this logging. The default value for this parameter is false. Disabling this parameter can speed up script execution if needed.
7.6.0.2 IV74590 The COLUMNNAME of a MAXATTRIBUTE is now used to create the Action Log XML for Cognos publishing instead of the ATTRIBUTENAME.
7.6.0.2 IV74590 The COLUMNNAME of a MAXATTRIBUTE is now used to create the Action Log XML for Cognos publishing instead of the ATTRIBUTENAME.
7.6.0.2 IV74590 The COLUMNNAME of a MAXATTRIBUTE is now used to create the Action Log XML for Cognos publishing instead of the ATTRIBUTENAME.
7.6.0.2 IV74590 The COLUMNNAME of a MAXATTRIBUTE is now used to create the Action Log XML for Cognos publishing instead of the ATTRIBUTENAME.
7.6.0.2 IV72571 The following default password rules were changed to make Maximo more secure.
Passwords must include a upper-case character.
Passwords must include a lower-case character.
Passwords must include a numeric character.
Passwords must have 8 or more characters.
7.6.0.2 IV70782 The GL Debit Account on any Receipt line that transfers a Rotating or Inspection Required Item from the Receiving location to the Storeroom location now autofills with the GL Debit Account specified on the PO Line, rather than the To Storeroom's GL Control Account.
7.6.0.2 IV73923 Time zone characters can now be used in the setting.DISPLAYTIME and setting.PARSETIME properties. The time zone character must be placed at the end of the format, for example, HH:MM:SS Z. The valid time zone characters are: z - General time zone; Z - RFC 822 time zone; X - ISO 8601 time zone. All time zones are converted to the clients local time zone.
7.6.0.2 IV74750 V7602_26.dbc: The original script to install integration script options now uses the ALLUSERGROUP maxvariable.
7.6.0.1 IV74220 A new property, webclient.richtext.discardTags, was added. This property is a comma delimited list of html tags that are discarded from rich text fields. By default, the following tags are discarded: script, object, embed, and iframe.
7.6.0.1 IV77474 A new script, HF7601_06.dbc, was added to create the sameasobject/sameasattribute relationship for the binnum attributes.
7.6.0.1 IV73278 A new system property, mxe.crontask.runonschedule, was added. When the property is set to 0, missed scheduled cron tasks are run immediately and then at the next scheduled time. When the property is set to 1, missed scheduled cron tasks are not run until the next scheduled time.
7.6.0.1 IV73278 Added a new System Property mxe.crontask.runonschedule 0 is the default behavior in that if a missed scheduled runs of crontasks are run immediately and then at the next scheduled time 1 is the new behavior that will skip any run of missed scheduled tasks until the next scheduled time for the task
7.6.0.1 IV75207 The Rich-Text Editor now applies the styles from the extended.css style sheet.
7.6.0.1 IV84473 The select value dialog for the Result Set Graph Display By field now displays all fields for the object/application that are available in the Field Configuration tab. They are not limited to only those fields that are selected for display on the portlet.
7.6.0.1 IV73923 Time zone characters can now be used in the setting.DISPLAYTIME and setting.PARSETIME properties. The time zone character must be placed at the end of the format, for example, HH:MM:SS Z. The valid time zone characters are: z - General time zone; Z - RFC 822 time zone; X - ISO 8601 time zone. All time zones are converted to the clients local time zone.

 

Resolved defects for Maximo Asset Management 7.6.0

Version 7.6.0.10
Defect APAR Application Name Description
314881 IJ01152 Administration When you delete an object structure that has the Authorization Name set, the application set in the Authorization Name set is deleted.
325790 IJ06106 Application Designer When you give access to more than one Signature Option in Security Groups the values do not remain selected.
325302 IJ03180 Asset Templates In the Asset Template application, when you generate multiple assets for a location, Maximo hangs.
314887 IJ02684 Assets In the Assets application, when you select View Calibration History, the information provided for the No Adjustments Made field are incorrect.
314902 IJ02928 Assets In the Assets application, when you download the assets, an error occurs.
314912 IJ00966 Assets In the Assets application, when you modify a meter reading, the cumulative reading values on child asset meters are updated as if the modification is a new reading.
314914 IJ02044 Assets In the Assets application, the Status field on the Select Asset dialog box does not consider your organization.
315782 IJ04871 Assets In the Assets application, when you enter meter reading values on an unsaved meter, a negative reading is displayed for the Average Units/Day value.
315812 IJ01052 Assets In the Assets application, the wrong behavior occurs when you click cancel.
315816 IJ04293 Assets In the Assets application, when you add hidden fields to an asset, the hidden fields appear in Start Center query results.
315840 IJ06625 Assets In the Assets application, when you click to delete an attachment, it is not deleted.
315899 IJ07023 Assets In the Assets application, in the Map tab, the Route dialog freezes and cannot be closed.
316503 IJ08595 Assets In the Assets application, auto zoom does not work on an asset that has a GIS location.
318423 IJ08955 Assets In the Map tab of the Query by Attributes tool, the Layers drop down list is not displayed correctly.
320020 IJ09760 Assets Asset function formulas which use two levels of function cause an error when implemented.
321206 IJ10375 Assets In the Assets application, the layers list does not follow the order defined in the Map Manager.
322263 IJ10684 Assets In the Assets application, the map display in Maximo Spatial maps is not able to zoom to the same level of quality as it does in ESRI maps.
322967 IJ10830 Assets In the Assets application, the map does not load when token security is enabled.
322968 IJ10958 Assets In the Assets application, when you link records, the an error occurs on the map.
325304 IJ02683 Assets In the Assets application, when you move over the map tab with a linked record, the feature gets centered but it is not zoomed in.
325310 IJ02900 Assets In the Assets application, after you upgrade Maximo, the auto-locate functionality no longer works.
325313 IJ02104 Assets In the Assets application, when you delete a Person Group an error occurs.
325747 IJ06322 Assets In the Asset application, when managing downtime history, the Downtime field is either read only or part of the primary key and you cannot edit the field.
325802 IJ06209 Assets In the Assets application, when you change the parent of an asset, the previous parent inherits the meter readings.
325824 IJ07144 Assets In the Assets application, on the Map tab, the map does not refresh when the navigation bar is turned off.
325826 IJ05150 Assets In the Assets application, when you open a map, the map is not centered on the blue marker.
325863 IJ03794 Assets In the Assets application, when placing a point using service addresses, the pin point disappears.
315873 IJ05590 Assignment Manager In the Assignment Manager application, when assigning an hours value for a date in the future for a labor, you receive a message that indicates that a value is required for the Assignment Status field on the WMASSIGNMENT object.
319141 IJ08062 Assignment Manager After you install iFix 004 for Maximo Asset Management 7.6.0.9, in the Assignment Manager application, in the Labor List section, the Hours Available field and the % Alloc Field can be empty after an assignment is made.
321209 IJ10277 Assignment Manager In the Assignment Manager application, when Maximo for Utilities is installed, crew availability is incorrect.
325293 IJ02401 Assignment Manager In the Assignment Manager, when you use selected work dates, the crew list on a Microsoft Excel spreadsheet does not match the data in the application.
315746 IJ02469 BIM Projects In the BIM Projects application, when you save map attributes in the Specifications dialog box, an error occurs.
325771 IJ02489 BIM Viewer When Select Records is clicked on the list tab of Assets, Locations, or Work Order Tracking for a large set of records, a BIM viewer frame is displayed midway up the page.
315827 IJ02314 Bulletin Board Bulletin board messages do not clear after they are read.
316506 IJ08431 Calendars In the Calendars application, non-interruptible tasks on a work order do not start as expected for a 24-hour shift.
320029 IJ09581 Calendars When the calendar type is set to Islamic, dates in the Inbox/Assignments portlet and Result Set portlet display as the Gregorian calendar instead.
320665 IJ10161 Calendars In the Calendars application, the calendar is not using the defined Days in Pattern value.
323364 IJ11363 Calendars In the Calendar application, when you apply a shift to a calendar, not all work periods are created based on the pattern of the shift.
323364 IJ11363 Calendars In the Calendars application, when you apply a shift to a calendar, the shift is only partially applied.
325805 IJ07883 Calendars In the Calendars application, when you apply a shift to a calendar, the shift pattern is not applied to the expected days.
321609 IJ10597 Changes In the Changes application, when you create a service request and then create a follow-up change request, the work log tab displays the incident work log and not the service request work log.
320023 IJ09678 Chart of Accounts When you use the Maximo Integration Framework to import 1000 GL components, an error occurs.
315825 IJ02232 Classifications In the Offering Catalog, offerings of the same classification, can be listed in different catalogs incorrectly.
325913 IJ07369 Classifications In the Classifications application, if you delete a classification that is not associated with any other record, the application hangs.
314921 IJ06624 Collections In the Collections application, you cannot add an asset from the Open Drilldown function of the Asset field.
325300 IJ03080 Communication Template When you send communication to roles, the following error occurs: BMXAA4214E An unknown error has occurred.
325902  IJ05452  Communication Template When you send communications from a service request and more than one attachment is sent, not all attachments are displayed in the communication log.
315790 IJ02999 Condition Monitoring In the Condition Monitoring application, if you Select Value lookup for the Upper Limit PM field, you receive an error that the record could not be retrieved from the database.
325308 IJ02799 Condition Monitoring In the Conditional Monitoring application, when you associate a job plan to an asset, a null pointer exception occurs.
325905 IJ06805 Conditional Expression Manager If you use the Conditional Expression Manager application and the Application Designer application to indicate that values in the Service Request field must be aligned and centered, in the Service Request application, when all records are queried for on the List tab, the first value for the Service Request field is not aligned or centered.
318219 IJ08970 Condtional Expression Manager In the Conditional Expression Manager application, when you upgrade to 7.6.0.9. IF007, SIGOPTION conditions no longer work.
325915 IJ07398 Configure Tooltips If you change your default insert site to a site that is not yet accessed, in the Configure Tooltips application, you must log out and log back in before the templates appear in the list.
320077 IJ09633 Crafts In the Crafts application, when you create a new craft and add a skill level to this craft, the description of the skill level is not correct if you type the value into the field instead of choosing the skill level from the value list.
315811 IJ08070 Create Requisition In the Create Requisition application, when you use the select value lookup from either the Requested By or Request For fields, an error occurs.
318420 IJ08070 Create Requisition In the Create Requisition application, when you use the select value lookup from either the Requested By or Request For fields, an error occurs.
325809 IJ06279 Create Requisition When you create a desktop requisition from a template, an incorrect general ledger account is used.
319888 IJ09113 Crews In the Crews application, when you modify the crew availability, all fields in the Modify Crew Availability dialog box show invalid binding. 
320036 IJ09113 Crews In the Crews application, when you modify the crew availability, all fields in the Modify Crew Availability dialog box show invalid binding. 
314915 IJ03543 Cron Task Setup The PMWoGenCronTask instance runs but does not generate work orders or a log.
319402 IJ01148 Cron Task Setup Sometimes escalations run twice.
321208 IJ08931 Cron Task Setup In the Cron Task Setup application, in a clustered environment, when you set mxe.crontask.donotrun = ALL, and perform a live refresh, an error occurs.
321839 IJ10577 Cron Task Setup In the Cron Task Setup application, when syncing existing phone records, the task tries to insert a new phone instead of updating an existing phone record.
325691 IJ04122 Cron Task Setup Cron tasks that send email results by using an mxe.email.content.type of text/HTML hang after processing the records without sending the email.
325772 IJ05870 Cron Task Setup In cron task tables, fields are not displaying values properly.
315837 IJ07231 Data Sheet Templagtes In the Data Sheets Template application, when language is set to DE and locale is set to de_DE, entering 'r' in Revision comments causes the Revision History dialog to display.
314891 IJ01264 Database Configuration In the Database Configuration application, when you run a DB Config, the server does not restart formulas.
314910 IV99665 Database Configuration In the Database Configuration application, when you select the Set Security Profile action for multiple users, the Electronic Signature Authentication does not work correctly.
315860 IJ01361 Database Configuration In the Database Configuration application, when you make a change to the WONUM attribute and apply the changes, the Same As relationships for the WONUM attribute are not affected.
325295 IJ05375 Database Configuration In Database Configuration, when using the CSV file format, in the .csv file, you can see exp.testformula as headers, but there is no value.
325525 IJ04236 Database Configuration In the Database Configuration application, if you update the ORGID length, some attributes are not updated due to a missing ORGID same as relationship.
325758 IJ02048 Database Configuration When you import a view that includes a UNION ALL in the where clause into Maximo Database Configuration, attributes are not properly defined, preventing a successful import.
325799 IJ05222 Database Configuration The locations to work order relationship is not editable in database configuration.
325444 IJ00880  Desktop Requisition In Maximo Asset Management, a Direct Requisition has a different behavior when it is created by template.
325822 IJ06099 Domains In the Domains application, when you add a crossover field to the TKLOCATIONCROSSCI domain, the Target Description field is not updated on a service request when you specify an asset.
325497 IJ03792 E-mail Configuration When setting up email notifications from a work flow to a role, you initiate the work flow, but the role does not receive the expected email notification.
322344 IJ10673 Escalations When you route a work flow from a Europe/Paris time zone and Fr locale to user in US/Eastern time zone with a En_US locale, the work flow record is not being escalated as needed.
325677 IJ03496 Escalations In the Escalations application, when an escalation runs, it leaves open cursors, eventually leading to an error Ora-01000 message.
315848 IV97796 Everyplace Technician In the Everyplace Technician (Tablet) application, on the View List screen, the Required Tools data area does not show any information.
315781 IJ03902 Failure Codes Each time a failure class record is deleted in the Failure Codes application, the number of open cursors in the session increases. Eventually the open cursor limit is exceeded and the following message is displayed: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 1000.
315794 IJ04791 Failure Codes In the Failure Codes application, the second time you create a failure code, the Description field is read only.
315858 IJ02823 Graphical Assignment In the Graphical Assignment application, when you publish a scenario, the changes made do not go to the default scenario or to work orders.
315866 IJ02388 Graphical Assignment In the Graphical Assignment application, when an assignment is made manually on the Assignment View tan, it is not saved when you select save.
315872 IJ05195 Graphical Assignment In the Graphical Assignment - Repair Facility application, when a location names includes an underscore, you cannot assign assignments to the location.
315879 IJ03255 Graphical Assignment In the Crew Graphical Assignment application, when un-assigning several assignments, they all disappear.
318394 IJ08819 Graphical Assignment Date changes made in the Graphical Assignment application are not updated in the Work Order Tracking application.
318769 IJ09106 Graphical Assignment In the Graphical Assignment application, a delay occurs when loading the Dispatch tab if the value of the skdprojectid attribute for a work list is greater than 1000.
319073 IJ08968 Graphical Assignment In Graphical Assignment (GA) application, when you set up the street level routes cron task to apply SLRs in the background, the cron task looks for GRPASSIGN instead of RLASSIGN. The Select SLR dialog returns empty.
319232 IV99165 Graphical Assignment In the Graphical Assignment application, on the Dispatch tab, when spatial is selected as the map provider, routes do not work.
319740 IV99165 Graphical Assignment In the Graphical Assignment application, on the Dispatch tab, when spatial is selected as the map provider, routes do not work.
321203 IJ10276 Graphical Assignment If you change the scheduled start and finish dates in the Graphical Assignment application, the schedule is not updated in the Work Order Tracking application.
322265 IJ10679 Graphical Assignment In the Graphical Assignment application, any assignment to a mismatched craft that was placed over a non-working time turned the status bar to yellow instead of red.
322266 IJ10524 Graphical Assignment In the Graphical Assignment application, if there are apostrophes in the work order of task descriptions and you change the tool tip using the System Properties application, the tool tips do not work on the Work View tab.
322336 IJ10737 Graphical Assignment In the Graphical Assignment application, work orders are not visible on the Dispatch tab.
322337 IJ10770 Graphical Assignment In the Graphical Assignment application, on the Dispatch tab, the start travel icon, travel time bars and stop travel icon for a work order do not display in the Calendar view.
322352 IJ10149 Graphical Assignment In the Graphical Assignment application, when a work order has an appointment required option set to true and you used the right click to lock the assignment, you can move the record to a new date.
322532 IJ10795 Graphical Assignment In the Graphical Assignment application, refresh does not work with the schedule date is deleted on a work order or task.
325294 IJ03155 Graphical Assignment In the Graphical Scheduling application, when you run an optimization using the Capacity Planning scenario, with the Target Date set for some number of days, all the work orders are set for the first day. It should prioritize the work orders during the entire number of days that you set in the Target Date field.
325296 IJ03174 Graphical Assignment In the Graphical Assignment application, when you assign labor in the Available Labor dialog box, the following error occurs: BMXAA4214E - An unknown error has occurred.
325301 IJ03360 Graphical Assignment In the Graphical Scheduling application, on the Gantt View tab, when the Export to Excel action creates decimal values in the Date column.
325499 IJ02709   Graphical Assignment In the Graphical Assignment application, refresh does not work when the schedule date is deleted for a work order or a task.
325524 IJ03254 Graphical Assignment In the Graphical Assignment application, if craft names have underscores, the assignments disappear after running optimization.
325585 IJ05468 Graphical Assignment In the Graphical Assignment application, when you assign available labor the following error occurs: ASSIGNMENT BMXAA4214E - An unknown error has occurred.
325663 IJ05539 Graphical Assignment In the Graphical Assignment application, on the Filtered Assignment page, you cannot assign available labor.
325665 IJ05537 Graphical Assignment In the Graphical Assignment application, when you assign multiple assignments for a crew, the duration of the assignments is incorrect.
325666 IJ05538 Graphical Assignment In the Graphical Assignment application, when you right click on an appointment or note, the following error occurs: BMXAA4214E - An unknown error has occurred.
325667 IJ05540 Graphical Assignment In the Graphical Assignment application, after you close a tooltip, the dropdown menu n the corner of the browser remains.
325672 IJ05552 Graphical Assignment In the Graphical Assignment application, when you assign a work order to a Labor or Crew that is outside of the default work zone, clicking OK does not work.
325674 IJ05553 Graphical Assignment In the Graphical Assignment application, when you try to assign a work order to a labor and crew outside of the Default Work Zone, nothing happens when you click OK.
325675 IJ05638 Graphical Assignment In the Graphical Assignment application, the right-click menu is not working when the system property mxe.skd.automationids.enabled is set to TRUE.
325678 IJ05554 Graphical Assignment In the Graphical Assignment application, when you open the Modify Availability window, in the Resource section, the range of scheduled days do not display correctly.
325679 IJ05555 Graphical Assignment In the Graphical Assignment application, spatial optimization is not working when the Start and End locations are not the same.
325681 IJ05559 Graphical Assignment In the Graphical Assignment application, when the end location is changed, and you try to assign a work assignment to a Labor, you receive a message that tells you that an unknown error has occurred.
325686 IJ05561 Graphical Assignment In the Graphical Assignment field, deleting an assignment does not work for scenarios.
325688 IJ05562 Graphical Assignment In the Graphical Assignment application, when creating a new scenario and then typing in the scenario template name, you receive a message telling you that an unknown error has occurred.
325690 IJ05564 Graphical Assignment In the Graphical Assignment application, when assigning a work order to available labor and then clicking the assignment, you receive a message telling you that an unknown error has occurred.
325694 IJ05565 Graphical Assignment In the Graphical Assignment application, the Apply Individual Street Level Routes action is not working.
325700 IJ05569 Graphical Assignment In the Graphical Assignment - Repair Facility application, if a parent does not have an association with the repair facility, the parent is not displayed.
325707 IJ05568 Graphical Assignment In the Graphical Assignment application, the Refresh Interval field should only be visible on the More Information tab if the Scheduler Plus license exists. However, this field is visible without the license.
325708 IJ04191 Graphical Assignment In the Graphical Assignment application, when you use the Assign Available Labor function and you click OK on the dialog, you receive a message that says that the work order has been updated by another user, and your changes have not been saved.
325709 IJ05570 Graphical Assignment In the Graphical Assignment application, some assignments are not in black lettering.
325714 IJ05574 Graphical Assignment In the Graphical Assignment application, work that is not selected on a hierarchy is still highlighted blue.
325715 IJ05575 Graphical Assignment In the Graphical Assignment application, reassignment is not working when performing an undo or redo of the last action taken.
325717 IJ05576 Graphical Assignment In the Graphical Assignment application, when you are looking for Labor that has the View Multi Craft icon available, the Multi Craft dialog does not appear when you click the icon.
325719 IJ05577 Graphical Assignment In the Graphical Assignment application, work orders are assigned to a different parent from the one in their hierarchy.
325720 IJ05579 Graphical Assignment In the Graphical Assignment application, when you create a schedule with a work order and you move to Assignment or Dispatch, the unassigned records are not displayed. The dates are only at the task level and not the work order level.
325721 IJ05580 Graphical Assignment In the Graphical Assignment application, when the the mxe.skd.syncwodates property is set to 1, the scheduled end date does not move when an assignment is added that has a date past the existing scheduled end date.
325722 IJ05581 Graphical Assignment In the Graphical Assignment - Repair Facility application, a Location shift to a time outside of the specified work time is not causing the assignment to turn yellow.
325723 IJ05582 Graphical Assignment In the Graphical Assignment - Repair Facility application, double-booking a location does not cause a yellow indication.
325750 IJ06337 Graphical Assignment In the Graphical Assignment application,  when you have an exiting Work List with a labor, if you change the Defualt Craft for that labor, the change is not shown on the Assignment View tab.
325753 IJ04895 Graphical Assignment In the Graphical Assignment application, when you select Zoom to Work, it does not work correctly.
325754 IJ06469 Graphical Assignment In the Graphical Assignment application, if you select a labor that is highlighted as having the right skill level, the highlighting turns red.
325756 IJ06468 Graphical Assignment In the Graphical Assignment application, if you assign a record to an available labor while the Work Zone flag is on, this action causes a blank dialog to appear.
325761 IJ04932 Graphical Assignment In the Graphical Assignment application, when a work period has the same start and end time, an error occurs.
325765 IJ04370 Graphical Assignment In the Graphical Assignment application, when a partial work period is sent, optimization fails.
325768 IJ04372 Graphical Assignment In the Graphical Assignment application, when you modify more than one labor availability for multiple people, the Gantt view does not refresh.
325770 IJ04378 Graphical Assignment In the Graphical Assignment application, when you leave the resource query empty, the labors related to work are not available.
325773 IJ04377 Graphical Assignment In the Graphical Assignment application, when you create a work list without a shift it still gets saved.
325801 IJ03643 Graphical Assignment In the Graphical Assignment application, labor availability is not adjusting according to the time zone.
325832 IJ06938 Graphical Assignment In the Graphical Assignment application, when you select the Assign Available Crew action, an error message is displayed.
325833 IJ06930 Graphical Assignment In the Graphical Assignment application, when you select the Assign Available Crew action, an error message is displayed.
325836 IJ06932 Graphical Assignment In the Graphical Assignment application, when an assignment is made into Labor whose Craft/Skill does not match that of the original Planned Labor record, the assignment bar does not turn red.
325868 IJ04610 Graphical Assignment In the Graphical Assignment application, when you run optimization on a schedule with partial resources, the optimization is incorrect.
325872 IJ05596 Graphical Assignment In the Graphical Assignment application, optimization does not consider the alternative resource for the time period defined.
325874 IJ04711 Graphical Assignment In the Graphical Assignment application, when creating a work list without a work query, you receive a message that tells you that the total activities records for that project exceeds the limit of records allowed to be created.
325877 IJ05265 Graphical Assignment In the Graphical Assignment application, when you change the owner of an action you must refresh the record for the record to be updated.
325882 IJ05268 Graphical Assignment In the Graphical Assignment application, when you filter dates with >< operators, the results are incorrect.
325883 IJ05270 Graphical Assignment In the Graphical Assignment application, a rollings schedule or work list only changes the start and end dates but does not refresh the record.
325884 IJ05271 Graphical Assignment In the Graphical Assignment application, on the More Information tab, your current schedule and work list are not displayed.
325886 IJ05272 Graphical Assignment In the Graphical Assignment application, the skd.gantt.view.snap_to_interval_mins property is available.
325888 IJ05274 Graphical Assignment In the Graphical Assignment application, on the Activity table, the Filter drop down menu is not available.
325914 IJ04614 Graphical Assignment In the Graphical Assignment application, when you select Work Order Symbology, work orders are given an undefined value when they are priority.
325917 IJ02604 Graphical Assignment In the Graphical Assignment application, when a graphical assignment doesn't have a start/end location and you move the record, a null pointer exception occurs.
325932 IJ04615 Graphical Assignment In the Graphical Assignment application, when you select Zoom to Work, the Gantt chart is resized incorrectly.
325934 IJ04616 Graphical Assignment In the Graphical Assignment application, when the user is on a different site setup than what is listed in the work order, an error occurs.
325938 IJ05877 Graphical Assignment The Graphical Assignment optimization process is failing when some assignments could not be made.
325941 IJ02234 Graphical Assignment In the Graphical Assignment application, on the Dispatch tab, when you drag an assignment to a crew, the system hangs.
325951 IJ05714 Graphical Assignment In the Graphical Assignment application, the Copy Query action allows you to copy data sources other than your current data source.
319346 IJ09016 Graphical Crew Management In the Graphical Crew Management application, when you select the Previous Day, Next Day, or Toggle View buttons, an error occurs.
315847 IV98311 Graphical Scheduling In the Graphical Scheduling application, if you have craft usage on a scheduled work order, the date is not displayed correctly.
315851 IJ01902 Graphical Scheduling In the Graphical Scheduling application, planned labor hour calculations do not consider time zones.
315854 IJ01302 Graphical Scheduling In the Graphical Assignment application, when you run optimization with the At This Time option, the optimization fails.
315855 IJ02544 Graphical Scheduling In the Graphical Assignment application, spatial optimization does not assign requirements.
315857 IJ00492 Graphical Scheduling When there is a no shift day before a work order assignment schedule, no information is displayed on the map.
315859 IJ00167 Graphical Scheduling In the Graphical Scheduling application, in Gantt view, you cannot add new rows in scheduler system properties.
315861 IJ02309 Graphical Scheduling In the Graphical Scheduling application, when a work order has a synonym status, Gantt view is not displayed.
315863 IJ02363 Graphical Scheduling In the Graphical Scheduling application, when you edit precedence constraints, an error occurs.
315865 IJ02435 Graphical Scheduling In the Graphical Scheduling application, when planning labor resources in the parent work order, the system does not display the planned resource in the activity tab column.
315867 IJ04886 Graphical Scheduling In the Graphical Scheduling application, when you filter records and select multiple records for an action, some of the hidden records are effected by the action.
315871 IJ04944 Graphical Scheduling In the Graphical Scheduling application, when you move a bar beyond the end of a schedule, the error message that is displayed is ambiguous.
315874 IJ05690 Graphical Scheduling In the Graphical Scheduling application, the SKDActivity table's Modified column is set to 1 even in cases where it is not needed and the record does not need to be committed.
315876 IJ07990 Graphical Scheduling In the Graphical Scheduling application, until the browser cache is cleared, Person availability changes are not correctly reflected.
315889 IJ04751 Graphical Scheduling In the Graphical Scheduling application, in Gantt view, when you select Add/View Notes, the system hangs.
315893 IJ01159 Graphical Scheduling In the Graphical scheduling application, after you resize a bar, the Duration field is incorrect.
315894 IJ02446 Graphical Scheduling In the Graphical Scheduling application, when you create preventive planning and go to Gantt view, the schedule is displayed in incorrect colors.
315895 IJ02746 Graphical Scheduling In Graphical Scheduling application, when you try to create a successor and predecessor dependency using the CTRL key, the system does not allow you to create the dependency on different hierarchy orders. Using the Create Restrictions button, the system allows you to create a successor and predecessor dependency, but it is not possible to reverse the successor position to be the predecessor position.
316624 IJ08695 Graphical Scheduling In the Graphic Scheduling application, the Calculate Cost Week tab does not consider the resources associated with the task.
316730 IJ08703 Graphical Scheduling In the Graphical Scheduling application, when you use Next Schedule or Previous Schedule while you view a schedule, the start of the date ribbon for the subsequent schedules is not used.
316753 IJ08646 Graphical Scheduling In the Graphical Scheduling application, if you select Rolling Project and then select a value, you receive an error that says that the start and end date must be entered.
318415 IJ08818 Graphical Scheduling In the Graphic Scheduling application, the Refresh When Opening Gantt View option does not include updates.
318770 IJ05242 Graphical Scheduling In the Graphical Scheduling application, when you use different time zones, craft availability is displaced by one day for some shifts.
320012 IJ08818 Graphical Scheduling In the Graphic Scheduling application, the Refresh When Opening Gantt View option does not include updates.
321194 IJ08989 Graphical Scheduling In the Graphical Scheduling application, when you toggle between scenarios, an error occurs.
321202 IJ08915 Graphical Scheduling In the Graphical Scheduling application, when you move a PM, the Save button does not undim and the row does not turn red.
321204 IJ09126 Graphical Scheduling In the Graphical Scheduling application, when you click Calculate Labor Hours, an error occurs.
322340 IJ10755 Graphical Scheduling In the Graphical Scheduling application, not all fields are translated into Portuguese.
322781 IJ10475 Graphical Scheduling In the Graphical Scheduling application, the Resources Load and Availability area does not display the full number of labor hours for a job plan.
323112 IJ11080 Graphical Scheduling In the Graphical Scheduling application, if you change the PM forecast for a PM record, on the Forecast tab, the New Date field is not updated after you commit your changes.
325303 IJ02677 Graphical Scheduling In the Graphical Scheduling application, when you leave the application and come back in, print options for columns are not retained.
325305 IJ03339 Graphical Scheduling In the Graphical Scheduling application, on the Graphical view, the date ribbons are misaligned.
325306 IJ03344 Graphical Scheduling In the Graphical Scheduling application, you cannot load the Treegrid CSS.
325307 IJ01549 Graphical Scheduling In the Graphical Scheduling application, in Gantt view, when you zoom out, cursor focus is lost.
325312 IJ02439 Graphical Scheduling In the Graphical Assignment application, on the Assignment View tab, when you select labor that has 0 availability hours, an error is occurs.
325491 IJ03282 Graphical Scheduling In the Graphical Scheduling application, when you select the Filter Work Orders Based on Selected Resources or the Filter Resources Based on the Selected Work Orders toolbar buttons, no data is displayed.
325495 IJ03670 Graphical Scheduling In the Graphical Assignment application, the hover text no longer shows the work order, and you can no longer customize this text.
325496 IJ03713 Graphical Scheduling In the Graphical Scheduling application, you are unable to re-schedule assignments. The start and end dates are not updated in the Graphical View tab.
325500 IJ03926 Graphical Scheduling In the Graphical Scheduling application, when the predecessor finishes in non-working time, the successor is not scheduled when it should be at the start of the next working shift, but rather gets delayed by the same number of hours that the predecessor works in the non-working time.
325501 IJ03984 Graphical Scheduling In the Graphical Scheduling application, the Date field value shows only numbers. The date value should be MM/DD?YYYY - TIME.
325502 IJ03904 Graphical Scheduling In the Graphical Scheduling application, Restrict Work To Dates and Rolling Project should not check the Target Dates if the Schedule Dates exist, but the Target Dates are being used.
325503 IJ03937 Graphical Scheduling In the Graphical Scheduling application, the duration changes on non-interruptible tasks when you run CPM.
325504 IJ03923 Graphical Scheduling In the Graphical Scheduling application,  if the predecessor finishes in working time, a non-interruptible successor should start in that same working shift and then finish in the non-working time if  it is long enough to extend into the non-working time. Now, it is scheduling the successor as if it were interruptible, meaning that it starts when it should but does not finish until some point in the next working shift.
325527 IJ05362 Graphical Scheduling In the Graphical Scheduling - Large Projects application, CPM is not calculating Early Start, Early Finish, Late Start, Late Finish and Float times.
325528 IJ05308  Graphical Scheduling In the Graphical Scheduling application, when you setup the Graphical Scheduler Compliance functionality and select the Activate Cron checkbox, the two compliance crons, SKDComplianceStartCronTask and SKDComplianceFinishCronTask do not get instances created in their respective crons in Cron Task application.
325579 IJ05426 Graphical Scheduling In the Graphical Scheduling application, when you do a calculation on long duration work, the calculation period is incorrect.
325581 IJ05243 Graphical Scheduling In the Graphical Scheduling application, the duration of higher level work orders is calculated inconsistently depending on the operation you do on the Gantt View tab.
325587 IJ05499 Graphical Scheduling In the Graphical Scheduling - Large Project application, when you use the filter on the toolbar for graphical scheduling, it does not filter.
325588 IJ05500 Graphical Scheduling In the Graphical Scheduling application, once you use the filter on the toolbar for a graphical scheduling project, the other actions on the toolbar do not work.
325589 IJ05501 Graphical Scheduling In the Graphical Scheduling application, the Revert Changes button takes you back to the original state but the blue italic modify indicator does not display.
325591 IJ02236 Graphical Scheduling In the Graphical Scheduling application, the modified date is not displayed correctly.
325593 IJ04387 Graphical Scheduling In the Graphical Scheduling application, when you expend the Resource in the Graphical View, the Tool Availability does not appear.
325594 IJ05021 Graphical Scheduling In the Graphical Scheduling application, the duration column is not displaying correctly.
325662 IJ05536 Graphical Scheduling In the Graphical Scheduling application, when you move a column, headers are misaligned.
325668 IJ02638 Graphical Scheduling In the Graphical Scheduling application, when you print a second time in a single session on Chrome you get a blank report.
325669 IJ05637 Graphical Scheduling In the Graphical Scheduling - Large Project application, when the Calculate Duration Action occurs, the start times, end times, and duration are not displayed.
325670 IJ03343 Graphical Scheduling In the Graphical Scheduler application, the description in the Graphical View tab shows as modified when it is not.
325673 IJ02898 Graphical Scheduling In the Graphical Scheduler application, a user can create a dependency between different parents and levels of work without a Scheduler Plus license.
325684 IJ03497 Graphical Scheduling In the Graphical Scheduling application, when you open large projects, select a record, and then mobe to the Graphical View tab, you receive errors telling you that the project data failed to populate the scheduler tables or that the activities did not populate.
325702 IJ05567 Graphical Scheduling In the Graphical Scheduling application, when you publish a Graphical Assignment record, the Last Published date is not available.
325710 IJ05571 Graphical Scheduling In the Graphical Scheduling - Large Project application, when you create a schedule based on an existing graphical scheduling record with a type of asset or location, the query section is not correct.
325711 IJ03627 Graphical Scheduling In the Graphical Scheduling application, the % Complete field is not calculated properly when the calculation method is set to task.
325712 IJ05572 Graphical Scheduling In the Graphical Scheduling - Large Project application, when you create an asset or location type schedule and select new row, the button for query restrictions is missing.
325713 IJ05573 Graphical Scheduling In the Graphical Scheduling Large Project application, when you create a schedule and then click New Row inside of Restrict Resources query, there are no data objects to select.
325733 IJ04253 Graphical Scheduling In the Graphical Scheduling application, the weekly and monthly tooltips are not displaying correctly.
325734 IJ04254 Graphical Scheduling In the Graphical Scheduling application, the weekly and monthly tooltips are not displaying correctly.
325735 IJ04256 Graphical Scheduling In the Graphical Scheduling application, the % complete color is not working correctly for the critical path bars.
325737 IJ04259 Graphical Scheduling In the Graphical Scheduling application, you cannot commit a change to a single work order.
325738 IJ04258 Graphical Scheduling In the Graphical Scheduling application, when you run optimization from the default scenario, the following error occurs: BMXAT1064E - Optimization can only be run on work orders, not PM forecasts.
325739 IJ04260 Graphical Scheduling In the Graphical Scheduling application, when you publish a scenario, the new schedule dates are not saved correctly.
325740 IJ04263 Graphical Scheduling In the Graphical Scheduling application, when modified availability times conflict with work period times, the optimization fails to run.
325745 IJ04264 Graphical Scheduling In the Graphical Scheduling application, when the work periods start and end at the same time, an error occurs.
325748 IJ04887 Graphical Scheduling In the Graphical Scheduling application, when you select the option to Modify Work Details an error occurs.
325749 IJ04894 Graphical Scheduling In the Graphical Assignment application, time that is taken to create a scenario depends on the number of associated records.
325760 IJ05969 Graphical Scheduling In the Graphical Scheduling application, a right-click action causes the Task ID to be removed from the Column value.
325784 IJ06569  Graphical Scheduling In the Graphical Scheduling application, it takes a long time to save a schedule.
325791 IJ04383 Graphical Scheduling In the Graphical Scheduling and Graphical Assignment applications, when you search for weather information for a past or future date, the tooltip states that the weather cannot be retrieved.
325803 IJ04385 Graphical Scheduling In the Graphical Scheduling application and the Graphical Assignment application, when you try to run an optimization with a low allocation of resources, the optimization fails.
325806 IJ03987 Graphical Scheduling In the Graphical Scheduling application, when you run the CPM, an error occurs.
325813 IJ06869  Graphical Scheduling In the Graphical Scheduling application, newly created snapshots are not flagged as snapshots in the Manage Snapshots and Scenarios dialog box.
325815 IJ07293 Graphical Scheduling In the Graphical Scheduling application, when you specify a PM hierarchy that references crafts, only the craft that is associated with the parent PM is displayed in the Resources section.
325816 IJ07309 Graphical Scheduling In the Graphical Scheduling application, on the Graphical View tab, when a PM is dragged to a new time, the duration of the PM changes.
325831 IJ04386