Hi Justin,

You need to run the Timer_SetupOutTracker (in the OutTracker_CS module) to reset your configurations, and the new ones to be taken into account.

Check however if the flow is going over the protection If, in the image below:

It is probably preventing the re-setting of configurations if there are some configurations set up already, so you might need to delete some data before setting it up again.

Kind Regards,
João

Hi @João Marques ,

i checked and it seems the Timer does run on every publish and updates the CaseStatusDefinition entity

upon checking my new status can be seen in the Timer's aggregate

and still on trying the code below it still gives out the "status is not valid.." error

Hi Justin,

With Case Management Framework, you define your configurations which are sent and persisted in the Case Management Framework internal tables.

So what you see in CaseStatusConfiguration is not the status entity in which Case Management Framework relies on but instead the CaseStatus entity in CM_CaseDefinition_CS module:

These configurations are setup on Case Management Framework via the SetupCaseManagementApplication service action which is called on the timer:

Given the explained above, this is not being set up successfully and you can check the status in the table I shared above.

And check Service Center logs / debug to see why this Service Action is not running successfully-

Kind Regards,
João

Hi @João Marques  

thanks was able to make the new status work now. Seems one has to execute the Timer again on the ServiceCenter and check whether the GUIDS are set correctly before running. Checking the CaseStatus helped.