When building out change worklfows, where is the best practice for auto generating CTASK

[Mary35 · Accepted solution]

Atul, 

Is this a customized option to add task during creation on the workflows? If so would it impact the future upgrades. We are going to OOB and the team is looking at task to be auto generated once you select Implement. 

Would it be a customization to turn them off and have them manually add the task prior to approvals? 

Thanks for your input! 

[Dr Atul G- LNG]

Hi @Mary35 

Greetings!!

When you talk about best practices it mainly depend on business nature. If you ask me,

CTask must be created before change move to approval state.

All information added in ctask including any detailed steps etc.

Only specific type of ctask raised in specific state.

[Mary35 · Accepted solution]

Atul, 

Is this a customized option to add task during creation on the workflows? If so would it impact the future upgrades. We are going to OOB and the team is looking at task to be auto generated once you select Implement. 

Would it be a customization to turn them off and have them manually add the task prior to approvals? 

Thanks for your input! 

[Dr Atul G- LNG · Accepted solution]

Hi @Mary35 

No, it is not considered customization, it is a configuration. Better copy the OOTB workflow and add your own steps in same.  SO that during upgrades it not create problem