IJ14949: WORKFLOW ICON SHOWS AS ACTIVE DESPITE NO WORKFLOW RUNNING WHEN CREATING RELATED RECORDS.

APAR status

• Closed as program error.

Error description

• The client has a WF process that creates a related record and
  then opens that new record in the new application.    When that
  record is opened in it's application, the Route WF toolbar
  button has the Active shape but it should not be Active as it
  is not in WF.   Looking closer this can be seen:
   - in the WFInstance table Active =0
   - in WFCallstack Active = 0
   - in the application View WF History is empty showing it was
  never in WF
   - in the original application that created the related record,
  the WF Icon shows Active though WF History shows stopped.
  
  NOTE:
  While development agrees that this is a problem, it cannot be
  fixed in an Interim Fix as the fix is too deep in the core
  Maximo code.    Fixing it in an Interim Fix or in a Limited
  Availability Fix would be too risky.
  
  In Maxdemo this can be reproduced using the SR WF process that
  is typically Active and Enabled right out of the box.   When
  using it, choose to create an Incident.   See the steps below.
   You can also create new WF processes for other objects and the
  same problem occurs.
  
  STEPS TO REPRODUCE:
  1. Go to WF Designer with a Maxdemo database and view the SR WF
  process.
  2. Typically Process Revision 13 is Active and Enabled.
  3. Open it and view properties for the CREATEINC Interaction
  node.
  4. It should have Application INCIDENT and Relation
  NEWINCIDENT.   This means when the process gets to this node,
  it will go to the Incident application and display the new
  Incident created by the SR CREATEINCIDENT Action on the Arrow
  leading into the CREATEINC Interaction node.
  5. Go to the Service Requests application.
  6. Create a new SR and give it a Summary and a Site.
  7. Save and click Route WF.
  8. Choose Create Incident when the Manual Input dialog appears.
    Click OK
  9. The Incident application now opens with the new record.
  
  RESULTS:
  You will see when Incident opens that the Route WF toolbar
  button is the Active shape, it has the checkmark on it.
  The Route WF toolbar button is the Active shape on the original
  application, too.
  
  EXPECTED RESULTS:
  The Route WF toolbar button should be in the In-Active shape.
  And in the SR application the new SR record should also have
  the Route WF button in the In-Active shape as the WF process
  has Stopped.
  
  VERSION INFORMATION:
  A client reported this in 7.6.0.8 with Oil&Gas using the MOC
  applications.
  Reproduced on 7.6.0.7 with Oil&Gas with the MOC applications
  And on pre-GA 7.6.1.1 using SRs as shown above.
  Note: Oil&Gas is not required to reproduce issue.
  

Local fix

Problem summary

Problem conclusion

• The fix for this APAR is contained in the following
  maintenancepackage:
  Release 7.6.1.3 of Base Services
  

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