Support changing the id of a given element in the process

[nkylstad]

Description

From v4 of app frontend, the process task id is exposed in the url of the app.
This will probably result in some wishes to change the id, as "Task_1" (which is our default task name) is not exactly descriptive of what the task is to the end user.

The taskID is used in the following configurations:

• The process itself
• applicationMetadata - multiple configurations, including:
  • data types
  • eFormidling config
• the policy file
• potentially also the layout-sets file (depending on where we land on dealing with layout sets)

Should probably inform user about where changes will be done when they change the task ID.

We should look into using the bpmn editor for the actual process file updates, and running our own code to update the other config files.

Tasks

Preview Give feedback

1. Detect taskId changes in frontend and send the metadata along with xml payload #12218
   app-fe-v4 status/ready-for-dev +2
2. Process-editor: Enable editing of taskID in config panel #12272
   app-fe-v4 area/process +2
3. Implement validation for taskId #12597
   0 of 1
   area/process +1
   
4. Add mediator and setup init event infrastructure #12219
   app-fe-v4 +1
   
5. Publish event when taskId is changed #12225
   app-fe-v4 +1
   
6. Add signalR hub for sync errors #12265
   app-fe-v4 +1
   
7. Add eventhandler for applicationmetadata #12220
   app-fe-v4 +1
   
8. Add event handler for policy file #12221
   app-fe-v4 +1
   
9. Add event handler for layout-sets file #12222
   added-to-sprint app-fe-v4 +2
   
10. Establish connection to sync-error SignalR hub #12266
    app-fe-v4 status/ready-for-dev +2
11. Create global error handling based on sync errors notifications #12267
    app-fe-v4 status/ready-for-dev +2
12. Implement sync success notifications #12401
    app-fe-v4 +1
    

[nkylstad]

Ref. presentation from @mirkoSekulic on using events to ensure correct syncing of files. Could this be a candidate to start testing that setup with?

[mirkoSekulic]

@nkylstad Yes. I think it's a good starting issue.

[nkylstad]

All tasks done. Closing.