Dynamic Form Generator has been part of the DCM app since R6.2 and customers don’t have to configure anything to use it. This article is only relevant to customer who have started using DCM prior to 6.2 release and has some issues with the Field Plans in Data Content Planner.
DCM R5.5 included a dynamic form generator, which replaces the “Dynamic Form View” add-on. This allows users to create Field Plans based on Field Setup. The “Dynamic Form View” add-on and “Default view” use the ServiceNow form view. The field plan creation using the ServiceNow standard form view adheres to applicable ACLs. On the other hand, this dynamic form can be used to overcome ACL restrictions during a content planning phase. Nevertheless, a person committing the content set should have all applicable user roles/permissions (ACLs).
Since R6.1, the Dynamic Form Generator (DFG) is enabled by default. The DFG creates a form on the fly using the Field Setup definition. There are a few limitations when it comes to DFG:
- The Form doesn’t work in a similar fashion to ServiceNow Form Views. It means that ACLs, Client Script, and UI Policy do not apply. We believe it’s not intended to be used in a similar fashion to ServiceNow Form.
- It currently supports a subset of Field Types, read more from here Dynamic Form Generator – Supported Field Types.
- The Field Setup is intended to be used for field planning and should not have multiple conditions for the same field.
Disable Dynamic Form Generator
We don’t recommend disabling Dynamic Form Generator. However, if there is a need it can be done by creating a user preference (sys_user_preference) record with the following details:
- Search for User Preference in the application navigator
- Go to User Administration > User Preferences
- Create a new record with the following details
| Field | Value |
|---|---|
| Description | Disable DCM dynamic form generator feature |
| Name | dcm.dcp.dynamic_form |
| Type | string |
| Value | disabled |
| System | True |
| User | NULL or blank |