- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
Subject: Now Assist Flow Generation - Subflows and Run Script Actions
Hi Community,
I am testing Now Assist Flow Generation in Workflow Studio and have observed the following behavior.
For both Subflow and Run Script actions, the flow generation process appears to identify and extract the correct action information from the prompt. For example, I can see that the intended Subflow or script-related details are recognized, and I am even providing the corresponding sys_id in the prompt.
However, after the flow is generated:
- The Subflow action is not automatically connected/configured with the referenced Subflow.
- The Run Script action is not automatically populated/configured as expected.
- Manual configuration is still required after generation.
My questions are:
- Does Now Assist Flow Generation currently support automatically connecting/configuring existing Subflows when the Subflow sys_id is provided in the prompt?
- Does it support creating and populating Run Script actions directly from the prompt, or is manual configuration currently required?
Has anyone successfully generated flows where Subflows and Run Script actions were fully configured and connected without post-generation edits?
Thanks in advance for any guidance.
Solved! Go to Solution.
- Labels:
-
Flow Designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
This is expected behavior at the moment because now assist flow gen is mainly designed to understand your intent and build the overall flow structure using supported actions. It does not have full access to resolve every custom object in your instance, such as a specific Subflow with its inputs and outputs, or to safely generate and configure custom script logic inside a Run Script action. Because of that, it can place the right type of step in the flow, but some of the detailed configuration still needs to be completed manually.
For custom Subflows, you will usually still need to select the correct Subflow yourself and map the required data pills. The same applies to Run Script actions. Now Assist can help build the structure of the flow, but the actual script and some of the more specific configuration still need to be completed manually.
So I would use Flow Generation mainly to create the initial structure and then finish the custom parts yourself. Hopefully this helps explain why you are seeing placeholders instead of a completely configured flow.
If this helped, could you mark it as helpful or as the solution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
This is expected behavior at the moment because now assist flow gen is mainly designed to understand your intent and build the overall flow structure using supported actions. It does not have full access to resolve every custom object in your instance, such as a specific Subflow with its inputs and outputs, or to safely generate and configure custom script logic inside a Run Script action. Because of that, it can place the right type of step in the flow, but some of the detailed configuration still needs to be completed manually.
For custom Subflows, you will usually still need to select the correct Subflow yourself and map the required data pills. The same applies to Run Script actions. Now Assist can help build the structure of the flow, but the actual script and some of the more specific configuration still need to be completed manually.
So I would use Flow Generation mainly to create the initial structure and then finish the custom parts yourself. Hopefully this helps explain why you are seeing placeholders instead of a completely configured flow.
If this helped, could you mark it as helpful or as the solution?
