Best practice forum (Archived)

该论坛讨论已删除

 
该论坛帖子已被删除
2014年01月6日 Monday 09:36
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月6日 Monday 10:22
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月7日 Tuesday 10:20
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月7日 Tuesday 10:59
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月7日 Tuesday 11:14
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月7日 Tuesday 11:58
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月8日 Wednesday 02:07
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2014年01月8日 Wednesday 11:44
该论坛帖子的内容已被删除,无法再访问。
Curry (Core Developer)David
Re: Certifications not working
Curry (Core Developer)David 发表于 2014年01月9日 Thursday 19:03
小组 Totara

Hey Liz,

I tested this today. It took me a while to get my head around how everything is supposed to work, but it is working.

I created a certification that was valid for 3 years with a 3 month recertification window, then tested uploading a range of dates and got the expected results (keeping in mind today is the 10th Jan 2014).

user020, 01/01/2010 - Expired
user021, 01/01/2011 - Expired
user022, 01/01/2012 - Valid
user023, 01/01/2013 - Valid
user024, 01/01/2014 - Valid
user025, 01/12/2010 - Expired
user026, 01/01/2011 - Expired
user027, 01/02/2011 - Window open & Renewal due
user028, 01/03/2011 - Window open & Renewal due
user029, 01/04/2011 - Window open & Renewal due
user030, 01/05/2011 - Valid

I was expecting the window to open after expiry not in the last 3 months, but this makes a lot more sense as this should keep the certification valid at all times. The expired users still had the certification assigned to them but they had to go back through the original certification path the regain the certification. The users with the window open do have the renewal status set as due, though it was also always marked as overdue which I'm going to have to look into further.

certifupload_openwindow.png

Since you have employees who took the original certification longer than 5 years ago, can I assume they have done the recertification in that time? are you uploading multiple records for the same user? There were some issues about multiple records for the same user recently that were fixed in 2.5.5, perhaps there is still some more to do. Let me know and I will look into it further.

Cheers,
David