At the moment, there is no warning to say the system is expiring due to the entitlement server being unreachable before it expires
Can you add a warning message prior to the 30 days to allow end users to act/fix the issue before a system expires
Idea Benefit | entire system will not go down due to an unexpected reason |
How do you solve for this problem today? | fix the issue after the system has expired. |
Product Variant | Sage 200 Professional |
Fixed in version | 2018 (Spring/ Summer/ Winter) |
Implemented in version (specific) | 2018 (Summer) |
An example of this would be if a customers IT made changes on the network which prevented the Licence fetch. The customer then carries on working in Sage 200 without issue for 30 days until suddenly it stops. As they had no reason to check the license status in Sage200 Administration this occurs out of the blue and the changes to the network are not instantly flagged as the issue. A notification of a failed fetch, the number of days this has occurred, to 'Admin' users would instead advise that there is a issue and the recent changes would be looked into/spotted.
This idea is relating to an issue with the gateway not being able to reach the entitlement server not the licence countdown
It does the countdown quietly in the log files but it also reports in System Administration as a failed licence fetch.
Most end users would not have any reason to check the system administration to see if there are any failed licence fetches.
After 30 days of failed licence fetch the system becomes unavailable to the end user until whatever is causing gateway issues is resolved
So what is required is something that brings it to the forefront to the end user so they are able to contact their support team. Maybe via a pop up or email or maybe there is another way to achieve this
Introduced in Summer 2018 the product licence countdown was changed. It originally counted down from 60 days. Based on customer feedback it was changed, the countdown begins at 30 days, then 14 and then 7 days for all users. Please contact your business partner to troubleshoot this further.