work on persisting import files and crms attachments
file repository and strategy beans are abstract because apps need to
define their own (and can use these as parents) to define rootPath and
archiveRoot
faciliate passing request parameters from the view to the decorator for
the decorator buttons
ImportDefinitionMappingFile changed to ImportFile to be more general
purpose to accomodate import data files as well
import msgs
comment only
work on page title parameters
work on page title timestamp parameter formatting
added the DO_NOT_EXECUTE flag param that jhesse used for PDF handing in
oldlava
attachmentsListHandler injected for all actions to use
fixed bug in handleDownload
directory path and file naming conventions for storing import mapping
and data files in the repository
new handler to support lists of attachments for any entity
ImportDefinitionMappingFile changed to ImportFile to be more general
purpose to support data files as well
ImportDefinitionMappingFile to ImportFile for general purpose use for
data files and mapping files
1) use ImportFile for data file and set definitionName for use in
repository generateLocation
2) persist data file
3) override prepareToRender so import flow state "result" gets "view"
componentMode
put importLog detail messages in the model for the view
mapping file is now of type ImportFile
data file is now of type ImportFile
inject attachmentsListHandler in crmsComponentFormAction for use by all
entities