The New Engagement configurable widget allows users to easily request new engagements. After they submit the request, the system can be configured to launch a program related to the engagement request to the requester, or to other stakeholders.
Links to navigate the user directly to each of the required fields are listed in a pink band across the top of the form. Any user input validation errors are indicated within the same pink band.
To create a new engagement using this widget, complete, at very least, the minimum required fields and the preferred optional fields within the widget form.
Click the Create button to submit your request. Or, click the Clear button to exit the form without saving changes.
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 the system permissions and only allow users with create rights to see and use the 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 the widget to reset, and will erase any changes that are made to the widget. Therefore, if a user is completing the New Engagement form and decides to move the widget elsewhere, then the form will be reset and the user’s data entry will be lost.
- A single custom New Engagement request widget can be configured per customer.
- Do not add the engagement number to the New Engagement widget.
- The application can be configured to error or warn on 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 the user’s corporate settings, they will be prohibited from submitting the New Engagement form when duplicate engagements are prohibited, or permitted to submit the form after the warning displays. If duplicate checking is not configured, then the user can create duplicate engagement records for the Engagement name 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.