RS02348: CANNOT PUBLISH EVENT OBJECT CONTAINED IN A FOLDER TO DC BRANCHES

Operational Decision Manager V8.7.1.1: Interim Fix 48
Operational Decision Manager V8.8.0.1: Interim Fix 13
Operational Decision Manager V8.0.1.2: Interim Fix 62
Operational Decision Manager V8.8.1 Mod Pack
Operational Decision Manager V8.7.1.2 Fix Pack
Operational Decision Manager V8.8.1 Download Document
Operational Decision Manager V8.8.0.1: Interim Fix 32
Operational Decision Manager V8.8.0.1: Interim Fix 34
Operational Decision Manager V8.8.0.1: Interim Fix 41
Operational Decision Manager V8.0.1.2: Interim Fix 68
Operational Decision Manager V8.8.0.1: Interim Fix 49
Operational Decision Manager V8.0.1.2: Interim Fix 70
Operational Decision Manager V8.8.0.1: Interim Fix 51
Operational Decision Manager V8.8.0.1: Interim Fix 62
Operational Decision Manager V8.8.0.1: Interim Fix 65
Operational Decision Manager V8.8.0.1: Interim Fix 72
Operational Decision Manager V8.8.0.1: Interim Fix 79
Operational Decision Manager V8.0.1.2: Interim Fix 67
Operational Decision Manager V8.8.0.1: Interim Fix 38
Operational Decision Manager V8.8.0.1: Interim Fix 83

APAR status

• Closed as program error.

Error description

• In Event Designer, an event object created in a subfolder under
  assets cannot be published to a branch in DC.
  You can reproduce this issue by the following steps:
  1) In ED, create an empty event project and publish it to DC,
  then disconnect the project from DC.
  2) In DC, create a subbranch for this event project
  3) In ED, create a folder under assets, name it Bob, then
  create a Event and Event Object, then choose to synchronize
  with the DC project's subbranch created in step 2.
  4) Then in ED, try to publish the new folder Bob to DC, you
  will see "error while publishing" box with messge: There is
  already an item for which the property name is Bob.
  I do not see any error in DC log and ED log. When I try to
  synchronize the change to main branch, it works fine.
  

Local fix

Problem summary

• The issue is related to checkEltFQN() method that
  does not take into account the different package kinds.
  This method is used to implement using java-code the
  db-constraint that cannot be applied to sub-branches (since
  elements from the folder path may be spread in the branch
  hierarchy).
  The checkEltFQN() finder should also include the
  packageKind in its change criteria.
  

Problem conclusion

• The code is fixed
  

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:

Modules/Macros

• 999
  

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R801 PSY

     UP