MohammadMu99 commented on issue #2421:
URL: 
https://github.com/apache/incubator-kie-issues/issues/2421#issuecomment-6623339376

   Hi all 👋
   
   The linked PR (apache/incubator-kie#7259) covers the **first step** of this 
issue: variable `rename`, `default` and `remove` rules.
   
   I've already built a few more extensions to migration plans in my own 
project, and I'd be happy to contribute them as follow-up PRs.
   
   ### Planned extensions
   
   |   | Extension | What it does |
   |---|-----------|--------------|
   | 1 | **Variable type conversion** | Changes a variable's type during 
migration when the new process version expects a different type. |
   | 2 | **Completed node migration** | Marks nodes as completed when the new 
version adds nodes *before* the point an instance has already reached, so the 
instance's state matches the new definition. |
   | 3 | **Node restart** | On a node mapping, instead of only remapping the 
ID, cancels the active node and starts the target node again on the new 
version. |
   | 4 | **Conditional rules** | An optional condition on any plan entry (node 
mapping, variable rule or completed node), so it applies only to instances 
whose variables match, e.g. `amount > 1000`. |
   
   ### Open question: JSON format
   
   All of these already work in my project, but the JSON shape in the `.mpf` 
file is my own design so far.
   
   If anyone would like to discuss the JSON format (naming, structure, or how 
these fit with the existing `nodeInstanceMigrationPlan`), I'd be happy to agree 
on whatever standard fits the project best **before** opening the PRs.
   
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to