Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Sample Application
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-5106Maintenance Document does not display attached file KULRICE-11379sample for M29 KULRICE-5144Create test for multiple attachments KULRICE-5206Create test for multiple attachments in trunk KULRICE-11384Create Automated Functional Tests for KRAD Labs - Maintenance Sample - Basic KULRICE-11388Create Automated Functional Tests for KRAD Labs - Maintenance Sample - Presentation Controller KULRICE-11390Create Automated Functional Tests for KRAD Labs - Maintenance Sample - Override Values KULRICE-11785Unable to attach note to Lab - Maintenance - BO Attachment Sample KULRICE-14134Exception adding attachment in maintenance document KULRICE-7302Selenium tests for Travel Maintenance Document -
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
The attached files adds the "Attachment Sample" maintenance document which can be used to test attachments and multiple attachments in maintenance documents of Rice 1.0.3.2.
Issue Links
- fixes
-
KULRICE-5120
Deletes from a collection in a Maintenance Documents do not persist to BO table
-
- is related to
-
KULRICE-10455
Support for retrieving attachments which have been linked to properties on the business object itself
-
- relates to
-
KULRICE-4896
Enable Maintenance Document Framework to allow associating multiple attachments to a Maintainable BO
-
Activity
Integrated in rice-1.0.3.2-nightly #46 (See http://ci.rice.kuali.org/job/rice-1.0.3.2-nightly/46/)
KULRICE-5144 : incorporating Claus Niesen's sample maintenance documents from KULRICE-5130 into both the test and sampleapp codebases for the purpose of facilitating testing of KULRICE-4896
This looks done since the Attachment Sample maintenance docs were put into code, so I'm closing. Please reopen if needed.
I notice that the document type for this screen isn't ingested into our master database. Should it be? We have a link to this screen on the rice portal, but it's pretty much useless without the document type.
^^^ That should read as "We have a link to this screen on the sample app" instead of "... rice portal"
Yes, the document type should be added to the master database.
Added the multiAttachment collection to the buildListOfDeletionAwareLists(). This is needed to support the deletion of collection entries. The attached patch file has been updated.