PRs:

• #30950 now when an existing contentlet tries to fire a workflow in a … #30992
• #30950 QA feedback #31020

In order to test this issue, please see postman, the Workflow Resource Test / SavingOnDiffLanguageByActionId
it creates a French language
creates a content in english
and finally creates a content in french, but with the same id of the previous step

Needs Work: This case is not working propertly

• Create a ContentType named type_1 with 2 fields: title and secondField, both Text
• Create a couple of locales, French and Italian
• Create a new Contentlet from the Content Type created previously with: title: English; secondField: A
• Now create a new version of the Contentlet but for French, using the new Workflow

Method: PUT
URL: {dotcmsEndpoint}/api/v1/workflow/actions/ceca71a0-deee-4999-bd47-b01baa1bcfc8/fire?identifier={content identifier}&lang=1&indexPolicy=WAIT_FOR
body: 
{
    "contentlet":{        
        "identifier":"content Identifier",
        "languageId":"French Id",
        "contentType":"Type1",
        "title":"French",
        "secondField": "B",
        "contentHost":"default"
    }
}

• Now create a new version of the Contentlet but for Italian, using the new Workflow

Method: PUT
URL: {dotcmsEndpoint}/api/v1/workflow/actions/ceca71a0-deee-4999-bd47-b01baa1bcfc8/fire?identifier={content identifier}&lang={French Language Id}&indexPolicy=WAIT_FOR
body: 
{
    "contentlet":{        
        "identifier":"content Identifier",
        "languageId":"Italian Id",
        "contentType":"Type1",
        "title":"Italian",
        "contentHost":"default"
    }
}

The secondField value should be B because the original is the French version but it is A

Needs Work:

• If you set a language that does not exists as target then you got a 500 HTTP response error and the message is not readable at all

{
    "message": "ERROR: insert or update on table \"contentlet\" violates foreign key constraint \"fk_contentlet_lang\"\n  Detail: Key (language_id)=(999999) is not present in table \"language\"."
}

• If you set the target language Id as "0" or something like "00000", then you got 200 and the Default language version got updated

• If you set a Contentlet that does not exists in the request body or the query parameter, you got a 400 HTTP Response and the not readable message

{
    "message": "The content (id da3a57919d33396651637b624a5b80ac, inode 9b4c3e44-5a3c-4ad0-950b-cbc0bbceeb3a, content type type_1) is not a new, live, or working version."
}

Looking at the feedback

PR to fix the feedback

Note: on the postmans I have found a mistake, the query string is using lang=1 for setting the language id, it is "language" instead

Note1: now when trying to create a contentlet with a non existing language, it returns 400 bad request.
In addition the validation has been pushed on the validateContent on the ContentletAPI so any checkin with a non existing language will throw a DotState Exception