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.5K All Categories
- 87 General
- 13 Training
- 213 Installation / Setup
- 1.2K Flows
- 112 Rules
- 277 Administration
- 215 Portal
- 503 General Q & A
- 722 Forms
- 356 Reports
- 3 Designer Extensions
- 47 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 190 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 72 Repository
- 238 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 26 Active Directory
- 12 Version 7
- 37 Version 8
- 143 Lunch And Learn Questions