1. Does G-Delta Only Work with XTS Import?
2. What databases does G-Delta work with?
3. Does G-Delta work with G-Migration+?
4. Are any additional Ports needed for G-Delta?
5. Do any additional IPs need to be whitelisted for G-Delta?
6. Who should be a G-Delta Admin in an organization?
7. How do I assign the G-Delta Admin role to users?
8. When will G-Delta Admins receive email notifications?
9. Can more than one G-Delta Admin be assigned to a G-Delta?
10. Can I create more than one G-Delta Configuration for a Project Version?
11. How often should G-Delta Requests be submitted?
12. How long does it take for an Audit Report to be available?
13. What happens if no new audits are found?
14. What if G-Delta is interrupted during the Audit process?
15. What happens if no decisions are made for an Audit Report, and the set time interval passes?
16. If I reject an audit in a report, will it be included in the next report?
17. I submitted an audit request and never received the report. Why?
18. My Domain shows the changes but not the Scenario. Why?
19. Once the Audit is approved, what parts of the test data project are refactored?
20. If a new Attribute is added, do I need to assign/tune a Generator?
21. Will a new Receiver be added if a new Domain is added?
22. Will a Scenario be created if a new Domain is added?
23. Will G-Cases/G-Questionnaire change when G-Delta Refactors the Changes?
24. Will G-Rules/G-Queries change when G-Delta Refactors the Changes?
25. What happens if a Domain or Attribute is deleted and has references?
1. Does G-Delta Only Work with XTS Import?
- G-Delta can work with any Domain Creation or Import method as long as the Database metadata is present within the Domain itself and the G-Repository Server is active.
2. What databases does G-Delta work with?
- G-Delta works with SQL databases. The most common SQL databases have been tested by our team.
3. Does G-Delta work with G-Migration+?
- G-Delta does not work with G-Migration+ at this time.
4. Are any additional Ports needed for G-Delta?
- No additional ports are needed to use G-Delta, only those required by G-Repository.
5. Do any additional IPs need to be whitelisted for G-Delta?
- No additional IPs need to be whitelisted.
6. Who should be a G-Delta Admin in an organization?
- A G-Delta Admin should be an individual in your organization who knows the database being audited and the Project Version that will be modified.
- Users with the Org Admin role automatically have permission to create and manage G-Deltas. They do not have to be assigned the G-Delta Admin role.
7. How do I assign the G-Delta Admin role to users?
- An Org Admin can view the My Organization page and edit the individual user. Available roles appear in the provided form. Please see this article for more details: User Management Overview.
8. When will G-Delta Admins receive email notifications?
- G-Delta Admins will receive email notifications for new audit reports, successful refactoring, refactoring errors, and when no new audits are found.
9. Can more than one G-Delta Admin be assigned to a G-Delta?
- Yes, more than one G-Delta Admin can be assigned. It is not recommended to have a large number of G-Delta Admins.
10. Can I create more than one G-Delta Configuration for a Project Version?
- No, only one G-Delta Configuration can exist per Project Version.
11. How often should G-Delta Requests be submitted?
- It is best practice to not submit a large number of G-Delta requests each day.
- Reports can be automatically provided at time intervals between 12 and 24 hours.
- Alternatively, an ad hoc option is provided for requesting an audit report.
12. How long does it take for an Audit Report to be available?
- It takes approximately 3 minutes in most instances.
13. What happens if no new audits are found?
- G-Delta Admins receive an email stating that no new audits were found, and it will check again at the specified time interval.
14. What if G-Delta is interrupted during the Audit process?
- Fault tolerance is built into G-Delta, meaning that when an unexpected issue occurs that interrupts the audit process (e.g., G-Repository Server being down), the audit process will resume from the point where it was interrupted (e.g., G-Repository Server restarted).
15. What happens if no decisions are made for an Audit Report, and the set time interval passes?
- If no decisions have been made, the report will be auto-rejected, and a new report will be created.
- However, if at least one decision has been made, no new report will be provided until the current Audit Report is accepted or rejected.
16. If I reject an audit in a report, will it be included in the next report?
This will vary on the detected difference. Below are two examples:
- A column's data type and size were changed within the database schema.
- The user rejects the recommended actions.
- When the next report is generated, the differences are picked up again.
- It will keep showing up until accepted or the size and type are changed back in the database schema.
- A column is renamed in the database schema.
- The recommended action is to delete the existing Attribute and create a new one with the new name.
- The user modifies the recommended action to rename the existing Attribute.
- Other related recommended action(s) will be automatically rejected.
- When the next report is provided, these differences will not be included in the new report.
17. I submitted an audit request and never received the report. Why?
If you do not receive a new audit report or an email stating no new audits are available, please check the following:
- Verify that G-Repository can access the database.
- Verify the JDBC Config File (config.properties) path and name are correct in the G-Delta configuration.
- Verify the right G-Repository Server has been selected in the G-Delta configuration.
- Make sure the G-Repository Server is running.
18. My Domain shows the changes but not the Scenario. Why?
- During refactoring, changes cascade down from the Domain (Template) level to the Scenario level.
- However, if the Scenario is locked, those changes will not be made to the Scenario during refactoring.
19. Once the Audit is approved, what parts of the test data project are refactored?
- What gets refactored will depend on the database change and the decisions made within the Audit Report.
- The following are some components that can be refactored:
- Domains, Attributes, Relationships, Scenarios, Scenario Chains, G-Cases, G-Rules, G-Queries, G-Families, and G-Questionnaires.
20. If a new Attribute is added, do I need to assign/tune a Generator?
- The data warehouse will automatically assign a Generator. However, it is best practice to check the assigned Generator, as Generator Tuning may be required.
21. Will a new Receiver be added if a new Domain is added?
- Yes, G-Delta will look at what Receiver has been added to other Domains in the Project Version and assign the same Receiver to the new Domain.
- If not all Domains have the same assigned Receiver, then no Receiver will be assigned to the new Domain.
22. Will a Scenario be created if a new Domain is added?
- Yes, G-Delta will automatically create a Scenario for the new Domain. Additionally, the Scenario will be added to a Scenario Chain Set if it exists in the Project Version.
23. Will G-Cases/G-Questionnaire change when G-Delta Refactors the Changes?
- Yes, if the added/deleted Domain or Attribute has references in a G-Case or G-Questionnaire, it will be impacted when the approved changes are synced to the Project Version.
24. Will G-Rules/G-Queries change when G-Delta Refactors the Changes?
- Yes, if the deleted Domain or Attribute has references in a G-Query or G-Rule, it will be impacted by the G-Delta when the approved changes are synced to the Project Version.
25. What happens if a Domain or Attribute is deleted and has references?
- Refactoring changes will depend on where the Domain or Attribute is referenced (e.g., Scenario, G-Case, G-Rule, G-Query, etc.) as well as any Parent-Child-Sibling relationship changes.
- This makes it highly important to copy the Project Version before going through the Audit process when a Project Version has many references.
- Copy the Project first, then review the Audits and approve the report to be refactored to the new Project Version. This ensures the old version is still available for reference in case one of these items is removed.