Implications
- 29 Mar 2024
- 1 Minute to read
- Print
- PDF
Implications
- Updated on 29 Mar 2024
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Other Implications? Identify how synergies flow
across features to amplify results!🔎
A table is created in the backend and a form is generated dynamically based on this created table. Forms will be created via different interface (Form Designer) where the Application Designer can drag-and-drop the form controls and other elements to create a form visually. Any user's input to the form gets updated in the created table in the backend.
The information captured in these tables can be leveraged to drive the functionality of Workflow, Table, Notification, Business Rule, SLA, and Scheduler.
The following infographic depicts the implications of Forms on other designers.
Let's explore the following use-case.
Use Case User Persona: Application Designer | Impact |
| The Application Designer Sam has created a form (VPN Access Form) which should have the details regarding VPN access with fields such as Requestor, Reason for VPN access, Duration of VPN access and so on. With this form, a corresponding table VPN Access is created. Now, the Application DesignerSam has to create a Workflow (VPN Access Workflow) to act upon the VPN access for a created record with the required conditions. | Any change in the VPN Access Form will impact the VPN Access Workflow, as both share the same table named VPN Access. |
Was this article helpful?