IV95414: NON-ADMIN USERS UNABLE TO SEE CREATED COMMENT FOR ORGANIZATIONS THAT DO NOT HAVE ORGNAME / SCOPE SET.

APAR status

• Closed as fixed if next.

Error description

• If an admin user logs in to view that Org Name and then go to
  Notes and Documents. They can see the comment,
  
  The real problem happens for non-admin users. The comment
  disappears when a Non-admin user activates the org record and
  tries to view the comment.
  
  To replicate, simply create a user with a non-admin
  affiliations to ensure that the accounts is tagged a non admin.
  
  Revise an Organization Record and go to the Notes and Docs Tab.
  Add a comment. Create and Activate the Record.
  
  Check the Org Record again. See that the comment disappears for
  a non-admin user.
  

Local fix

• N/A
  

Problem summary

• Need to update the Workflow: Organization - Synchronous -
  Update Intermediate Locators and Dependant Records
  

Problem conclusion

• The Organization - Synchronous - Update Intermediate Locators
  and Dependent Records workflow now updates the dependent
  records orgName field with it's orgName value.  This change
  prevents a user that has access to a parent Organization
  without Organization Scope access from losing access to the
  parent records dependent records.
  This is targeted to the 1h2017 OM/Application Release.
  

Temporary fix

• Steps to Resolve this:  Modify the Workflow: Organization -
  Synchronous - Update Intermediate Locators and Dependant Records
  For each of the modify tasks, modify the orgName Map to no
  longer use the 'source' as the map.  The map needs to be
  changed to map orgName to orgName.
  The underlying problem here is when the parent object does not
  have orgName Set (Org Access), this workflow stamps the child
  records with the parent org.  The result is the user loses
  access to the child records of the org, they once had access to.
  To test, ensure that the dependent records in Organization -
  Synchronous - Update Intermediate Locators and Dependant
  Records are being set to the parent records OrgName value, and
  not the parent in the event they were different.
  

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

Applicable component levels

• R352 PSY

     UP