Action flow entity inputs missing properties
Comments
-
[font=Calibri, sans-serif]We like to debug action flows inside entity configuration folders, but when we debug these flows, the input mapper shows only the custom properties, not the fundamental properties (like created_on_date or ID). We need the ID to debug the flow. Previously, we could define the ID and the debugger would fetch the entity and run it throw the flow correctly. But now that we can’t see the ID input, we have to wrap all of our action flows in a second flow and manually map in the ID.[/font]
-
[font=Roboto, Arial, Helvetica, sans-serif]By default, only the custom fields are accessible. When using the upload from XML/JSON action, you can specify the entity itself. After doing so, an EntityID field appears like the old view. This would be your ideal workaround since it can be saved as sample data and unit tests.[/font]
Howdy, Stranger!
Categories
- 4.1K All Categories
- 61 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 260 Administration
- 212 Portal
- 489 General Q & A
- 693 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 178 Pages
- 5 Process Mining
- New Features
- 178 Datastructures
- 69 Repository
- 219 Integrations
- 28 Multi-Tenant
- 27 SDK
- 76 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 66 Lunch And Learn Questions