Andrew, we MUST get this in to the Release Notes as well as it is a change in behavior.

In terms of the regular guides, wherever in the documentation it talks of creating a service, and the entry point can be namespace/class/instance, it must also state that the instance must be and instance of a state machine.  This is most likely in the Automate Guide.  We MUST have a new pdf for this by the 3.2.1 release errata.

Andrew: Once you have the PDF update,..please send directly to me.

It appears we'll be doing a build early part of next week.

Assigning to Shikha for review.

Shikha, we need to add a simple line or two stating the above to sections in the Lifecycle and Automation Guide -

* ⁠5.3.2. Creating a Catalog Item permlink, near Step 5.b.

The initial doc text outlining this can be added to this bug for now; I will search for an engineering bug that might be a better fit for documenting this change.

To provide some more context for the doc text, here is an excerpt from the original mailing list email where this discussion started -

"In CF 3.1 a user was able to choose a non Statemachine entry point for provisioning Service Catalog item.

...


In 3.2 It seems that  Provisioning Entry Point are filtered by /statemachine. All other Entry points do not show up when clicking into the provisioning Entry Point field. Meaning that I am only able to choose an entry point which actually is a statemachine."

Andrew: I'd like to use this issue as the tracker for code changes we're expecting. That being said,...I'm changing the status back to Assigned.

Andrew, I couldn't find one so I'm sending this to Dave.  (It's probably an RFE somehow, but I don't recognize it.)

I don't know of an engineering bug on this.  Sending needinfo to dave johnson in QE.

This issue has been documented in the Red Hat CloudForms 3.2 documentation, which is live on the Customer Portal.

I am closing this bug, but please feel free to re-open it if required for further tracking purposes.

Canceling old needinfo request.