Genesys Cloud - Developer Community!

The only option to validate a work plan is to pass in the information about the work plan. If you are creating or otherwise have the work plan 'in hand', you already know the values to fill in for a validate step. On the API side the create, get, and validate method for work plans all have essentially the same set of fields.

May I ask why you need to create work plans via the SDK? That seems like such a low value high effort task (unless it is to support some large migration of an org).

hi Jay, thanks for the reply. I also raised a Genesys case after this post for this and I got confirmation that the documentation is incorrect, the body must be set when doing a verification.

I already modified my code and the validation works but it is painful that i need to create a new object and copy over a 10+ properties one by one. For example, the object i have is "WorkPlan" but the object type needed for validation body is "WorkPlanValidationRequest" so i end up copying over attributes one by one, this is painful and it will also break if new attributes are added in the future.

the answer your other questions, we are doing a mass deployment and we need to perform a lot of workplan addition so developing this script will save time.

Zsolt

The only option to validate a work plan is to pass in the information about the work plan. If you are creating or otherwise have the work plan 'in hand', you already know the values to fill in for a validate step. On the API side the create, get, and validate method for work plans all have essentially the same set of fields.

May I ask why you need to create work plans via the SDK? That seems like such a low value high effort task (unless it is to support some large migration of an org).

Unfortunately we do not have another way to do this via the SDK. I'm not sure why it's showing the body of the route you referenced as being optional, because as far as I'm aware there are no cases in the workforce management APIs where the entire request body is optional. We will look into that.

I already modified my code and the validation works but it is painful that i need to create a new object and copy over a 10+ properties one by one. For example, the object i have is "WorkPlan" but the object type needed for validation body is "WorkPlanValidationRequest" so i end up copying over attributes one by one, this is painful and it will also break if new attributes are added in the future.

This should be something you can write a single time and then loop as many times as needed. You can set up a method in your script that takes whatever parameters are needed and pass them in. Hope that helps.

hi Jay, thanks for the reply. I also raised a Genesys case after this post for this and I got confirmation that the documentation is incorrect, the body must be set when doing a verification.

I already modified my code and the validation works but it is painful that i need to create a new object and copy over a 10+ properties one by one. For example, the object i have is "WorkPlan" but the object type needed for validation body is "WorkPlanValidationRequest" so i end up copying over attributes one by one, this is painful and it will also break if new attributes are added in the future.

the answer your other questions, we are doing a mass deployment and we need to perform a lot of workplan addition so developing this script will save time.

Zsolt

The only option to validate a work plan is to pass in the information about the work plan. If you are creating or otherwise have the work plan 'in hand', you already know the values to fill in for a validate step. On the API side the create, get, and validate method for work plans all have essentially the same set of fields.

May I ask why you need to create work plans via the SDK? That seems like such a low value high effort task (unless it is to support some large migration of an org).