IJ47934: AUTOMATION SCRIPT NOT BEING FIRED WITH ASSETSPEC.NUMVALUE CHANGE

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  Automation Script not being fired with ASSETSPEC.NUMVALUE change
  
  
  PROBLEM:
  Automation Script not being fired with ASSETSPEC.NUMVALUE
  change, but works with ASSETSPEC.ALNVALUE.
  You have 2 scripts that are object launchpoint scripts. One
  script is a simple script that modifies an attribute of ASSET on
  ASSETSPEC.SAVE.
  
  When you modify the classification attribute ALNVALUE of an
  ASSETSPEC, a script modifies an attribute of ASSET. Another
  script is triggered (SAVE of ASSET) and everything works fine.
  Although, when you modify the NUMVALUE of an ASSETSPEC, the same
  script modifies an attribute of ASSET however the other script
  is not triggered.
  
  STEPS TO REPRODUCE:
  1- open maximum logged as Maxadmin
  2- create a new classification in the classification app as
  below
  Classification= BOBCLASS
  Use With= ASSET
  In the attributes section create 2 attributes one of them
  NUMERIC type and the other one ALN.. (AA1 and AA2)
  
  3- Before saving the classification, ensure that in the "Use
  with Object Detail" dialog box for each attribute line the "Use
  in description generation?" checkbox is unchecked
  4- Save the classification
  5- go to automation scripts application
  6- create new automation script with object launch point as
  below
  
  script= TEST_ASPEC
  language= python
  log level= debug
  
  object= ASSETSPEC
  
  events= Save
  
  Save= Update? / Before Save
  
  No variables
  
  Script code:
  from psdi.util.logging import MXLoggerFactory
  from psdi.server import MXServer
  from psdi.mbo import MboConstants
  
  ### MAIN ####
  service.log("TESTMG12345 ->VDM_BDSA_GEN_PROP")
  if interactive:
  if mboname == "ASSETSPEC":
  asset = mbo.getOwner()
  asset.setValue("SERIALNUM","TEST12345",MboConstants.NOACCESSCHE
  CK)
  
  7- create another automation script with object launch point as
  below
  
  script= TEST_A
  language= python
  log level= debug
  
  object= ASSET
  
  events= Save
  
  Save= Update? / After Commit
  
  No variables
  
  Script code:
  from psdi.util.logging import MXLoggerFactory
  from psdi.server import MXServer
  from psdi.mbo import MboConstants
  
  service.log("TESTMG12345 ->VDM_BDSA_GEN_PROP_ENTETE")
  
  8- now go to assets application and create a new asset
  9- in the specifications tab ensure that you add the newly
  created classification in the classification field and you will
  see in the specifications section the two attributes
  10- save the record
  11- go to the attribute line that is ALN data type and in the
  alphanumeric value field enter any value for example MYTEXT
  12- go to the system out log and try to find the 12345
  information from each of the automation scripts you created to
  ensure they are running.
  
  You should be able to find the following 2 strings with a search
  in the systemout.log: TEST12345 and TESTMG12345 (this means the
  2 scripts ran fine)
  
  Let's repeat the test now but this time changing the numeric
  attribute instead and try to find the three strings again in the
  log
  13- go to the attribute line that is NUMERIC data type and in
  the alphanumeric value field enter any value for example 99999
  12- go to the system out log and try to find the 12345
  information from each of the automation scripts you created to
  ensure they are running.
  
  You should be able to find the TEST12345 but not the other one,
  which means that only one script is running when you modify a
  NUMERIC attribute.
  
  CURRENT ERRONEOUS RESULT:
  Automation Script not being fired with ASSETSPEC.NUMVALUE change
  
  
  EXPECTED RESULT:
  Automation Script is fired with ASSETSPEC.NUMVALUE change
  
  ENVIRONMENT (SYSTEM INFO):
  IBM WebSphere Application Server 9.0.5.10
  IBM Maximo Calibration 7.6.1.0 Build 20200715-0100 DB Build
  V7600-08
  IBM Maximo Asset Management Scheduler 7.6.8.0 Build
  20200715-0100 DB Build V7680-148 HFDB Build HF7680-19
  IBM Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
  V7640-12
  IBM Tpae Integration Framework
  7.6.1.2-MIF_7612_IFIX.20210803-0716 Build 20200715-1444 DB Build
  V7612-11 HFDB Build HF7612-02
  IBM Maximo APM - Asset Health Insights 7.6.1.0 Build
  20190321-2009 DB Build V7610-29
  Tivoli's process automation engine 7.6.1.2-IFIX20210819-1713
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-46
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
  IBM Maximo Linear Management 7.6.1.0 Build 20200715-0100 DB
  Build V7610-04
  IBM Maximo for Service Providers 7.6.3.3 Build 20190519-2208 DB
  Build V7633-13
  IBM Maximo BIM Extensions Autodesk Forge viewer plug-in 7.6.0.8
  Build 20170508-0100 DB Build V7608-02
  IBM Maximo Transportation 7.6.2.5 Build 20180730-2210 DB Build
  V7625-10
  IBM Maximo Spatial Asset Management 7.6.1.0-20210824-1530 Build
  20200716-1706 DB Build V7610-15 HFDB Build HF7610-08
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
  V7611-01
  IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  V7603-32
  IBM Maximo Health, Safety and Environment Manager 7.6.1.0 Build
  20161020-0816 DB Build V7610-01
  TPAE OSLC Object Structure 7.6.4.0 Build 20200219_092917-0500 DB
  Build V7640-04
  SE Serveur Windows Server 2016 10.0
  Base de données serveur Microsoft SQL Server 14.0 (14.00.2037)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * AUTOMATION SCRIPT NOT BEING FIRED WITH ASSETSPEC.NUMVALUE    *
  * CHANGE                                                       *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 8.8 Product
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels