Skip to main content
Solved

configurator editor - movetaskappointmentTohistory


Forum|alt.badge.img+11

HI

 

I didn’t achieve to find what was behind this parameter in the configurator editor / times section / MoveTaskAppointmentToHistory ?

 

Thanks for your feedback

rgds

Christophe

 

Best answer by Phil Seifert

HI Christophe,

I confirm Joshua’s guess is correct.

The setting in the configuration editor triggers the action to start the move.  Thus in my case, a setting of 86400 seconds means the move action occurs every 24 hours (daily).

The setting in the application referred in Joshua’s post above refers to eligibility filter to move the data to history.

So between the two settings, once per day any records that are older than 30 days will be moved to history.

Unlike some of the other timers in the global.xml, there is not a setting to determine the eligibility such as seen in the ClearLostSessions - DaysToKeep.  I believe it was thought to make this more customer friendly to modify via the application UI instead of the server configuration editor when this was implemented.

Hopefully this helps.

 

View original
Did this topic help you find an answer to your question?

Forum|alt.badge.img+12
  • Superhero (Employee)
  • June 18, 2024

Hi Chris,

My best guess is that MoveTaskAppointmentToHistory moves Private Activities / Task Appointments to history (instead of purging) with the interval defined in this parameter.
The Expiration Threshold is as defined in the Miscellaneous I setting.

 

Regards,
Joshua


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23
  • Ultimate Hero (Employee)
  • June 19, 2024

HI Christophe,

I confirm Joshua’s guess is correct.

The setting in the configuration editor triggers the action to start the move.  Thus in my case, a setting of 86400 seconds means the move action occurs every 24 hours (daily).

The setting in the application referred in Joshua’s post above refers to eligibility filter to move the data to history.

So between the two settings, once per day any records that are older than 30 days will be moved to history.

Unlike some of the other timers in the global.xml, there is not a setting to determine the eligibility such as seen in the ClearLostSessions - DaysToKeep.  I believe it was thought to make this more customer friendly to modify via the application UI instead of the server configuration editor when this was implemented.

Hopefully this helps.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings