Extension Data Behavior
Comments
-
[font=Roboto, Arial, Helvetica, sans-serif]Hello. We are trying to find a "quick and easy" solution to passing values into Extension Data. We initially define the values in the flow at the Setup Process Folder step, then we pass different values for each form output path (e.g., Submit, Reject, Save, Timer Exit) through a create data step for each output path. Is there a way to accomplish this change in values only once in the flow, or does a form output revert to the values initially set earlier in the process? Please advise.[/font]
-
[font=Roboto, Arial, Helvetica, sans-serif]Its possible to change the output mappings of the form to Change Data > [Extension Data.Value]. If the forms output data needs to be handled differently for each outcome, then it would be better to use separate Create Data or Mapping Steps to map the output data into the Extension Data of your process.[/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
Howdy, Stranger!
Categories
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions