Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | |||||||||||
0014676 | |||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
design defect | [Openbravo ERP] A. Platform | minor | have not tried | 2010-09-23 15:02 | 2022-02-01 08:08 | ||||||
Reporter | plujan | View Status | public | ||||||||
Assigned To | Triage Platform Base | ||||||||||
Priority | normal | Resolution | open | Fixed in Version | |||||||
Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
Projection | none | ETA | none | Target Version | |||||||
OS | Any | Database | Any | Java version | |||||||
OS Version | Database version | Ant version | |||||||||
Product Version | main | SCM revision | |||||||||
Review Assigned To | |||||||||||
Web browser | |||||||||||
Modules | Core | ||||||||||
Regression level | |||||||||||
Regression date | |||||||||||
Regression introduced in release | |||||||||||
Regression introduced by commit | |||||||||||
Triggers an Emergency Pack | No | ||||||||||
Summary | 0014676: DE007 After the warning message in login, I have no other information about what modules have expired. | ||||||||||
Description | After the warning message in login, I have no other information about what modules have expired. | ||||||||||
Steps To Reproduce | 1. Log in an instance with an Active subscription. One installed module's license has expired yesterday 2. As SysAdmin, you receive a warning message 3. Continue and go to MMC. All installed modules look the same. 4. Go to instance activation, there is no modules list, nor individual expiration dates, so basically the only way to recall what modules were expired is to log out and log in again. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0031536) alostale (manager) 2010-10-01 11:10 |
Proposed solution: Display in Instance Activation window a list of installed commercial modules with their expiration date. |
(0042995) johnfandl (reporter) 2011-11-18 17:36 |
It is true that individual commercial modules may have an expiration date different from the overall subscription--and the UI does not provide visibility into expiration dates of individual modules. Instead of adding individual modules to the Activation screen (which does not have module details now), it may make more sense to add the "Expiration Date" to the MMC "Installed Modules" tab, with ability to sort by the expiration date. Perhaps best is to upgrade this screen at some point to use a Smartclient control like this example: http://www.smartclient.com/#_Trees_Sorting. [^] So, the parent would have the earliest expiration date of all of its children. |
(0046976) alostale (manager) 2012-03-30 13:05 |
Setting as design defect: New design is required to display this info and it needs to be decided whether should be in instance activation window or in module management. |
(0052475) AugustoMauch (administrator) 2012-09-24 23:28 |
Effort: 1 Impact: mid Plan: mid |
Issue History | |||
Date Modified | Username | Field | Change |
2010-09-23 15:02 | plujan | New Issue | |
2010-09-23 15:02 | plujan | Assigned To | => alostale |
2010-09-27 08:59 | alostale | Status | new => scheduled |
2010-10-01 11:10 | alostale | Note Added: 0031536 | |
2010-10-14 08:34 | alostale | Target Version | 2.50MP23 => 2.50MP25 |
2010-12-13 16:45 | alostale | Target Version | 2.50MP25 => 2.50MP26 |
2011-02-07 08:33 | alostale | Target Version | 2.50MP26 => |
2011-11-18 17:36 | johnfandl | Note Added: 0042995 | |
2012-03-30 13:05 | alostale | Note Added: 0046976 | |
2012-03-30 13:05 | alostale | Type | defect => design defect |
2012-09-24 23:28 | AugustoMauch | Note Added: 0052475 | |
2012-09-24 23:28 | AugustoMauch | Priority | urgent => normal |
2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
2017-04-10 14:34 | alostale | Assigned To | alostale => platform |
2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
Copyright © 2000 - 2009 MantisBT Group |