Scope: managed applications.
Develop a parameterizable list form so that when the form is created on the server, the passed parameters will define the form's properties: set of columns, filters, item ordering, and the title.
Set this form as the main list form of the object. If a user opens the form with no parameters, the form's presentation must match the main list form's presentation.
Develop common commands so that each command opens the form with a specific parameter. The title of the form must match the command name.
Place command buttons on the command interface. They can belong to different subsystems, forms, and so on.
Ensure that the application saves the settings separately for each workstation. For example, user-defined filters. See the PurposeUseKey form property.
You can find an example of a parameterizable list form in the Task.PerformerTask.ListForm form in Standard Subsystems Library.
- For each use case, create a common form.
- Create common commands, so that each command opens a specific form.
- Place the commands on the command interface.
4. Consider combining the above mentioned approaches when for one object some list some forms are parameterizable and some are not. Please notice that the best practice is to develop one parameterizable form.