The New Engagement Request widget allows a user to request a new engagement to be added to the customer. After the user submits the request, the application can be configured to launch a program associated with the engagement request to the requester or to other stakeholders.
Links to take the user directly to each of the required fields are listed in a pink band across the top of the expanded widget. Any validation errors pertaining to the user’s input are included in the same pink band.
The following validation rules are applied when the form is submitted:
- Engagement Name is required.
The application can be configured to error or warn of a duplicate. When a duplicate engagement name is detected, the following validation message is displayed: An Engagement with this name already exists in the system. Based on your corporate settings, users will be: prohibited from submitting the when duplicate Engagements are not allowed, or allowed to submit the form after displaying a warning. If duplicate checking is not configured, the user may create duplicate Engagement records for the Engagement name that was entered.
Additionally, matching logic is applied to the following fields to determine duplicates: fuzzy match on Engagement name, and exact match on contract number when populated.
- Engagement Manager - select from the dropdown list of customer users.
- Classification is required - select from the dropdown list of options.
- Category is required - select from the dropdown list of options.
- Organization is required - select from the dropdown list of options.
- Description is required – enter a description in the free-text field provided.
To create a new engagement using the widget, complete the minimum required (*) fields and any optional fields.
Click the Submit button, or, click the Reset button to exit the form without saving changes.
Following are important additional permission and functional details pertaining to the New Engagement Request widget:
- By default, the user must have permission to create new engagements in order to use this widget. A flag can be set that allows the customer to deny “create access” for the engagement and override the permission setting to allow users to create engagements via the widget. The flag that can be set via localization under the parent tag is <TenantBehaviours> and is called <IgnoreEngagementCreateWidgetSecurity>false</ IgnoreEngagementCreateWidgetSecurity>. The default setting of “false” configures the widget to respect system permissions and only allow users with create rights to see and use this widget. Changing the setting to “true” will allow all users to see and use the widget, regardless of their create rights.
- Moving the widget causes it to reset, and will erase any changes made to the widget. Therefore, if a user is completing the New Engagement Request form and decides to move the widget elsewhere, then the form will be reset and the user’s data entry will be lost.
- Values for the Classification and Category selection dropdown lists must first be configured by an Admin user via the Admin tab > Configuration Data Management section > Setup Data Management link.
- The Engagement Manager dropdown list is populated with all existing internal customer users of the application.
- The content presented in the New Engagement Request widget can be customized via localization. Searching for the following tags in the XML file exposes the items that can be customized: <WebContextHome> or <Widgets_SupplierRequest>.