FOUR-12173: Develop Wizard Template database schema #5706
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces two migrations to enhance the database schema. The changes include:
Migration to Add a
asset_type
toprocess_templates
:add__asset_type_column_to_process_templates
) to insert a string column after the existingis_system
column in theprocess_templates
table.Migration for
wizard_templates
Table:create_wizard_templates_table
) to define the schema for thewizard_templates
table.id
,uuid
,process_template_id
,process_id
,media_id
, and timestamps.process_id
andmedia_id
columns.Reason for the Changes
The additions to the database schema were necessary to accommodate new requirements and improve data management for the development of Wizard Templates.
Checklist
process_templates
table.wizard_templates
table with appropriate foreign key constraints.Testing
Migration Stability:
php artisan migrate
php artisan migrate:rollback --step=2
wizard_templates
Table:process_templates
Table:asset_type
or actual name) afteris_system
.Rollback Effects:
wizard_templates
deletion andprocess_templates
rollback to the previous state.These steps cover essential aspects of migration stability, table and column creation, rollback effects, and functional verification. Adjust the steps based on your specific requirements.
Related Issues
Ticket FOUR-12173
Screenshots
Code Review Checklist