Auto-Populating Fields in a BP Record

Using the auto-population feature, you can automatically populate fields on a form or line item at the time the form/line item is created. Auto-population can occur on business processes that are in the same shell, or across shells. Using auto-population means that you do not have to enter data in every field in a form. For example, this feature could automatically fill in a "Plant Location" field from an attribute form.

For another example, the date field on a time sheet could be set up to default to the server date and time so that you do not need to use a date picker. Or a field could be set up to automatically display a title or other text that you would normally need to fill in on a frequent basis.

In addition, auto-population can be used with the Unifier portal. When a user logs into the portal to submit a form, such as a work order, the user's information, such as his/her location and department, can be automatically populated on the work order. Or when an employee "move" request is created, the current location of the employee can be auto-populated onto the move request form.

Fields on a form can be auto-populated from the following sources:

Fields on an attribute form for managers (except a code-based configurable manager)
Fields on another business process form or line item
Fields on a User Attribute Form (via a user data picker)
Shell Attribute Forms
Fields from an upper form (to fields on a detail form)
Fields on single-record BPs at the company, shell, or project level
Fields on an SOV (for a payment application BP)
Fields from document properties of a line item attachment
The total value from a line-item numeric field (can populate a field on an upper form; becomes a read-only field)
A constant value that was specified for a field when the form was created
Note: If you configure specific Data Elements (DEs) to auto-populate from a Base Commit BP, do not configure the same auto-population using CSV, Microsoft Excel, or REST API in an SOV sheet for General Spends, Payment Applications, or Summary Payment Applications.

Exceptions

When BP records and line items that have auto-populate DEs defined from pickers (all data pickers, BP picker) are updated through integration (REST API and Excel update), the auto-populate DEs from the picker are not updated when the input request does not include a picker value.

Notes:

Auto-population is also not triggered if the picker element is in the Main form of the record, when the input request (REST API and Excel update) includes the same value for the picker.
Although uDesigner supports the inclusion of Pull Down DEs (string or integer) on the payment detail form for use with Auto Population from an SOV Sheet, the Pull Down DE column cannot be added to the SOV Sheet from the SOV Structure. Because of this, the Pull Down DE in a line item cannot auto-populate a value from the SOV Sheet when a classic Payment BP record is created. Auto Population is only supported for decimal or current amount DEs.

Additionally, when a picker (destination picker) in a detail form is designed to be is auto-populated from another picker (source picker) from the Upper form, the system auto-populates the DEs from the former picker (destination picker) when a line item is created, only if a picker value (from the source picker) exists in the Upper form.

Exceptions

See Also