 dflaven
|
a218fb419e
Bulk Export redesign... Typo in dict entry name.
|
10 years ago |
|
dflaven
|
47e596aa0b
Bulk Export redesign, addressing the tickets:
|
10 years ago |
|
dflaven
|
dc265ab87f
New look for iTop !
|
10 years ago |
|
dflaven
|
1146642677
New look for iTop !
|
10 years ago |
|
dflaven
|
e493fd7f48
Added an alternate implementation for storing "transaction" identifiers on disk instead of inside the $_SESSION variable.
|
10 years ago |
|
dflaven
|
2ea54b8644
Mutex instrumentation for troubleshooting...
|
10 years ago |
 romainq
|
a3ac3a60ff
JSON/REST: When specifying a case log entry (or the whole), it was not possible to set the user name without knowing a valid user id
|
10 years ago |
|
dflaven
|
5551f50e4e
Make sure that the SQL mutexes are specific to the current iTop instance, but still preserving the capability for the setup to detect an already running cron job with or without a valid config file.
|
10 years ago |
|
romainq
|
c5b0b80b11
Integrated the lexer/parser build tools (Lexer=0.4.0, Parser=0.1.7)
|
10 years ago |
|
dflaven
|
a886de7dbb
Impact analysis diagram is now considered as beta !
|
10 years ago |
|
romainq
|
2df37cedd7
Implemented GetForJSON and FromJSONToValue for AttributeLinkedSet (though this is not used for the Rest/JSON services which are doing much more) -retrofit from branch 2.1.0
|
10 years ago |
|
romainq
|
22e3f8fd29
Make it possible to overload RestUtils (static methods called with static:: instead of self::) - iTop NOW REQUIRES PHP 5.3: we have verified, there are very installations of iTop made on PHP 5.2. It is worth to note that PHP 5.3 is already end of life (5.4 will become end of life in 8 months)
|
10 years ago |
|
dflaven
|
bf800862db
Relations & Impact analysis enhancements:
|
10 years ago |
|
dflaven
|
badf45f3b5
Automatically save the PDF of the impact analysis as an attachement to the ticket.
|
10 years ago |
|
dflaven
|
c44f391f36
Removed unused function parameter.
|
10 years ago |
|
dflaven
|
9548d067ed
Default value (=empty array) for excluded objects
|
10 years ago |
|
dflaven
|
e17b81d6c8
Impact analysis diagram uses jQuery context menus.
|
10 years ago |
|
dflaven
|
76a43b3264
Integration of the new impact analysis into the tickets.
|
10 years ago |
|
dflaven
|
2147e65a32
More options for the PDF export of the 'impact' graph.
|
10 years ago |
|
dflaven
|
587c2c3ffe
Optimization of DisplayBlock::FromObjectSet, load only the needed column!
|
10 years ago |
|
romainq
|
4688735bac
XML Modelization of the relations: wrong computation of the upstream query (wrong computation of the redundancy when an Application Solution is made of CIS of various types)
|
10 years ago |
|
dflaven
|
c75766edb2
Relation diagrams:
|
10 years ago |
|
romainq
|
8e646e72de
Enable queries on the synchronized objects (SynchroReplica::dest_id changed into an attribute of type AttributeObjectKey).
|
10 years ago |
|
romainq
|
51c07f3900
#1079 DBWriteLinks deleting related objects
|
10 years ago |
|
dflaven
|
4fa6ce55c4
Make sure that 'source' nodes for ComputedImpactedItems are not added twice to the ticket.
|
10 years ago |
|
dflaven
|
2c4841693c
Integration of the new way to compute relations into the datamodel (ComputeImpactedItems)
|
10 years ago |
|
romainq
|
62ad0e8e0b
#1069 (continuation of commit 3558) There may be some null values in the Database, making it impossible to upgrade. Defining a default value is far enough for external keys and hierarchical keys. Furthermore, this will be less time consuming during the setup (no need for table scans)
|
10 years ago |
|
romainq
|
e9c9f2bf19
Code refactoring: coloring a relation graph (purpose: distinguish potentially impacted CIs and really impacted CIs, when analyzing a change ticket)
|
10 years ago |
|
romainq
|
f8c00e5065
Improved the symptom when an error occurs in the "apply stimulus form". The symptom used to be: Object could not be written; unknown error. Now it will give the error message (e.g. Missing query arguments) so as to help in determining what's going on.
|
10 years ago |
|
romainq
|
d15faba600
ormStopWatch::GetElapsedTime not working in case of queries containing :this-> parameters (the prototype of GetElapsedTime has changed and is NOT compatible with the previous one)
|
10 years ago |
