Table of Contents
Forms types
Summary
| Standard forms | activity template | @live |
|---|---|---|
| SIMPLE FORM | default | NO |
| MAGIC FORM | default | NO |
| custom forms | default | YES |
| Not Standard forms | ||
| not standard forms | not standard | YES |
Explanation
In the TECH2018/session2 you have learned how to handle the engine using SIMPLE FORMS or MAGIC FORMS. While these forms have the main advantage that they do not require any development activity to be setup, on the other side they to not allow the user to update any data in the “business data” tables. This process is particular named as @live.
When you want to create process that will cause any update to the @live environment you will need a form which contains fields related to the specific data model. This requires a development activity.
In this session you will learn how to create forms that are capable to save @live data. We will distinguish the case where:
- we use the default activity template;
- we decide to create a completely custom page template.
Examples:
- Edit account data: WManager brings onboard the EDIT_ACCOUNT_DATA process. This is one of the simplest processes to be used to show how a standard form can work.
- Inorder: is one of the most complex scenarios of not standard activity template.
