Platform Support
This page provides an overview of notable issues where support is limited due to JADE platform issues (raised via Parsys or JEDI), or support hasn't been implemented within JadeGit yet.
See the project issue tracker for other issues, where you can create new issues for faults or new feature requests for JadeGit in general (whether they should be noted here or not).
Change Tracking
The following table lists entity operations which cannot be performed during development due to issues with the IDE hooks or because support hasn't been implemented yet.
| Entity Type | Function | Issue | Workaround |
|---|---|---|---|
Local Features (on imported classes) | Any | PAR 69387 | None |
References | Inverse Deletion | PAR 66873 | Update references affected when change isn't tracked upfront. |
Translatable Strings | Deletion | PAR 68418 | Remove from locale file within repository directly. |
Schemas | Deletion | PAR 68417 | Delete schema file & folder from repository directly. |
Schemas | Update Text | PAR 67677 | Update schema file within repository directly. |
C# Exposures | Add & Update | PAR 67309 | None |
External Databases | Update | Not Raised Yet | None |
RPS Mappings | Any | Deploy changes directly. | |
Skins | Any | Deploy changes directly. |
Schema Versioning
The following table lists issues with schema versioning during development which impacts accurate change tracking.
| Issue | Problem | Workaround |
|---|---|---|
PAR 67751 | When an entity needs to be versioned during an update, change tracking cannot distinguish if the change is being made in current or latest schema version. | Explicitly version the schema, update entity text in latest schema version, then perform update or delete operation. |
PAR 67678 | When an entity is deleted from latest schema version, change tracking treats it as current schema version when latest entity version doesn't exist. | Update the entity in latest schema version first, then delete it. |
Deployment
The following table lists issues which impact deployment capabilities.
| Issue | Problem |
|---|---|
Cannot handle map file changes efficiently without intermediary re-orgs. | |
Complete JCF support needed to support rename & delete operations for all entity types. | |
PAR 66557 | Cannot remove property after removing from exported package in latest schema version. |
PAR 67022 | Cannot remove interface after removing collection references in latest schema version. |
PAR 67023 | Cannot remove constants after removing references in latest schema version. |
Commands
The following table shows what JADE versions support new JCF commands (proposed by JEDI #457), using which support for deploying these kinds of changes can be implemented by JadeGit.
| Command | 2020 SP1 | 2022 SP1 | 2022 SP2 |
|---|---|---|---|
Delete Application | ❌ | ✔ | ✔ |
Rename Application | ❌ | ✔ | ✔ |
Delete Library | ❌ | ✔ | ✔ |
Rename Library | ❌ | ❌ | ❌ |
Rename Package | ❌ | ✔ | ✔ |
Delete ExportedType | ❌ | ❌ | ✔ |
Delete ExportedFeature | ❌ | ❌ | ✔ |
Delete ExposedList | ❌ | ❌ | ❌ |
Delete HTMLDocument | ❌ | ❌ | ❌ |
Rename HTMLDocument | ❌ | ❌ | ❌ |
Delete RelationalView | ❌ | ❌ | ❌ |
Rename RelationalView | ❌ | ❌ | ❌ |
Orange check marks indicate new command is available, but usage yet to be implemented.
Multi-User Support
JadeGit currently supports development on a single-user JADE database only.
Support for multiple thin-client users connecting to a single-user application server depends on changes needed to retrieve thin-client user configuration.
Support for multiple users/nodes connecting to a database server depends on JEDI #402.
Last updated