[Feature] Workflow Migration #2325
Conversation
auslin-aot
force-pushed
the
FWF-3718-workflow-migration
branch
2 times, most recently
from
7e48501 to
720e902
Compare
auslin-aot
force-pushed
the
FWF-3718-workflow-migration
branch
from
720e902 to
1ac5851
Compare
| @classmethod | ||
| def migrate(cls, request): | ||
| """Migrate by process key.""" | ||
| current_app.logger.debug("Migrate process started..") |
There was a problem hiding this comment.
Migration needs to happen only for all the other mappers with same process_key and keep the same for the one which initiates it. For e.g, if Workflow1 is used by Form1, Form2 and Form3. Then when the user saves Form2 and decides to keep the workflow for that form, then Form1 and Form3 needs new workflow (cloned)
There was a problem hiding this comment.
yes picking the mappers excluding the mapperId provided in the payload & adding the new workflow for other form mappers
|
|
||
| def upgrade(): | ||
| # ### commands auto generated by Alembic - please adjust! ### | ||
| op.add_column('form_process_mapper', sa.Column('is_migrated', sa.Boolean(), nullable=True, comment="Is workflow migrated", server_default='false')) |
There was a problem hiding this comment.
We will also need to set the value to TRUE for workflows (process) with only one form linked, right ?
There was a problem hiding this comment.
As of now, it's done as part of getting by process key API. After fetching from camunda & is_migrated set to True for workflows (process) with only one form.
There was a problem hiding this comment.
done. Added is_migrated TRUE for workflows with only one form linked to the migration file
…low-ai into FWF-3718-workflow-migration
…e form linked to migration file
…low-ai into FWF-3718-workflow-migration
|
Issue Tracking
JIRA:
Issue Type: BUG/ FEATURE
https://aottech.atlassian.net/browse/FWF-3718
https://aottech.atlassian.net/browse/FWF-3841
Changes
Workflow Migration
mapperIdto get by process key API to support migration.If process_key is not found, if the mapper is not migrated then workflow fetched from camunda
-
http://localhost:5000/process/key/<process-key>?mapperId=1http://localhost:5000/process/migratewith payload { "mapperId":"mapper-id", "processKey":"process_key"}Screenshots
Migrate api
Checklist