Differences

This shows you the differences between two versions of the page.

--- en:extensions:workflowdesigner:tasks:flow:requestvalues [2014/12/15 15:37]
swarnat
+++ en:extensions:workflowdesigner:tasks:flow:requestvalues [2021/09/20 00:34] (current)
swarnat
@@ Line 1: / Line 1: @@
 ====== request values from user ====
+https://manuals.redoo-networks.com/wiki/manuals/view/Workflow%20Designer/Workflow%20Actions/User%20Interaction/request%20values%20from%20user/
-This task requests values from the user and store these values in //$env["value"][<variableName>]//.
-**These variables are only available inside custom expressions.**
-The "request values before execution" of the start block behave equal to this block and will be handled absolutely in the same way.
-If you execute a workflow from the sidebar, the variables will be requested directly.
-If the request value block will be reached in an automatic execution (after save or creation), the workflow will be paused on this block and the execution user get an entry on his main front end workflow page, you could open in the Main Menu.
-The workflow will be paused too, if you don't want to enter the variables directly and click "enter values later".
-=== Fieldtypes ===
-Text, Picklist, Checkbox and Date should be clear to understand.
-Reference will list all records from the module you choose, which are related to the current record. It will write the CRMID of the choosen Record into the Environment variable for later usage.
-[[en:extensions:workflowdesigner:developers|Create your own Fieldtypes]]
-=== Example===
-{{:en:extensions:workflowdesigner:tasks:startfields.png?direct|}}
-This will request 3 variable on start, which will result in this form: (Looks different in VtigerCRM 6)
-{{:en:extensions:workflowdesigner:tasks:startfields2.png?direct|}}
-You could access these variables with the ''$env["value"]["..."]'' variable. In this example use
-  $env["value"]["field_1"]
-  $env["value"]["field_2"] # "on" if checked
-  $env["value"]["field_3"]