3166674 - MDF Workflow Todo category related API issues

Customer is using Todo API or TodoEntryV2 API, and the API returned data is less or more than they expected with MDF todo categories as filter (14, 17, 18, 21, 24, 25, 29, 39, 46). 

It is probably because the Todo category change of MDF objects.

For example:

• /odata/v2/TodoEntryV2?$filter=categoryId eq '39' and status eq '2' and userNav/userId eq '012570' and wfRequestNav/status eq 'PENDING'
• /odata/v2/TodoEntryV2? $filter=categoryId in '46','18','29' and status eq '3' and completedDateTime ge datetime'2021-09-13T05:37' and completedDateTime le datetime'2021-10-13T05:37' and createdDate ge datetime'2020-12-31T16:00' and createdDate le datetime'2021-01-01T15:59'

• SAP SuccessFactors HXM Suite
• Metadata framework (MDF)

This KBA is relevant for the customers who:

- Have Todo category configuration issue or

- Have Todo API use case with MDF Todo category or

- Did not correct the Todo category with Check Tool post b2111

Starting from last release (b2111), SAP SuccessFactors announced deprecation of four to-do categories (24, 25, 39, 46), and defined what todo category should an MDF object belong to.

With the release of b2205, the Todo category configuration for MDF objects will be migrated and hence mapped with correct category automatically. Post this enhancement, customers will not have the control over this configuration and they will not be able to change the pre delivered configuration anymore.

Query Todo and filter them based on latest MDF Todo category.

If you think certain MDF object/s are not mapped to the correct categories as per your expectations, please create a ticket with relevant team to review and discuss your use case.

Todo Category, MDF , workflow , todo , to-do 

KBA , LOD-SF-MDF-OBJ , Object Definition & Field Related Issues , LOD-SF-MDF-WFL , Custom Object based Workflows , Product Enhancement