cancel
Showing results for 
Search instead for 
Did you mean: 

Records Management Error - Alfresco Enterprise 2.0

mvanbergen
Champ in-the-making
Champ in-the-making
Hello,

We are doing some internal testing of the Records Management module on Enterprise 2.0 (build-23) and have run into a problem.  When we update an existing record (i.e. updating the "Last Review Date" upon performing a vital record review), it appears that the next review date is not automatically calculated upon clicking OK on that record to accept the "Last Review Date".  It does appear that the "Last Review Date" is being persisted properly.  Isn't the "Next Review Date" supposed to be calculated automatically based on the vital record increment?

After further investigation, we have noticed the following error message in the alfresco.log file:

08:12:19,004 WARN  [alfresco.missingProperties] Failed to find property 'rmaSmiley SurprisedtherAddressee' for node: workspace://SpacesStore/37e7f00c-a616-11db-b705-a76dc4fc3b7b

After referencing the recordModel.xml, it appears that there is no rmaSmiley SurprisedtherAddressee property as shown below:

<property name="rmaSmiley SurprisedtherAddressees">^M
               <title>Other Addressees</title>^M
               <type>d:text</type>^M
               <mandatory enforced="false">false</mandatory>^M
</property>^M

It is actually "rmaSmiley SurprisedtherAddressees".  

Anyway, could this error be what is causing the "Next Review Date" from not being calculated automatically on a record review update?

Thanks,
Matt
2 REPLIES 2

derek
Star Contributor
Star Contributor
Hi,

Thanks for the feedback.  We'll have a look and probably raise a JIRA issue for it.

Regards

rwetherall
Confirmed Champ
Confirmed Champ
Hi,

Currently the nextReview date is not calculated which perhaps it should be.   Also a review action that actomatically sets the reviewed date for you would be a good idea.  I've added this as feature request in JIRA http://issues.alfresco.com/browse/RM-17

The problem with the address property sounds like a bug so i've raised that in Jira also http://issues.alfresco.com/browse/RM-18

Cheers,
Roy