[KULRICE-9380] refactor DocumentHeader so that we can remove special logic for stashing the WorkflowDocument in the UserSession Created: 24/Apr/13  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Peter Giles (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to KULRICE-9358 Form and WorkflowDocument no longer b... Closed
is related to KFSOLD-23383 CAMS - NPE when initiating Asset Manu... Closed
Similar issues:
KULRICE-12233workflowDocument should not be a field on the DocumentHeader
KULRICE-7069Removing special Page refreshing and just use component refresh
KULRICE-4864remove the dependencies UserSession has on EditablePropertiesHolder, ConfigService, & WorkflowDocument
KULRICE-11664DocumentBase JPA versus OJB change regarding saving/restoring documentHeader
KULRICE-1823KualiHttpSessionListener sessionDestroyed method does not have valid UserSession in GlobalVariables
KULRICE-7700Remove special data properties
KULRICE-13965In dev environment, WorkflowDocument is null in DocumentHeader on maintenance doc submit
KULRICE-5341UserSession gets bound to a thread, and eDocLite documents are not establishing user session properly
KULRICE-9384Analyze usage of SequenceAccessorService and determine if we can refactor away the need to "prefetch" sequence identifier values
KULRICE-8417Make it so that you can add link text to the question framework
Rice Module:
KRAD, KEW
KRAD Feature Area:
Document
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

See if we can make the workflowDocument field of the DocumentHeader non-transient and remove special logic for stashing and retrieving the WorkflowDocument in the UserSession. In theory we should be able to do this, since the object tree for the form contains the workflowDocument (form->document->documentHeader->workflowDocument), and the form is already being stashed in the session and retrieved for each request.


Generated at Sat Feb 22 06:56:18 CST 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.