Description:
This widget shows a drop-down menu of options, which can be based on either a 'My Team' or a 'My Managers' list category.
Inputs
- ID/Name - Name of the widget generated by FlowWright
- Input Size - Select one of the display sizes
- Required - Select the checkbox for mandatory (tick mark)
- Select Multiple Items - Select the checkbox for multi-items (tick mark)
- Hide - Select the checkbox to hide (tick mark)
- Lock Widget - Click the button to toggle the lock/unlock feature
- Read Only - Select the checkbox to set to Read-Only (tick mark)
- Use Type Ahead - Select the checkbox for the type-ahead feature (tick mark)
- Select Type - Select between My Managers / My Team
- Display Condition - Define a display condition for other widgets based on the control field value
- Tooltip - Enter information to display on mouse hover on form render
- Styles - Enter the CSS scripts for widget styles
- Apply Classes - Select between custom classes defined
- Save - Save the input values
- Delete - Remove this form widget from the designer page
- Close - Close the input popup window
Design:
Typical Workflow Suggestions:
The following five examples are potential use cases inferred from the widget's name. They assume that the implementation supports the corresponding manager- or team-related behavior.
Employee Onboarding
Consider using the widget in an employee onboarding form to identify the new employee's manager or team. Verify that the widget exposes the required selection and value-storage functionality.
Leave Approval Requests
Evaluate the widget for a leave request form where a manager may need to be identified for approval routing. Confirm whether the selected manager can be passed to the workflow.
Team Assignment Requests
Consider using the widget in a team assignment form to help users identify a team associated with a task, project, or operational request.
Internal Service Requests
Include the widget in an internal service request form if requests need to be associated with a responsible manager or team. Configure and verify any assignment or routing behavior separately.
Project Resource Requests
Evaluate the widget for a project resource request form where a requester identifies a relevant manager or team for review and coordination.
Example:
Let’s build and execute the “SelectManagersOrTeamListDef” example.
- Create a new Form definition called “SelectManagersOrTeamListDef.”
- Drag the “BootstrapGrid, Label, SelectManagersOrTeamList, and Submit” controls onto the canvas and arrange them as shown below.
- Double-click the “SelectManagersOrTeamList” widget to configure its “Settings” properties. A pop-up window will appear to set it up. Enter a name for the control. Choose the list type (My Managers or My Team). Check the box to include the current user. Check the “Required” box to make input mandatory. Check the “Multiple items” box to allow selecting multiple items from the dropdown. Check the “Hide” box to hide this widget at runtime. Check the “Read-Only” box to view the list without making a selection. Check the “Use type ahead” box to select an item by typing its value. Click the “Lock Widget” button to toggle the lock/unlock feature and prevent accidental configuration changes. Click the “Save” button.
- Double-click the “SelectManagersOrTeamList” widget to configure its “Settings” properties. A pop-up window appears for configuration. Select the “Conditions” tab. Click the plus sign (+) to add an empty row. Set up the display conditions here. Enter the control key value and map it to the required Form field to display under this condition. Otherwise, the selected Form field remains hidden at runtime. The example below shows the “label” Form field at runtime when the user selects the “GUID value of user AlphaC” from the drop-down list. Click the plus sign (+) to add more display conditions. The Form controls appear when the appropriate checkbox values are selected at runtime.
- Double-click the “SelectManagersOrTeamList” widget to configure its “Styling” properties. Choose the input width from the drop-down list. Enter the CSS syntax. Select the classes to apply from the global drop-down list. Click the Save button.
- Double-click the “SelectManagersOrTeamList” widget to configure the “Other” properties. Enter the tooltip text. Click the Save button.
- Double-click the “SelectManagersOrTeamList” widget to set up the “Globalize” properties. The application will notify you if nothing needs to be globalized, as shown below. Otherwise, choose a language from the drop-down menu, then click the Translate button. Finally, click the Save button.
- To view the organizational structure, navigate to Administration > User Management > Organizational Structure. The example's organizational structure is displayed below.
- Save the Form definition. Select Actions > Create Form Instance. Generate a new Form instance, then check the box to edit it.
- The Form is displayed for the user, as shown below. Click the drop-down list to select an option. The Form field remains hidden because the control field (or value) is not selected in this example. Click the Submit button to finish.
- Click the drop-down list to select an option. The Form field appears as the control field (or value) is selected, as shown in the example below. Click the Submit button to complete.
Tips:
- Verify data sources: Determine where manager and team information comes from and how it refreshes.
- Test selection behavior: Check whether the widget supports selecting one or multiple managers or teams.
- Check access permissions: Verify that the displayed information is appropriate for the current user.
- Validate returned values: Confirm whether selections produce the identifiers or values needed by downstream processing.
- Test end-to-end behavior: Verify that selections are retained after submission and remain available wherever the workflow requires them.
Definition Sample:
You may download and extract the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the import process steps for any missing configurations, such as file path references and database connections. Then, save the definition to confirm the changes.