romainq
|
1ad3a6ba7d
#1207 Customization: allow the implementation of interfaces by the mean of abstract classes
|
9 years ago |
romainq
|
43d294e036
Internal: query arguments could be array values, making it easier to build dynamic IN() clauses
|
9 years ago |
dflaven
|
4ab7616cf5
YOU MUST RUN THE SETUP AFTER PERFORMING THIS UPDATE !!
|
9 years ago |
dflaven
|
4d54906d6d
Cleanup and optimization of the handling/loading of the dictionary files.
|
9 years ago |
romainq
|
1d2fd7f774
Label of the final class attribute could only be defined on the root class (overriding it in derived classes had no effect)
|
9 years ago |
romainq
|
0064a82cd2
Fixed regression introduced with [3912] : autocomplete not working (new User request with lots of existing user requests)
|
9 years ago |
dflaven
|
0ec001e1db
Optimization/bug (!): Never use the whole object as a placeholder in ApplyParams !!
|
9 years ago |
romainq
|
1d4c9abbfe
Prerequisites for custom fields
|
9 years ago |
dflaven
|
ccf403a397
(HTML) Formatted Case Logs, Description and Notifications with inline images uploaded as Attachments. Beta Version !!
|
9 years ago |
romainq
|
1c5dc468d5
Magic query arguments:
|
9 years ago |
romainq
|
7f46108d88
New type of attribute: AttributeMetaEnum.
|
9 years ago |
dflaven
|
46fe2f3221
Do not rely on MetaModel::GetRootClass() to check the data model, use the abstraction of ModelReflection instead to keep the code portable.
|
9 years ago |
dflaven
|
d9653c3e57
Preserve the initial sort order on lists by determining the default sort order of the tables based on the equivalence between the "friendlyname" and another actual field of the class.
|
9 years ago |
romainq
|
b2618d03ae
Exports further improved:
|
9 years ago |
romainq
|
eaee9c5ddc
Exports: a fields spec can now be an extended attribute code (e.g. location_id->org_id->parent_id->code)
|
9 years ago |
romainq
|
5ed735e8d0
#942 OQL now supporting unions. Unions support polymorphism and can be used anywhere in the application.
|
10 years ago |
dflaven
|
5571c138ae
A little bit of polishing on the impact analysis feature...
|
10 years ago |
dflaven
|
bf800862db
Relations & Impact analysis enhancements:
|
10 years ago |
dflaven
|
76a43b3264
Integration of the new impact analysis into the tickets.
|
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
|
2c4841693c
Integration of the new way to compute relations into the datamodel (ComputeImpactedItems)
|
10 years ago |
romainq
|
cb006da414
#1069 Added a default value to the column definitions whenever possible: makes it less a pain to add a new hierarchical key when there are already some records in the DB
|
10 years ago |
romainq
|
c97fa8049f
XML Modelization of the relations: no option to restrict the browsing to downstream
|
10 years ago |
dflaven
|
0ea7084670
Replacement of the impact Flash based analysis graph by graphviz + Raphael + TCPDF. ALPHA version.
|
10 years ago |
romainq
|
815e3563d3
Rework of the relation diagrams: configuration of the redundancy (AttributeRedundancySettings)
|
10 years ago |
romainq
|
2151413df9
Rework of the relation diagrams: implemented MetaModel::GetRelatedObjectsUp, and took the redundancy into account (still misses a GUI)
|
10 years ago |
romainq
|
c89f6ecfb0
Rework of the relation diagrams: implemented MetaModel::GetRelatedObjectsDown (still not taking the redundancy into account)
|
10 years ago |
romainq
|
8ecee4985a
XML Modelization of the relations: reworked toward an asymetric definition (downstream: A impacts B, upstream: B depends on A)
|
10 years ago |
romainq
|
f2a3b8237f
XML Modelization of the relations, with full support of the previous way (by implementing a method GetRelationQueries). Still, the standard data model has not been migrated to the new format.
|
10 years ago |
romainq
|
a80cf12522
OQL enhancement: continuation... (bug fix with a query on object history)
|
10 years ago |