HI @Karim.katif5 ,
This is due to a change in business logic where we have introduced ROLLBACK for a certain functionality.
This can impact for Workflow if you use API task. Since API tasks maintain transaction atomicity and rollback is not allowed in API tasks (more info mentioned in https://docs.ifs.com/techdocs/24r1/040_tailoring/500_business_process_automation/025_considerations/ ).
You can use REST tasks instead. it doesn’t guarantee transaction atomicity and therefore rollback can be used. So using the REST task will be the workaround for this.
Probably in future framework team will generate an upgrade consideration document (workflow) to identify any breaking changes introduced in the specific release code which can impact for existing workflows.
@Lahirumala de Mel Please add your thoughts if I missed anything here.
Yes. As @Masheesh said if your process does not require all API calls to run on the same transaction you can use a IFS REST task, giving the same projection as the URL endpoint. But note that when the Workflow is transferred between environments(Ex: from CFG to UAT) the URL might have to be changed since the server name of the URL differ from env to env.
Hello,
I don’t have a IFS Rest call in this projection CRMCOMPANIONAPP.