CreateSchedule should reject an empty workflow ID, or generate one

[antmendoza]

Is your feature request related to a problem? Please describe.

Temporal server should validate and either reject or generate a UUID for an empty Workflow ID when a schedule is created.

Some users and customers have schedules triggering at the same time, which can cause the workflows they start to collide on Workflow ID unintentionally.

Each client behaves diferently:

• temporal cloud allows empty string
• temporal UI (comunity) does allow submiting the form with empty value

[ayushsarode]

@antmendoza can you please assign me for this work?

[karasowles]

@ayushsarode this is a feature request board that is solely for awareness of what features users want to see. It is not a place where we are logging in-progress issues or assigning work to contributors. more context here: #12088

[Quinn-With-Two-Ns]

CreateSchedule should probably reject an empty workflow ID, it is intended to be a require parameter. I am surprised it is not

[dnr]

I had a plan a long time ago to make it optional and default to the schedule id if not set. In many or most cases it makes sense for the schedule id and the workflow id [prefix] to be the same, so making that the default seems good.

[antmendoza]

makes sense