Need to change the change tasks number in proper way

[prasannasun]

when we create change request we get the change tasks created with numbers for example 

CTASK0010082

Implement

and 

CTASK0010081

Post implementation testing

but as part of requirement I wanted the change task numbers differently for implement it should low and for post implement it should be high like etc.

CTASK0010081 - Implement

CTASK0010082 - post implementation task

I wanted number in this order but trying to check everything but nothing worked. Please give me some idea

[J Siva]

Hi @prasannasun 

If you are using templates to trigger the tasks then you can achieve that by modifying the task sequence.

May I know how the change tasks are created? Workflow/template etc.

Regards,

Siva

[AshishKM]

Hi @prasannasun,

Seems like the business logic required to create both task at same time ( e.g. parallel ) , however the best practice, task should be in sequential and post-implementaion task should create when implementation task is closed.

If both tasks are created in parallel mode then CTASK may have this number order issue.

Share more details, how these task are being created.

[Shivalika]

Hello @prasannasun 

There must be something template or workflow that is creating the tasks, you just need to alter the sequence (ORDER) field of task generation and then it will be done. lower order will execute first. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

[Dr Atul G- LNG]

Hi @prasannasun 

These tasks are being generated via Flow/Workflow in Change. You need to check the logic there or check the Change Model where it has been defined. It's just the way the system is creating them. It might be due to some delay added or the order in which things have been described.

These tasks are created from the flow, for example: Change → Normal → Implement. When I tested on my PDI, it behaves the same way as you mentioned.