 dflaven
|
fd7bc2714a
Bug fix: for archive and obsolescence flags: the parent class may be a pure PHP class. Use ParentPersisteClass instead.
|
il y a 8 ans |
 romainq
|
9f6d33d764
N890.6 Obsolescence: if the expression defining the flag is evaluated to null, then consider the object as being NOT obsoleted. The workaround implemented in the reference datamodel has been removed (no need to use COALESCE anymore).
|
il y a 8 ans |
|
romainq
|
898a6939f6
Obsolescence: fixed the case when an external field points to an external key that is obsoletable (or archivable), causing an error during the setup (view could not be created)
|
il y a 8 ans |
|
romainq
|
0e1f3d02b9
Rework of the edition of 1-N and N-N links: managed as a delta from the GUI down to the the lowest APIs.
|
il y a 8 ans |
 glajarige
|
3057ac020a
N°653 Ticket Lifecycle: Part 2, core & console done.
|
il y a 8 ans |
|
romainq
|
013adc56b5
N.542 Refactored the code so that query placeholders (current_contact->attcode or current_user->attcode) become available in template too.... BUT this will not work if the notifications are sent asynchronously (thus the logged in user is an account dedicated to the cron).
|
il y a 8 ans |
|
romainq
|
5ffb6104a5
Obsolescence: background task setting (or resetting) the obsolescence date for obsolete data. The periodicity can be tuned by the mean of obsolescence.date_update_interval, defaulting to 10 minutes. Also renamed show_obsolete_data into obsolescence.show_obsolete_data for consistency.
|
il y a 8 ans |
|
romainq
|
b246164f18
Obsolescence: finalizing the implementation of the flag (hide obsolete objects, show an icon on hyperlinks and a tag on the object details, user preference defaulting to the new setting 'show_obsolete_data')
|
il y a 8 ans |
|
glajarige
|
850f9bc590
Internal: Added some PHP Doc in MetaModel class
|
il y a 8 ans |
|
romainq
|
4b36e9e017
Obsolescence: introduction of this new concept (wording could change later). The obsolescence of an object is computed after other attributes, by the mean of an OQL expression. The code has been refactored (again) so as to factorize between the computation of friendly names and the computation of obsolescence flags. The refactoring involved a significant AND RISKY change: external key friendly names (magic attributes) have been changed from AttributeFriendlyName to AttributeExternalField, which simplifies the SQL query build logic.
|
il y a 8 ans |
|
romainq
|
a5c61374bd
Internal: getting rid of the unused API GetExtKeyFriends, which initialization was not compatible with the declaration of <extkey>_friendlyname as external fields
|
il y a 8 ans |
|
romainq
|
3109a0a7ca
Internal:
|
il y a 8 ans |
|
romainq
|
d76a5b9cb8
Archives: archivability must be set on root classes
|
il y a 8 ans |
|
romainq
|
1d9b68088c
Archives: default label for the magic attributes archive_flag and archive_date
|
il y a 8 ans |
|
romainq
|
d998853c23
Archives: refactoring of the API to enable/disable the archive mode
|
il y a 8 ans |
|
romainq
|
34ab6cd77b
NEW! Archiving data. Archiving is a soft delete. It can be undone. Enter the archive mode to see all the data including archives (everything is read-only in that mode). Archiving must be enabled per class (data model). Archiving is achieved by the mean of the API DBObject::Archive (or Unarchive).
|
il y a 8 ans |
|
glajarige
|
da0260c569
N°653 Lifecycle flags can be defined on both states and transitions (Note: This is a beta version and need to be tested!)
|
il y a 8 ans |
|
romainq
|
20fc87e4da
Optimization: make it less cumbersome to have the APC user cache enabled for PHP 5.5+. Prior to this enhancement, it used to require a compilation flag (for apcu) until PHP7... then it became mandatory to install a dedicated backward compatibility module named after apcu_bc. Now, having apcu installed and enabled is ENOUGH.
|
il y a 8 ans |
|
romainq
|
e50b8569ad
#1325 Part III - Completing the fix by aligning the internal data structures of iTop... and possibly fix an issue (?) - Not recommended for a retrofit
|
il y a 8 ans |
|
romainq
|
b1d46aab3d
#1325 Part II - Completing the fix by aligning the internal data structures of iTop... and possibly fix an issue (?) - Not recommended for a retrofit
|
il y a 8 ans |
|
romainq
|
9e2419b5fa
#1325 Could not declare an ext key to a subclass (view could not be created). This commit is minimalistic and aims at being retrofitted into the various branches of iTop. It will be followed by a second commit, which aims at completing the fix by aligning the internal data structures of iTop... and possibly fix an issue (?)
|
il y a 8 ans |
|
dflaven
|
eebeeeb210
Regresssion of iTop 2.3.0 beta: properly load the metamodel from the environment.
|
il y a 9 ans |
|
romainq
|
1ad3a6ba7d
#1207 Customization: allow the implementation of interfaces by the mean of abstract classes
|
il y a 9 ans |
|
romainq
|
43d294e036
Internal: query arguments could be array values, making it easier to build dynamic IN() clauses
|
il y a 9 ans |
|
dflaven
|
4ab7616cf5
YOU MUST RUN THE SETUP AFTER PERFORMING THIS UPDATE !!
|
il y a 9 ans |
|
dflaven
|
4d54906d6d
Cleanup and optimization of the handling/loading of the dictionary files.
|
il y a 9 ans |
|
romainq
|
1d2fd7f774
Label of the final class attribute could only be defined on the root class (overriding it in derived classes had no effect)
|
il y a 9 ans |
|
romainq
|
0064a82cd2
Fixed regression introduced with [3912] : autocomplete not working (new User request with lots of existing user requests)
|
il y a 9 ans |
|
dflaven
|
0ec001e1db
Optimization/bug (!): Never use the whole object as a placeholder in ApplyParams !!
|
il y a 9 ans |
|
romainq
|
1d4c9abbfe
Prerequisites for custom fields
|
il y a 9 ans |
