Skip to main content
Skip table of contents

2022.1 Release Notes

These items were released to production on Wednesday, March 4th.

We will no longer support Microsoft Internet Explorer after this release.

IE hasn’t been updated with new features since July 2015, and Microsoft is ending all IE support in 2022.

Please upgrade to a modern browser such as Chrome, Firefox, Safari, or Edge as soon as possible.

Performance

FEATURE 456666 For large organizations, system performance will be improved in the worklist and contract library.

Executive Summary Controls

When a user initiates the Signature Phase, the application automatically generates an executive summary cover page, which contains a summary of reviews and approvals, with date/timestamps, that were obtained throughout the workflow. With executive summary controls, Admins will be able to customize Executive Summaries to better meet the needs of their unique organizations.

FEATURE 288002 Admins will have greater control over where the executive summary is saved, how it appears among other workflow documents, and the content contained in the executive summary.

USER STORY 454721 The timezones on an executive summary will be the timezone of the user who created the executive summary.

USER STORY 318360 Data changes made immediately prior to clicking Start Phase for the Signature Phase will automatically update the related content on the executive summary.

USER STORY 287499 When a user retracts a Signature Phase, the executive summary will be removed, and a new executive summary will be created when the user returns to the Signature Phase.

USER STORY 450391 Phase retractions prior to the creation of the executive summary will be captured on the executive summary.

  • The Phase Manager for the phase will be listed as expected.

  • Below the phase information will be a textbox indicating that the phase was retracted and providing the retraction reason.

  • Any action during the phase that took place before retraction will be recorded.

USER STORY 450932 Declines and skipped participants will be captured on the executive summary.

  • When a participant is skipped during a phase captured by the executive summary, the following information will appear:

    • The name of the participant who was skipped will be listed in the Participants row.

    • The skipped user’s role will be listed in the Role & Group row.

    • The text Participant Skipped and a timestamp of when the skip occurred will appear in the Start/End row. The timestamp will be provided in the duration column, if available.

  • When a participant declines their turn during a phase captured by the executive summary, the following information will appear:

    • The name of the participant who declined their turn will be listed in the Participants row.

    • The user’s role will be listed in the Role & Group row.

    • The text Participant Declined and a timestamp of when the declination occurred will appear in the Start/End row. The timestamp will be provided in the duration column, if available.

USER STORY 287685 Executive summaries will have a Contract Summary section at the top of the report.

USER STORY 319330 Workflow header information will be pulled into the executive summary.

  • The Contract Summary section will include:

    • Workflow Name

    • Requestor (if applicable)

    • Initiator

    • Organization

    • Contract Locations

    • Contract Description (if applicable)

    • Contract Type

    • Action

  • If the information is not applicable, the field will be hidden on the summary.

  • For large organizations, Contract Locations can be removed or placed in an appendix.

USER STORY 285722 Following the Contract Summary, each workflow phase will have a section with a prominent header, and the sections will be listed in chronological order from top-to-bottom.

For completed phases:

  • Each section header will include the Phase Name, Phase Manager, date and time the phase was started, and date and time the phase was completed. The Duration field will show the total time from Phase Start to Phase End.

  • The body of each section will contain a table that will show the following:

    • Participants, including Name and Title.

    • Role & Group.

    • Start/End date, time, and timezone.

    • Duration in days, hours, and minutes.

For open review phases:

  • The Duration column will be omitted.

For incomplete phases:

  • Each section header will include the Phase Name, Phase Manager, and date and time the phase was started.

  • The body of each section will contain a table that will show the following:

    • Participants, including Name and Title.

    • Role & Group.

    • Start date, time, and timezone.

  • Start and end dates and time will be presented as they were recorded in the system.

  • Durations will be simple calculations, subtracting the start date/time from the end date/time. No adjustments for non-working hours or weekends will be made.

  • The timezones in an executive summary will be the timezone of the user who creates the executive summary.

  • All participants in each phase will be included, regardless of if they were assigned (i.e., Admin or Phase Manager) or if they were triggered into the workflow.

USER STORY 318808 The header and footer will be updated.

  • The header will contain the title “Executive Summary Cover Page.”

  • The footer will contain a system-generated date formatted as MM/DD/YYYY, timestamp with timezone indicated, Customer Name, Workflow Name, and the page number.

  • A disclaimer will appear below the footer: This Executive Summary was automatically generated at the time the Signature Phase was started. Durations throughout this document are calculated based on the total elapsed time between the start and the conclusion of a participant’s turn within a phase, including non-working hours, weekends, and holidays. It is not meant to indicate time spent working on the contract.

USER STORY 318356 Executive Summary will be added as a form type on form templates.

  • The Executive Summary form type will allow Admins to select which system and custom fields will appear on the executive summary and to control the order and orientation in which they appear.

  • Admins will be able to:

    • Open the existing form builder function.

    • Select Executive Summary as the form type.

    • Provide a name for the form.

    • Save the form template and edit the form template, as they can with any other form template.

USER STORY 318357 Properties and triggers for Executive Summary form types will be removed, i.e., hidden.

  • No properties will be accessible.

  • No triggers can be set for the form.

  • Users will be able to drag and drop any available field type to the form template.

  • All types of data fields can be used except:

    • Triggers

    • Properties

    • Attachments

USER STORY 318813 Custom fields on the assigned Executive Summary form will appear on the executive summary.

  • The column setup will be honored on the executive summary.

    • If the form has a one-column layout, one column will appear on the executive summary.

    • If the form has a two-column layout, two columns will appear on the executive summary.

  • The Section Name will appear on the executive summary, if applicable.

  • If the form has more than one section, the sections will be spaced apart on the executive summary and have the Section Name, as they are on the form view.

USER STORY 454700 The Executive Summary setup on workflow templates will be rearranged to improve readability and flow.

USER STORY 318358 An Executive Summary section will be added to the Edit Signature Phase modal of the workflow template.

  • Admins will be able to select one form template of any type (excluding Pulse Check, Conflict Capture, or Timesheet) to define which fields will be on the executive summary.

  • When a user selects the form template, the system will default to listing only form templates of type = Executive Summary.

  • When the Display all form types checkbox above the selection box is checked, all active forms will be available for selection. When the checkbox is unchecked, the system will revert to the default of listing only form templates of type = Executive Summary.

  • Triggers, or any other options set in a form template, will not impact the behavior of the form when the form is used to control the executive summary.

USER STORY 321031 In the Executive Summary section on the workflow template, users will be able to choose how they want the executive summary saved, if they want it saved at all.

  • The Save Executive Summaries as field will have three radio buttons: Document | Attachment | Do not save

    • If the user selects Document, the executive summary will be visible to internal and external parties. This is the default selection.

    • If the user selects Attachment, the executive summary will be visible only to internal parties.

    • If the user selects Do not save, the form selection dropdown will be disabled.

  • If a user selects a non-type executive summary form, Property settings that may impact DocuSign or other aspects of display will be ignored.

USER STORY 318359 Prior to the creation of the executive summary (i.e, at the completion of the phase immediately preceding the Signature Phase), the system will automatically reference all executive summary settings in the workflow template.

  • If the workflow template specifies that the executive summary is not to be saved, the system will take no further action.

  • If the workflow template specifies that the executive summary is to be saved, the system will generate the executive summary and save it as specified in the workflow template.

  • The executive summary will contain all standard formatting and content.

  • The executive summary will include all system and/or custom fields specified by the Admin in the Form Template associated with this workflow’s template.

Document Viewer

FEATURE 287991 Workflow participants will be able to expand the document in the document viewer.

  • The document viewer will remain on the same page.

  • Approved Language and Form Data will continue to be accessible.

USER STORY 285754 Workflow participants will be able to expand the document in the document viewer by either resizing the document viewer or resizing the right panel.

  • Workflow participants will be able to expand and collapse the document with the controls located in the document header.

    • The workflow participant must be the current sequenced participant, and the expand feature will only be available when the document is in edit mode.

  • Workflow participants will be able to expand and collapse the right panel with the controls located on the top left of the panel.

    • Resize and collapse functionality of the right panel will apply to the Contract Library and all phases of the workflow.

Contract Library

FEATURE 293899 Keyword search functionality will leverage the same technology that supports global search, allowing keyword search to function with the new Permission Matching Logic.

  • The existing keyword search UI will not change.

  • Rather than configuring each column’s filter, users will be able to perform a text-string search across all columns in the Contract Library grid.

  • Users will be able to:

    • Enter a text-string and filter the data by matching either All Displayed Columns or All Columns, which will include columns that are not currently displayed.

    • Specify if the search should apply to either only fields that are currently displayed or All Fields.

    • Clear the search, allowing the system to return full results.

    • Choose if inactive contracts should be included in the search results. By default, inactive contracts will be excluded.

    • Apply column filters subsequent to keyword search. The system will narrow the result set based on the parameters of the keyword search, plus each successive filter that the user sets. In other words, the keyword search and filter parameters will be treated as an AND logic, with the results matching both.

USER STORY 319563 Keyword search functionality in the Contract Library will follow most standard query syntax rules.

  • Search entries will not be case sensitive, unless the entry is in quotes. For example, a search for “AAA” will only return exact matches for AAA.

  • /.*n/ will return not results.

  • For many search engines, a hyphen preceding a word (such as Admin -agreement) excludes the word following the hyphen. However, this search functionality will not adhere to this practice.

  • The * operator (such as ad*) will return results containing words that start with “ad.”

  • The search engine will not autocorrect or search for what it thinks you meant to type. For example, if you enter “physican” instead of “physician,” you won’t see the results unless there is a matching typo in the database.

  • The following characters can be added without affecting the results:
    + - = & || > < ! ( ) { } [ ] ^ “ ~ * ? : \ /

This feature only applies to customers whose tenants have the keyword search bar above the Contracts table toggled on. Most tenants do not use this feature because before this release, it was incompatible with the technology powering global search.

Classifications Management

FEATURE 302830 All active contract categories will be listed in the contract category dropdowns; Super Admins will be able to assign contract types to a contract category and edit contract categories.

USER STORY 300524 All active contract categories will be listed in the Contract Category dropdown on the initiation screen, Add New Document Template modal, and the New Workflow Template modal.

  • Initiators, Phase Owners, and Admins will be able to view and select any active contract category on the initiation screen.

  • Admins will be able to view and select any active contract category on the Add New Document Template modal and the New Workflow Template modal.

  • An active contract category must have at least one contract type under it to be visible as a selection in the Contract Category dropdown.

USER STORY 300525 In the New Contract Category modal, Super Admins will be able to assign contract types to a contract category when creating a new contract category, which will allow the classifications to be complete when the category becomes active.

  • Only active contract types can be grouped under the new contract category.

  • Multiple contract types can be grouped under the same contract category.

  • To add a contract category:

    • Navigate to Admin > Application Settings > Classifications Management > Contract Categories.

    • Click New.

    • In the New Contract Category modal, enter a name for the contract category.

    • Optional: Enter a description.

    • Select one or more contract types from the Contract Type dropdown.

    • To make the contract category active, toggle ON the Inactive/Active toggle.

    • When finished, click Save
      OR
      To close the modal without creating the new contract category, click Cancel or X.

USER STORY 300526 Super Admins will be able to edit contract categories, including the contract type groupings.

  • Only active contract types can be grouped under the new contract category.

  • Multiple contract types can be grouped under the same contract category.

  • To edit a contract category:

    • Navigate to Admin > Application Settings > Classifications Management > Contract Categories.

    • Click the contract category that you’d like to edit.

    • In the modal, edit as needed.

    • When finished, click Save
      OR
      To close the modal without saving your changes, click Cancel or X.

DocuSign

FEATURE 285707 For Signatories, an embedded link to the Signature Phase of the workflow will be included in the body of email notifications that DocuSign sends for an envelope.

  • For some emails, the link will be clickable.

  • Non-clickable links can be copied and pasted into a browser window.

  • The link will not be included in the email notification for Other Party Signatories.

FEATURE 285640 The banner in the DocuSign Signature Phase will be updated to include more information and a link to the DocuSign login page, which will allow signers to quickly access envelopes in need of a signature.

FEATURE 288142 PDF form fields will be preserved when symplr Contract transfers the document to DocuSign, preventing an Admin or the Phase Owner from having to recreate the tabs in DocuSign.

When a fillable PDF used as a document is submitted to DocuSign from symplr Contract, DocuSign will identify the form fields and automatically convert them to fillable tabs, retaining properties such as Required.

FEATURE 285800 When a Sender’s DocuSign account has administrative defaults set up, envelopes from symplr Contract will defer to those settings.

This applies to the following settings:

  • Initial email reminders and their frequency

  • Envelope expiration and the number of days before expiration to send a warning email

FEATURE 285853 Senders (Admins or the Phase Owner of a Signature Phase) will be able to add, remove, or resequence Signatories on in-flight DocuSign envelopes.

USER STORY 317288

Admins and Phase Owners will be able to:

  • Remove DocuSign Signatories who have not yet signed.

  • Add additional Signatories to an in-flight DocuSign envelope.

  • USER STORY 340590 Resequence future Signatories. DocuSign tabs will be preserved, and resequenced Signatories will not be transformed into a free-form signer.

Phase Mediators will be able to:

  • Remove DocuSign Signatories who have not yet signed and were added by that Phase Mediator (i.e., Phase Mediators cannot remove Signatories added by a trigger or by the workflow template).

  • Add additional Signatories to a in-flight DocuSign envelope.

Users will perform these actions in symplr Contract, and changes will be propagated to the DocuSign envelope.

Signatories added to an in-flight envelope will become free-form Signatories, allowing them to add their signature anywhere on the document.

FEATURE 328425 Handling of non-Signatory sequenced participants in a DocuSign Signature Phase will be improved.

USER STORY 304179 Non-Signatory sequenced participants (such as Reviewers, Approvers, Phase Owners, Phase Mediators, and Admins) will be added to the DocuSign envelope as Needs to View recipients, and they will need to view the document to complete their turn.

  • DocuSign does not enable a Decline feature for Needs to View recipients.

In the unlikely event that a decline action is necessary, consider converting the Needs to View user to a Needs to Sign role. The Needs to Sign user will be able use the Approve/Decline tabs that DocuSign provides, and the envelope will sync with symplr Contract.

  • Signatories will remain as Needs to Sign recipients.

  • The label on the panel will be updated from Signatory Sequence to Participant Sequence.

  • Sequencing in DocuSign will match sequencing in symplr Contract.

  • The Complete Review button in symplr Contract will be removed, and users will be required to complete the review in DocuSign.

  • Internal Reviewers and Approvers will receive the email containing the link to the workflow phase.

  • Syncing behavior will match the existing Signatory behavior.

    • A green checkbox will appear after a Reviewer has reviewed the document.

    • All participants, including non-Signatories, must finish before phase completion.

To prevent an error when starting a DocuSign Signature Phase, a user must check Enable needs to view role under Sending Settings > Recipient Roles in the account settings for DocuSign.

FEATURE 285912 When creating a DocuSign envelope, Admins or the Phase Manager will be able to select (or deselect) which documents are included in the envelope.

Previously, all documents were included in the envelope by default, and users managed documents in DocuSign.

USER STORY 323147 When an Admin or the Phase Manager starts the phase, the Confirm DocuSign Settings modal appears. Under the Documents to Include tab, the user can select (or deselect) documents.

  • By default, all documents will be selected.

  • The user will be able to deselect any documents.

  • The user will be able to reselect a document if deselected in error.

  • If the phase is retracted, the modal will appear when the Admin or the Phase Manager starts the phase, and all settings are set to the defaults.

FEATURE 287671 Admins, Phase Owners, or Phase Mediators of a DocuSign Signature Phase will be able to optionally CC the Phase Manager on the DocuSign envelope.

USER STORY 325089 This feature is controlled by a toggle, which will default to OFF at the time of this release.

  • Under the Application Settings tab in Admin > Application Settings, Admins will see an Off/On switch with the text Include Phase Owner/Mediator by default as a cc recipient on DocuSign envelopes.

  • An Admin can toggle the feature on or off, then save the selection.

  • The selection determines the default state in the Confirm DocuSign Settings modal. The modal has a checkbox where the user can decide whether or not to include the Phase Owner/Mediator as a CC recipient on the DocuSign envelope.

    • If the toggle is OFF, the checkbox will not be selected by default.

    • If the toggle is ON, the checkbox will be selected by default.

FEATURE 286015 When creating a DocuSign envelope, Admins or the Phase Manager will be able to include attachments in the envelope, and attachments will have versioning functionality similar to document versioning functionality.

  • Selected attachments will load into the DocuSign UI, following the expected behavior for documents.

  • When the envelope is completed, the attachments will return as new versions of attachments, not as documents.

USER STORY 309183

  • A user who has permissions to upload an attachment can upload a new version of an existing attachment.

  • Any user who can see and download attachments will be able to view the Version history, including the existing abilities with documents. Users can view and download versions from Manage All > View > View History.

  • This feature applies to Vendors, Providers, Workflows (with the exception of the Initiation page), and Contracts.

  • The controls to upload a new version will exist in the Attachments panel in the accordion. The user can access the control from the ellipsis next to the attachment or by clicking Manage All.

FEATURE 285910 Users who have permissions to upload a new document version will be able to restore a previous version of the document.

USER STORY 321477 Users will be able to restore a previous version of the document in the Document Source Phase, the Negotiation Phase (including sequenced and open), and the DocuSign Signature Phase.

  • Document Source and Sequenced Negotiation:

    • Reviewers and Approvers can upload when they are the active sequenced participant.

    • Phase Owners, Phase Mediators, and Admins can upload at any time.

  • Open Negotiation:

    • Reviewers and Approvers can upload when they are an active participant.

    • Phase Owners, Phase Mediators, and Admins can upload at any time.

  • DocuSign Signature Phase:

    • Reviewers, Approvers, and Signatories can upload when they are the active sequenced participant, including when the participation is in DocuSign.

UI Changes

  • To distinguish between the View History and Restore Previous Version operations, the icon on View History will be changed to three stacked lines.

  • For users who can access the upload control, in the document viewer will be an icon, which will have a tooltip that reads Restore this version and make it the current version.

FEATURE 304171 A Decline to Sign event will be captured in the workflow.

USER STORY 332656 A Decline to Sign event notification will appear in the workflow banner.

  • The workflow banner text will be updated from Waiting on signature from DocuSign to There has been a decline in DocuSign and the envelope is voided. You must retract or cancel the phase.

  • If a user retracts the phase, the banner will clear.

USER STORY 301810 The Decline to Sign reason will appear in the workflow history and in the tooltip over the Declined status indicator in the Participant Sequence panel.

  • The workflow history entry for declining to sign will be similar to the entry for declining to approve or review.

USER STORY 304160 When a DocuSign Signatory declines to sign, the Phase Manager will be inserted into the sequence as the active participant.

When a DocuSign Signatory declines to sign:

  • The Phase Owner or Mediator will be inserted into the sequence as the active participant.

  • The Phase Owner or Mediator must cancel or retract the phase.

  • Email and in-app (bell) notifications will be sent to applicable recipients.

  • The Complete Phase option will be removed.

Time Tracking (TERMS 2.0)

FEATURE 327066 Users will be able to add or update email contacts for inquires regarding locked timesheets.

USER STORY 328320

  • Admins will be able to add or update the default email address on the Timesheet Management page.

  • Admins will be able to add multiple email addresses.

USER STORY 328330 If no global email address has been added, the timesheet initiator’s email will be the default contact.

USER STORY 328327 When a Timesheet Reporter or Timesheet Assistant clicks Contact Administrator, the email addresses will automatically populate the Send to field in the Inquiry About Locked Timesheets email.

FEATURE 338760 The Reject button will be hidden on the Time Entry Phase, as timesheets should not be rejected before they are submitted, and Timesheet Reporters should not have the option to reject their own timesheet.

USER STORY 318324

  • For Timesheet Reporters and Timesheet Assistants, the ellipsis menu will be hidden.

  • For Approvers, the ellipsis menu will be displayed with the option to cancel or reject the timesheet during the Approval Phase.

  • For Financial Reviewers, the ellipsis menu will be displayed with the option to cancel or reject the timesheet during the Financial Review Phase.

  • For Admins:

    • The ellipsis menu will be displayed with the option to cancel the timesheet on all phases.

    • The ellipsis menu will be displayed with the option to reject the timesheet on the Approval Phase and the Financial Review Phase.

Conflict Capture

Our Conflict Capture integrates with symplr Contract to automate the distribution, submission and management of conflict of interest statements. 

To access Conflict Capture, your organization must subscribe to it, and your user profile must have the appropriate user role and permissions. If you have any questions, contact your Admin.

FEATURE 334250 Conflict Capture: Campaign Completion

When the campaign end date is met, a final record of the campaign will be created.

USER STORY 334284 Campaign Completion: Notify users that the campaign is complete and there are workflows requiring resolutions.

When the campaign end date is met and there are workflows that require a resolution form, the following users will receive an automated email notification:

  • Moderator
    If the Moderator is only assigned to a Respondent, they’ll only receive the email if the assigned Respondent requires a resolution form. 

  • Campaign Coordinator

  • Resolution Manager

USER STORY 334278 Campaign Completion: Record the Moderators and Resolution Managers on the campaign.

When a campaign end date is met:

  • The campaign is complete. No further action can be taken on the campaign or associated workflows, nor can any participants be added or removed from the campaign.

  • The Resolution Managers and Moderators for the campaign are recorded.

    • Note that Resolution Managers and Moderators are only shown at the campaign’s end.

When the campaign end date is met or the campaign is cancelled:

  • The campaign is complete. No further action can be taken on the campaign.

  • Participants cannot be added or removed from the campaign on the campaign detail page. 

    • Note that adding or removing roles or Conflict Capture Categories on the user record does not impact the campaigns. 

  • The Resolution Managers and Moderators for the campaign are recorded.

  • The Campaign Coordinator or Admin can view the list of participants on the campaign detail page. 

If an Admin removes the Conflict Capture Category from a user record, then that category will be removed from display on the campaign participant list. The user will remain on the participant list in the campaign, and the Category column will reflect the categories currently assigned to that user. 

USER STORY 334282 Campaign Completion: Resolution Managers and Moderators can view completed and cancelled workflows.

Resolution Managers and Moderators can view any completed or cancelled workflow matching their Conflict Capture Category and role, regardless of whether they are participants on that workflow. This will allow them to compare the responses on a current statement to responses on previously completed statements.

If the role or category is removed, then the user can still view any workflow in which they were a participant: 

  • A Respondent can view assigned workflows.

  • A Moderator can view all workflows if assigned to that campaign when the end date was met. 

  • A Moderator assigned to a single Respondent can view all workflows for that Respondent if assigned when the campaign end date was met. 

  • A Resolution Manager can only view the workflows if assigned when the campaign end date was met. If the Resolution Manager was removed while the campaign was active, they will be unable to see the workflows for that campaign.

USER STORY 387878 Campaign Completion: Resolution Managers and Moderators can view completed and cancelled workflows in the worklist.

Resolution forms can be added to completed campaigns.

FEATURE 287964 Conflict Capture: Campaign Management

USER STORY 286172, 287814 Campaign Management: Within a multi-organization tenant, a customer can select one or more organizations where they will manage Conflict Capture campaigns.

  • The Conflict Capture menu and screens will only appear within the selected organization.

  • All users added to campaigns as participants will be set up in the designated organization.

USER STORY 285684 Campaign Management: Admins and Campaign Coordinators will see Conflict Capture in the Explore dropdown.

Selecting Conflict Capture will open the Conflict Capture page.

USER STORY 285636 Campaign Management: On the Conflict Capture page, Admins and Campaign Coordinators can see three tabs:

  • Campaigns

  • Workflows

  • Manage Categories

USER STORY 285645 Campaign Management: Campaigns table

Under the Campaigns tab, the table lists all campaigns.

  • The following columns appear by default:

    • Conflict Capture Category

    • Campaign Name

    • Duration

    • Send on Date

    • Calendar Year

    • Status

  • The following columns can be added via Manage Columns:

    • Conflict Capture Statement form

    • Conflict Capture General Information form

    • Conflict Capture Resolution form

    • Campaign Coordinator

USER STORY 285663 Campaign Management: The following widgets are available for the Campaigns table:

  • Filter Table widget

  • Manage Columns widget

  • Export widget

USER STORY 285642 Campaign Management: View campaign setup from table.

Selecting a campaign in the table will open the Manage Campaign page. An Admin or Campaign Coordinator can can review the campaign details and edit as needed.

USER STORY 285647 Campaign Management: Workflows tab and table

Under the Workflows tab, the table lists all workflows.

The following columns appear:

  • Workflow Name  

  • Conflict Capture Category

  • Campaign Name

  • Send on Date

  • End Date

  • Respondent

  • Job Title

  • Status (Completed, In process, Cancelled) 

  • Resolution Managers

  • Cancellation Reason

  • Potential Conflict

  • Resolution Added By 

USER STORY 285662 Campaign Management: The following widgets are available for the Workflows table:

  • Filter Table widget

  • Manage Columns widget

  • Export widget

  • Additional Columns widget

USER STORY 285659 Campaign Management: View workflows from table.

Selecting a workflow in the table will open the workflow page. An Admin or Campaign Coordinator can assess the status of the workflow and follow up if needed.

Completed workflows are read-only. 

FEATURE 287966 Conflict Capture: Cancel a campaign or workflow

USER STORY 285862 Cancel the campaign and all workflows for that campaign.

The Admin or Campaign Coordinator can cancel an active campaign (i.e., start date has been met).

  • The Cancel action appears on each active campaign in the Campaigns table.

  • The user must enter a reason for cancelling the campaign. This will be included in the campaign cancellation notification. 

  • Completed campaigns cannot be cancelled.

  • The Campaign Coordinator or Admin must enter a reason for the cancellation and this field must be completed before the campaign can be  cancelled. 

  • The campaign will appear in the Campaigns table with a status of cancelled.

  • All active workflows within the campaign will be cancelled. 

USER STORY 285845 All campaign participants are automatically notified of the cancellation via email and in-app (bell) notification.

USER STORY 285848 Cancel an individual workflow.

The Admin or Campaign Coordinator can cancel an individual workflow within an active campaign.

  • The Cancel action is on the ellipsis menu. It only visible to Campaign Coordinators and Admins.

  • The user must enter a reason for cancelling the workflow. This will be included in the workflow cancellation notification. 

  • Complete workflows cannot be cancelled.

  • The cancelled workflow will move to the completed list in the Conflict Capture My Worklist, with a status of cancelled.

USER STORY 317343 All workflow participants are automatically notified of the cancellation via email and in-app (bell) notification.

FEATURE 285700 Conflict Capture: Campaign Creation

USER STORY 341118 Campaign Creation: The Super Admin can manage campaigns, view campaigns, view workflows and manage workflows.

The Super Admin role is unavailable in the UI. If you would like one or more Admins in your organization to have this role, contact a symplr Contract representative. Note that the Super Admin must be assigned an Admin role within the UI.

A user with the Super Admin role can do anything an Admin can do: 

  • Navigate to the Conflict Capture management pages.

  • View Campaigns

  • Add, edit and cancel campaigns

  • View conflict capture workflows

  • Add and update resolution forms

  • Cancel conflict capture workflows 

  • Access the Application Settings menu in the Conflict Capture organization. 

USER STORY 285840 Campaign Creation: Add Participants to a campaign.

An Admin or Campaign Coordinator can add participants (Respondents, Moderators and Resolution Managers) to a scheduled campaign.

  • The list of available users shows all active users assigned to the current organization.

  • If a user with a conflict capture role is assigned a Conflict Capture Category, then the user is automatically added to the scheduled campaign with the same Conflict Capture Category.

  • When a user is added to a campaign as a Respondent, Moderator, or Resolution Manager, the role and Conflict Capture Category are added to the user record.

  • The Conflict Capture Category assigned to a user always syncs with scheduled campaigns.

  • Adding a participant to a campaign automatically adds the role and Conflict Capture Category to the user record.

  • Removing a participant from a campaign automatically removes the Conflict Capture Category from the user record.

USER STORY 285921 Campaign Creation: On the Manage Campaign page, when removing a participant from a campaign that has not yet started, alert the Campaign Coordinator or Admin when that the Conflict Capture Category will be removed from the user record.

  • If a user with a conflict capture role is assigned a Conflict Capture Category, then the user is automatically added to the scheduled campaign with the same Conflict Capture Category.

  • The Conflict Capture Category assigned to a user always syncs with scheduled campaigns.

  • Adding a participant to a campaign automatically adds the Conflict Capture Category to the user record.

  • Removing a participant from a campaign automatically removes the Conflict Capture Category from the user record.

USER STORY 288113 Campaign Creation: The campaign is associated with the conflict capture organization.

Each campaign is associated with the organization in which it was created, so that all of the conflict capture statements can be managed in that organization.

USER STORY 285870 Campaign Creation: User can test the campaign.

The Campaign Coordinator can send a test version of the campaign to a few users so that they can review the statements and verify everything is correct before sending statements to all the Respondents

  • The test workflow is only sent to the selected user(s).

  • Test mode is available until Send on Date is met.

USER STORY 295304 Campaign Creation: The minimum value a user can enter in the Duration field is 7 days.

USER STORY 285911 Campaign Creation: User can preview a form template.

The Campaign Coordinator can preview the form templates when selecting a form template to ensure they are selecting the correct form template for the campaign.

USER STORY 295302 Campaign Creation: Alert the Campaign Coordinator/Admin if there are no Conflict Capture Categories.

The Admin or Campaign Coordinator will be alerted if there are no conflict capture categories so that they will know why the Conflict Capture Category dropdown is empty.

  • The Conflict Capture Category dropdown is disabled if there are no Conflict Capture Category records in Active status.

  • The user sees the following message:
    No Conflict Capture Categories were found, please add the conflict capture categories. Conflict capture categories can be added here.

    • The user can click the a link to view the conflict capture setup tab.

    • The list of Conflict Capture Categories refreshes when the user navigates back to the campaign setup screen.

USER STORY 303268 Campaign Creation: Campaign Status

A Campaign Coordinator or Admin can see the status of campaigns.

The campaign statuses are: 

  •  Pending: A campaign has been created but not yet scheduled.

  •  Scheduled:  A campaign has been scheduled (StartDate and Duration entered) but the Start Date has not been met. 

  •  Active: The Start Date has been met.

  •  Complete: The End Date has been met.

  •  Cancelled: The campaign was cancelled.  

USER STORY 295395 Campaign Creation: Display the appropriate action buttons based on the status of the campaign.

The available actions are based on the status of the campaign.

  • If the campaign is created but not yet active, then the following buttons appear:

    • Test | Schedule | Delete

    • The user can click on the row to edit the campaign setup.

  • If the campaign is active (start date met), then the following buttons appear:

    • View Schedule | Cancel

    • The user can click on the row to view the campaign setup.

  • If the campaign is cancelled or completed (End Date met), then the following button appears:

    • View Schedule

    • The user can click on the row to view the campaign setup.

The View Schedule button is shown on completed campaigns so the user can view the Start Date and Duration. All fields are read-only.

USER STORY 285905 Campaign Creation: Filter the forms and users based on the selected Conflict Capture Category.

The Campaign Coordinator can select a Conflict Capture Category when creating a campaign to auto-populate the fields with the correct participants and form templates. This reduces the likelihood of selecting the wrong participants or failing to select participants.

When a Conflict Capture Category is selected in the Create Campaign modal:

  • The form templates available for selection that match the selected Conflict Capture Category.

    • If there is more that one form with the selected Conflict Capture Category, then the user can choose one.

  • The participants (Respondents, Moderators, and Resolution Managers) that match the selected Conflict Capture Category will be added to the campaign.

USER STORY 285773, 337754 Campaign Creation: Help text for each field

When creating a campaign, the Admin or Campaign Coordinator can hover over the (info) next to a field to see information about the field.

  • Conflict Capture Category: Populates users and form templates with the same Conflict Capture Category.

  • Campaign Name: The reference name for the campaign.

  • Conflict Capture Statement form template: The conflict capture statement completed by the Respondent.

  • Conflict Capture Resolution form templates: The resolution form completed by the Resolution Manager if a response on the statement triggers a potential conflict.  

  • Conflict Capture General Information form template: This is an optional form that can be added to the workflow to display reference information.

USER STORY 285904 Campaign Creation: New page to create a conflict capture campaign

An Admin or Campaign Coordinator can generate multiple instances of the COI Statement so they can easily manage which users are required to complete the statements and ensure each Respondent receives the correct statement to complete.   

The following information is added to create a campaign and built in sections:

General Info

  • Conflict Capture Category

    • The initiator can only assign the Conflict Capture Category to one scheduled campaign.

    • The list of Conflict Capture Categories is filtered to exclude those already assigned to scheduled campaigns.

  • Campaign Name

    • This must be unique.

  • Conflict Capture Statement form template (preview option)

    • Filtered by active status and Conflict Capture Category if one has been selected.

  • Conflict Capture General Information form template (preview option)

    • Optional

    • Filtered by active status and Conflict Capture Category if one has been selected.

  • Conflict Capture Resolution form template (Preview Option)

    • Filtered by active status and Conflict Capture Category if one has been selected.

  • Add and manage workflow participants.

    • Respondents

    • Moderators

      • Add Moderators to Respondents

    • Resolution Managers

  • Save

USER STORY 285965 Campaign Creation: Prohibit the Campaign Coordinator/Admin from setting up duplicate campaigns.

  • The Conflict Capture Category dropdown is disabled if a campaign is scheduled for all Conflict Capture Categories.

  • The following message will appear: All Conflict Capture Categories have scheduled campaigns.

USER STORY 285963 Campaign Creation: Testing a campaign

Open the test campaign setup and enter the info to send a test workflow:

  • Click Test to open the test campaign setup.

  • Select the participants.

  • Click Begin Test.

    • To cancel the test, click Cancel.

USER STORY 285962 Campaign Creation: Scheduling a campaign

Open the schedule campaign setup and enter the info to schedule the workflow:

  • Click Schedule to open the schedule campaign setup.

  • Enter the Duration (number of days the campaign lasts).

    • This must be an integer between 7 and 365.

  • Select the Send on Date.

    • Must be after the current date.

  • Click Save.

    • To cancel the campaign, click Cancel.

USER STORY 337730 Campaign Creation: No Conflict Capture Categories alert

If a user attempts to set up a campaign but there are no Conflict Capture Categories, then the following alert will appear:
No conflict capture categories were found. Please add at least one Conflict Capture Category here.

  • Click the here link to view the Conflict Capture Setup tab.

  • The list of Conflict Capture Categories refreshes when the user navigates back to the campaign setup screen.

USER STORY 337732 Campaign Creation: Alert the user when all Conflict Capture Categories have active campaigns.

If a user attempts to set up a campaign but all Conflict Capture Categories have active or scheduled campaigns, then the following alert will appear:
All conflict capture categories have scheduled campaigns.

USER STORY 285920 Campaign Creation: Select the Conflict Capture General Information form template.

The Conflict Capture General Information form template is an optional form template that can be included in the campaign to share general information that can be referenced by the participants.

  • The list of form templates available for selection is filtered by:

    • Active status

    • Form Type of Conflict Capture General Information

    • Conflict Capture Category (if one has been selected)

  • The form is displayed in edit mode on the campaign setup screen.  

  • The fields on the form can be completed by the Campaign Coordinator or Admin during campaign setup.

  • In the conflict capture workflow, the form fields are read-only.

USER STORY 285872 Campaign Creation: Select the Conflict Capture Resolution form template.

The Conflict Capture Resolution form template is a required form template that is included in the campaign to ensure that Resolution Managers have the correct statements to manage any conflicts.

  • The list of form templates available for selection is filtered by:

    • Active status

    • Form Type of Conflict Capture Resolution

    • Conflict Capture Category (if one has been selected)

USER STORY 285914 Campaign Creation: Select the Conflict Capture Statement form template.

The Conflict Capture Statement form template is a required form template that is included in the campaign to ensure that each Respondent has the correct statement to complete.

  • The list of form templates available for selection is filtered by:

    • Active status

    • Form Type of Conflict Capture Resolution

    • Conflict Capture Category (if one has been selected)

  • The Campaign Coordinator selects one form.

USER STORY 285887 Campaign Creation: Select the Duration for the campaign.

The Campaign Coordinator or Admin must set the duration of the campaign.

  • The duration is entered as the number of days, which must be between 7 and 365.

  • Upon the end of the selected duration, the statements are read-only, and Respondents can no longer update their Conflict Capture Statement forms.

USER STORY 285888 Campaign Creation: Select the Send on Date.

The Campaign Coordinator or Admin must select the date that campaign workflows are created and the campaign starts.

  • The date must be on or after the current date.

  • Workflows are generated when the Send on Date is met.

USER STORY 285831 Campaign Creation: Add the Moderators.

The Campaign Coordinator or Admin can assign Moderators to the campaign or to individual Respondents so that a Moderator with relationship to a Respondent can view that Respondent’s statement.

  • Moderators can only be added or removed on scheduled campaigns.

  • One or more Moderators can be added to the campaign or to individual Respondents.

    • Adding a Moderator to a campaign gives them access to all the workflows in that campaign.

    • Adding Moderators to specific Respondents limits their access to the Respondents' workflows to which they are assigned.

  • The list of available users to add as Moderators is filtered by all active users within the current organization.

    • The user list shows the Name and Email.

  • Multiple Moderators can be added to a single campaign or a single Respondent.

USER STORY 296674 Campaign Creation: Admin and Campaign Coordinator can view completed campaigns.

  • If the campaign is completed (end date met), then the Admin or Campaign Coordinator can see the campaign setup.

  • If the campaign is completed (end date met), then the Admin or Campaign Coordinator can see the schedule Start Date and Duration.

  • All fields are read-only.

USER STORY 295291 Campaign Creation: Edit the Moderators assigned to a Respondent.

The Campaign Coordinator or Admin can add or remove Moderators assigned to the Respondent.

  • The Edit button is in each row of the Respondents table.

  • Clicking Edit will open the Edit Moderators screen.

USER STORY 285919 Campaign Creation: Remove participants from a campaign.

The Campaign Coordinator or Admin can remove participants from a campaign.

  • Respondents, Moderators and Resolution Managers can be removed from scheduled campaigns.

  • If a user has a Conflict Capture role and is assigned a Conflict Capture Category, then the user is automatically added to the scheduled campaign with the same Conflict Capture Category.

  • The Conflict Capture Category assigned to a user always syncs with scheduled campaigns.

  • Removing a participant from a campaign will automatically remove the Conflict Capture Category from the user record.

  • Adding a participant to a campaign will automatically add the Conflict Capture Category to the user record.

  • The Delete button is in each row of the table.

USER STORY 285833 Campaign Creation: Respondent tab and table

The Campaign Coordinator or Admin can see the list of Respondents and review their information.

The Respondent table shows the following columns:

  • Name

  • Job Title

  • Email

  • Conflict Capture Categories

USER STORY 328279 Campaign Creation: If a campaign is active, completed, or cancelled, then the Schedule button will change to View Schedule.

The Campaign Coordinator or Admin can click View Schedule on a completed, cancelled, or active campaign and view the schedule Start Date and Duration.

The Start Date and Duration fields are read-only. 

USER STORY 297052 Campaign Creation: Update the Respondent table and show the Moderators added to a Respondent.

The Campaign Coordinator or Admin can see the Moderators added to a participant and update if needed.

A single Respondent may have dozens of Moderators.

  • On the Campaign Management screen, the Moderators column is included in the Respondents table.

  • The user can expand the cell to see all the Moderators.

  • The user can collapse the expanded cell to the default size.

FEATURE 288019, USER STORY 285810 Conflict Capture Custom Fields

An Admin can create custom fields specific to Conflict Capture to include on Conflict Capture form templates.  

In keeping with current custom field functionality, any edits to Conflict Capture custom fields are applied to all instances of the field on all workflows, contracts, and form templates. 

  • Conflict Capture custom fields are managed in Admin > Organization Management > Custom Fields.

  • To designate a custom field for Conflict Capture, select Conflict Capture as the Field Type.

  • All the field properties are available for Conflict Capture custom fields.

FEATURE 287965, USER STORY 285787 Conflict Capture: Deleting a Campaign

If the campaign status is scheduled, i.e., the start date has not been met, then an Admin or Campaign Coordinator can delete the campaign.

  • If the campaign status is scheduled, then the Delete button will appear on the table row.

  • Upon clicking Delete, the user will see a confirmation message:
    Are you sure you want to delete this campaign?

  • Upon delete confirmation, the campaign will be deleted and removed from the campaign table. 

FEATURE 287963, USER STORY 285972 Conflict Capture: Editing the Campaign Setup

If the campaign status is scheduled, i.e., the start date has not been met, then an Admin or Campaign Coordinator can make the following changes:

  • Update the Campaign Name, Duration, or Send on Date.

  • Change the selected Conflict Capture Statement template.

  • Change the selected Conflict Capture Resolution template.

  • Change the selected Conflict Capture General Information template.

  • Add or remove participants.

  • Send a test workflow to one or more of the recipients. 

If the campaign status is active, i.e., it has started but not completed, then an Admin or Campaign Coordinator can make the following changes

  • Add or remove participants

If the campaign status is completed or cancelled, then no changes can be made.

Once you save the Conflict Capture Category, you cannot change it. This is because it clears the form, essentially requiring you to create a new campaign. If the Conflict Capture Category is incorrect, then delete or cancel the campaign and create a new one.

FEATURE 287961 Conflict Capture Form Templates

By customizing Conflict Capture form templates, customers can collect all the information required to ensure any potential conflicts are identified and resolutions to mitigate the potential conflicts can be documented. The information collected on the forms will vary by the type of position the Respondent holds in the organization and the policies and procedures for managing potential conflicts.

USER STORY 285816 Form Templates: Trigger to identify which value or response in a field indicates a potential conflict

  • The Admin can select the Trigger Conflict trigger to identify which response or value entered in a field indicates a potential conflict. 

  • The Trigger Conflict trigger is only available on the Conflict Capture Statement form. 

USER STORY 285847 Form Templates: Editing a Conflict Capture form template

  • The Admin can edit the Conflict Capture form templates.

  • Changes made to Conflict Capture form templates are not applied to active workflows.

If a conflict capture form template is edited, the latest version of the form template is added to the campaign when the start date is met and the workflows are generated.

USER STORY 285880 Form Templates: Exclude Conflict Capture forms from workflow template builder

In the workflow template builder, Conflict Capture forms will be hidden so that they aren’t inadvertently selected when building a contract workflow template.

This applies to Conflict Capture Statement , Conflict Capture General Info, and Conflict Capture Resolution form templates.

USER STORY 285724 Form Templates: Conflict Capture General Info form template

The Conflict Capture General Info form template is an optional form template that can be included in the Conflict Capture workflow to share information with the workflow participants.

Using custom fields, the Admin can build a General Info form template to capture and provide information relevant for their organization. This could include info from a third-party system integration or custom fields required for reporting.

Because the General Info form can include any info, the Admin can select any custom field to include on the form. This is different from the other Conflict Capture forms, which limit the custom fields to Conflict Capture custom fields.  

  • When the Conflict Capture General Info Form Type is selected, the Conflict Capture Category field will appear.

    • The Admin can select one or more Conflict Capture Categories, including All.

    • The selected Conflict Capture Category will filter the form templates available on the initiate campaign page.

  • Attachment field types are unsupported on the Conflict Capture General Info form.

    • The list of available custom fields excludes attachment field types.

    • The Admin can select any other custom field. 

  • All field properties are available.

  • Once the form template has been saved, the Form Type cannot be changed.

  • All references to field triggers are hidden.

  • Only existing sections with the type Conflict Capture General Info can be added to the form template.

  • The Active/Inactive toggle determines if the Form Template is available for selection on the Create Campaign page. Only form templates set to Active status are available.

USER STORY 285928 Form Templates: Conflict Capture Resolution form template

The Conflict Capture Resolution form template is designed to document a plan to manage any potential conflicts of interest.

  • When the Conflict Capture Resolution Form Type is selected, the Conflict Capture Category field will appear.

    • The Admin can select one or more Conflict Capture Categories, including All.

    • The selected Conflict Capture Category will filter the form templates available on the initiate campaign page.

  • All field properties are available.

  • Once the form template has been saved, the Form Type cannot be changed.

  • The only triggers available are Display Field and Display Static Text. All other triggers are hidden.

  • Only existing sections with the type Conflict Capture Resolution can be added to the form template.

  • The Active/Inactive toggle determines if the Form Template is available for selection on the Create Campaign page. Only form templates set to Active status are available.

USER STORY 285820 Form Templates: Conflict Capture Statement form template

The Conflict Capture Statement form template is designed to solicit responses from a user that identify potential conflicts of interest. The Conflict Capture Statement form is the attestation signed by the Respondent.

  • When the Conflict Capture Statement Form Type is selected, the Conflict Capture Category field will appear.

    • The Admin can select one or more Conflict Capture Categories, including All.

    • The selected Conflict Capture Category will filter the form templates available on the initiate campaign page.

  • When the Conflict Capture Statement Form Type is selected, the Add Certification Text field will appear.

    • This field is optional.

    • If this field is populated, the certification text will appear near the button the Respondent clicks to submit the survey.

  • All field properties are available.

  • Once the form template has been saved, the Form Type cannot be changed.

  • The Add Role to Phase and Notify Phase Owner triggers are hidden.

  • Only existing sections with the type Conflict Capture Statement can be added to the form template.

  • The Active/Inactive toggle determines if the Form Template is available for selection on the Create Campaign page. Only form templates set to Active status are available.

FEATURE 288026 Conflict Capture Categories

Users and forms are assigned one or more Conflict Capture Categories. When the Admin or Initiator creates a campaign, it will auto-populate with the users and forms based on the selected Conflict Capture Category.

285916 Conflict Capture Categories: Editing a Conflict Capture Category

  • The Initiator or Admin can edit Conflict Capture Categories:

    • Click on a row in the table to open the edit modal.

  • Edit the Conflict Capture Category as needed.

  • Toggle the status to Active/Inactive as needed.

  • Click Save.

Changing the status to Inactive removes the Conflict Capture Category from the Conflict Capture Category dropdowns. It does not remove the Conflict Capture Category from user records. 

USER STORY 285714 Conflict Capture Categories: Table

Conflict Capture Categories are listed in a table under Explore > Conflict Capture > Manage Categories.

The table shows the following columns:

  • Conflict Capture Category

  • Status

  • Created Date

  • Created By

  • Last Modified By

  • Last Modified Date

USER STORY 285696 Conflict Capture Categories: Table widgets

The Conflict Capture Categories will have the standard table widgets:

  • Filter Table

  • Manage Columns

  • Export

USER STORY 285717 Conflict Capture Categories: Adding a Conflict Capture Category

The Admin or Initiator can add Conflict Capture Categories so that they can be assigned to users and forms.

Conflict Capture Categories appear in dropdowns in the following places:

  • Form template builder (if the selected Form Type is one of the Conflict Capture forms)

  • Explore > Users > Manage user modal > Conflict Capture

  • Explore > Conflict Capture > Campaigns > Setup New Campaign

To add a Conflict Capture Category:

  • Explore > Conflict Capture > Manage Categories.

  • Enter the Category Name.

  • When finished, click Save.
    OR
    To close the modal without adding a Conflict Capture Category, click Cancel or x.

By default, the status is inactive. Only active categories can be applied to a user profile or a campaign.

FEATURE 296727 Conflict Capture: Managing Participants on Active Campaigns

As a best practice for managing participants on a campaign, we recommend managing the participants on the campaign management page.

Respondents

  • The Admin or Campaign Coordinator can add a Respondent to an active campaign.

  • A Respondent cannot be removed from an active campaign.

Campaign Moderators and Resolution Managers

  • The Admin or Campaign Coordinator can add or remove a Campaign Moderator or Resolution Manager on a campaign.

  • Once they’ve been added to a campaign, the Campaign Moderator or Resolution Manager will have access to all historical workflows for the Conflict Capture Category.

  • If there is only one Resolution Manager on a campaign, then they cannot be removed.

Changing the Conflict Capture Category on the User Record

  • If a Conflict Capture Category has an active campaign, then it can neither be added nor removed on a Campaign Moderator, Resolution Manager or Respondent user record.

USER STORY 429596 Managing Participants on Pending and Scheduled Campaigns: Alert the Admin a user will be added to a campaign if the Admin adds a category with a pending or scheduled campaign.

If an Admin starts to add a Conflict Capture Category with a pending or scheduled campaign to a user record, they’ll see the following alert:

The user will be added to the conflict capture campaigns <list Pending/Schedule campaigns>. Are you sure you want to proceed?

The Admin can confirm or cancel.

USER STORY 430156 Managing Participants on Pending and Scheduled Campaigns: Alert the Admin a user will be removed from a campaign if the Admin removes a category that has a pending or scheduled campaign.

If an Admin starts to remove a Conflict Capture Category with a pending or scheduled campaign from a user record, they’ll see the following alert:

The user will be  removed from the conflict capture campaigns <list campaigns>. Are you sure you want to proceed?

The Admin can confirm or cancel.

USER STORY 296662 Managing Participants on Active Campaigns: Alert the Admin that the category cannot be removed from the Resolution Manager’s user record if there is only one Resolution Manager on the campaign.

If an Admin attempts to remove a Conflict Capture Category from a Resolution Manager’s user record and that user is the only Resolution Manager assigned to a campaign, they’ll see the following alert:

This user is the only Resolution Manager on the campaign(s): [list campaign names]. Campaigns require at least one Resolution Manager. Before you can remove the Conflict Capture Category from the user record, you must add another Resolution Manager to the campaign(s).

USER STORY 429146 Managing Participants on Active Campaigns: Conflict Capture Categories with active campaigns neither be added nor removed on a user record.

The Admin can add a user to a campaign on the campaign management page.  

If an Admin attempts to add a Conflict Capture Category with an active campaign to a Resolution Manager’s user record, they’ll see the following alert:

The Conflict Capture Category <category> cannot be changed on this user record because there is an active campaign for the category.  If you want to add  or remove this user on the campaign, you can do this in Conflict Capture Campaign Management.  Click on the link to open Conflict Capture Campaign Management. [link to Conflict Capture Campaign Management page]

If an Admin attempts to remove a Conflict Capture Category with an active campaign from a Resolution Manager’s user record, they’ll see the following alert:

The Conflict Capture Category <category> cannot be changed on this user record because there is an active campaign for the category.  If you want to add  or remove this user on the campaign, you can do this in Conflict Capture Campaign Management.  

USER STORY 296664 Managing Participants on Active Campaigns: Conflict Capture Categories with active workflows cannot be removed from a Respondent's user record.

Likewise, the Respondent role cannot be removed from the user record.

If needed, the Admin can remove the Conflict Capture Category from the Respondent’s user record once the workflow is cancelled or completed.

If an Admin attempts to remove the Conflict Capture Category from the Respondent’s user record, they’ll see the following alert:

The Conflict Capture Category cannot be removed from this record because it is used in an active conflict capture workflow. Before you can remove the Conflict Capture Category, you must cancel or complete the workflow.  Click on a link below to open a workflow to cancel it. [link to workflow]

USER STORY 296663 Managing Participants on Active Campaigns: Conflict Capture Categories with active workflows cannot be removed from a Campaign Moderator's user record.

If an Admin attempts to remove the Conflict Capture Category from the Campaign Moderator’s user record, they’ll see the following alert:

The user will be removed from the conflict capture campaigns <list campaigns>. Are you sure you want to proceed?

The Admin will be given the option to suppress this message.

USER STORY 296667 Managing Participants on Active Campaigns: Adding Resolution Managers to active campaigns

The Campaign Coordinator or Admin can add a Resolution Manager to an active campaign.

  • This will add the Conflict Capture Category and Resolution Manager role to the user record.

  • The Resolution Manager will be notified via automatic email that they have been added to the campaign.

  • The Resolution Manager will have access to all workflows for the Conflict Capture Category, including those in completed campaigns.

USER STORY 296668 Managing Participants on Active Campaigns: Removing a Moderator from an active campaign

The Campaign Coordinator or Admin can remove a Moderator from an active campaign.

  • This applies Moderators assigned to an entire campaign as well as those assigned to individual Respondents within the campaign.

  • If the Moderator has no other role on the campaign, removing them from the campaign will:

    • Remove the Moderator from the campaign.

    • Remove the Moderator’s access to the workflows associated with the campaign.

    • Remove associated workflows from the Moderator’s worklist.

    • Remove the Conflict Capture Category from the user record.

    • Trigger an automatic email notifying the Moderator they’ve been removed. 

  • If the Moderator attempts to access a workflow to which they were previously assigned, they’ll see a message stating that they do not have access to that workflow.

USER STORY 296666 Managing Participants on Active Campaigns: Removing a Resolution Manager from an active campaign

The Campaign Coordinator or Admin can remove a Resolution Manager from an active campaign, so long as the campaign will have at least one remaining Resolution Manager.

Removing them from the campaign will:

  • Remove the Resolution Manager from the workflows.

  • Remove the Conflict Capture Category from the user record.

  • Remove associated workflows from the Resolution Manager’s worklist.

  • Trigger an automatic email notifying the Moderator they’ve been removed. 

USER STORY 296670 Managing Participants on Active Campaigns: Respondents cannot be removed from active campaigns.

If the Respondent needs to be removed, the Campaign Coordinator or Admin can cancel the individual workflow. Once the workflow has been cancelled, the Admin can remove the Conflict Capture Category from the user record if needed.

If a user attempts to remove a Respondent from an active campaign, they’ll see the following hover text on the Delete icon:

You cannot remove a Respondent from an active campaign. If the Respondent no longer needs to complete the conflict of interest statement, cancel the workflow.  

USER STORY 329824 Managing Participants on Active Campaigns: Update the Suppress alert option.

Within a single session, the Admin can choose to suppress the alert shown when changing a user record in a way that updates a campaign.

  • The message on the alert is Hide this message until your next session.

  • This is a single-session, fixed suppression. 

USER STORY 296671 Managing Participants on Active Campaigns: Adding a Respondent to an active campaign

The Campaign Coordinator or Admin can add a Respondent to an active campaign. They can then add a Campaign Moderator to the Respondent.

Adding a Respondent to a campaign will:

  • Add the Conflict Capture Category and Respondent role to the user record.

  • Add the Conflict Capture Category and Moderator role to the user record (if applicable).

  • Generate the workflow for the Respondent.

  • Send the Initial Email notification to the Respondent.

USER STORY 296669 Managing Participants on Active Campaigns: Adding Campaign Moderators to active campaigns

The Campaign Coordinator or Admin can add a Campaign Moderator to an active campaign.

Adding a Campaign Moderator to a campaign will:

  • Add the Conflict Capture Category and Campaign Moderator role to the user record.

  • Add the Campaign Moderator to the campaign or to the assigned Respondent(s).

  • Give the Campaign Moderator access to all workflows for the Conflict Capture Category, including those in completed campaigns.

USER STORY 296665 Managing Participants on Active Campaigns: Adding a Resolution Manager or Campaign Moderator to a campaign by adding the Conflict Capture Category to the user record

The Admin can only add a Conflict Capture Category to a Respondent’s user record if the campaign is in Pending or Scheduled status. However, a Respondent can be added to an active campaign on the campaign management page.

FEATURE 287988 Conflict Capture: My Worklist Updates

User Story 285841 My Worklist Updates: To access the Conflict Capture worklist, go to Queue > Conflict Capture.

User Story 285864 My Worklist Updates: New queue for Conflict Capture workflows

The table contains the following columns:

  • USER STORY 296675: Workflow Name

  • Respondent

  • Job Title

  • Conflict Capture Category

  • Campaign Name

  • Survey Start Date

  • Campaign End Date

  • Status

  • Resolution Managers

  • Potential Conflict (Yes/No)

  • Resolution Added By

The Conflict Capture Categories will have the standard table widgets:

  • Filter Table

  • Manage Columns

  • Additional Columns

  • USER STORY 355882: Export

The following columns are available via the Manage Columns widget:

  • Campaign Coordinator

  • Campaign Start Date

  • Cancellation Reason

  • Date Resolution Form Submitted

User Story 355881 My Worklist Updates: When the user closes a workflow, they will be directed to the correct list or directory.

  • If a user accesses a workflow via the Conflict Capture worklist, they will be returned to it upon closing the workflow. 

  • If a user accesses a workflow via a notification, they will be directed to the Conflict Capture worklist upon closing the workflow. 

  • If an Admin or Campaign Coordinator accesses a workflow from the Campaign Management page, they will be returned to it upon closing the workflow.  

User Story 355890 My Worklist Updates: Hide the Explore menu for users that only have the Respondent and/or Moderator role.

Users who only have the Respondent or Moderator role should not have access to view the Vendor, Provider, or User Directories. If a user requires access to these directories, the Admin should assign them additional contract roles. 

User Story 381216 My Worklist: The Conflict Capture worklist is the default queue for users who only have Conflict Capture roles.

User Story 295306 My Worklist: The Cancellation Reason column will be available on the Conflict Capture worklist.

  • The column is hidden by default.

  • It can be added via the Manage Columns widget.

FEATURE 287981 Conflict Capture Notifications

User Story 285743 Notifications: Super Admins will be able to configure Conflict Capture email notifications.

User Story 296660 Notifications: Notify the Moderator when they are removed from an active campaign (in-app and email).

User Story 295296 Notifications: Notify participants when a conflict capture resolution is submitted notification (in-app).

  • If one or more conflict capture resolution forms are submitted, the Moderator, Initiator, and Resolution Manager will see an in-app (bell) notification.

  • If a Moderator is only assigned to a Respondent, the notification will appear when the assigned Respondent submits their statement.

  • A user can receive no more than one Conflict capture resolution form submitted notification per day.

User Story 285770 Notifications: Notify participants when conflict capture statements are submitted (in-app).

  • If conflict capture statements are submitted, the Moderator, Initiator, and Resolution Manager will see an in-app (bell) notification.

  • If a Moderator is only assigned to a Respondent, the notification will appear when the assigned Respondent submits their statement.

  • A user can receive no more than one Conflict capture statements submitted in-app notification per day.

User Story 285784 Notifications: Notify Respondents the conflict capture statement is ready to be completed (email).

When the campaign start date is met and the workflow is generated, the Respondent will receive an automated email notification.

User Story 296661 Notifications: Notify the assigned Moderators and Resolution Managers when the campaign starts (in-app and email).

When the campaign start date is met and the workflows are generated, the Moderators and Resolution Managers will be alerted that they have been added to the campaign. They will also receive this notification when they’ve been added to an active campaign.

User Story 285643 Notifications: Notify the Moderators, Campaign Coordinator, and Resolution Managers when conflict capture resolution forms are submitted (email).

  • The email is sent the day after resolution submission.

  • The email is not sent to the Resolution Manager that submitted the form.

  • If a Moderator is only assigned to a Respondent, the notification will appear when the assigned Respondent submits their resolution.

  • A user can receive no more than one Conflict capture resolution forms submitted email per day.

User Story 285771 Notifications: Notify the Moderators, Campaign Coordinators, and Resolution Managers when conflict capture statements are submitted (email).

  • The email is sent the day after statement submission.

  • If a Moderator is only assigned to a Respondent, the notification will appear when the assigned Respondent submits their statement.

  • A user can receive no more than one Conflict capture statement ready for review email per day.

User Story 285641 Notifications: Notify the Respondent a resolution has been submitted (email).

User Story 285786 Notifications: Remind Respondents the conflict capture statement must be completed (email).

Respondents will receive a reminder email every seven days after the campaign start date until they submit their statements.

FEATURE 287984 Conflict Capture Reporting

User Story 449102 Reporting: The customer can schedule a custom Conflict Capture report to go to specified recipients.  

User Story 285837 Reporting: View custom report.

Campaign Coordinators and Admins can view details for all statements.

  • The following fields are available for reporting:

    • Workflow Name

    • Respondent

    • Job Title (Hidden by Default)

    • Conflict Capture Category

    • Campaign Name

    • Status

    • Potential Conflict (Yes/No)

    • Date Resolution Form Submitted

    • Campaign Start Date (Hidden by Default)

    • Campaign End Date (Hidden by Default)

    • Resolution Manager (Hidden by Default)

    • Campaign Coordinator (Hidden by Default)

    • Resolution Added By (Hidden by Default)

    • Cancellation Reason (Hidden by Default)

    • Survey Start Date (Hidden by Default)

  • The Conflict Capture reporting table has the following standard table widgets:

    • Filter Table

    • Manage Columns

    • Additional Columns

    • Export

  • Applicable custom fields, such as questions, resolutions, general info, can be added via the Additional Columns widgets

FEATURE 287958 Conflict Capture Roles

Users who only have Conflict Capture roles have no access to menus relating to contract and workflow management. If a user requires access to these areas, they should be assigned a contract role as well.

USER STORY 285755 Campaign Moderator Role

A Campaign Moderator can view any assigned Conflict Capture Statements to monitor the results and take action on statements with identified potential conflicts. 

  • Can access the campaign workflows where the user is added as Moderator. 

  • Has read-only access to the Conflict Capture Statement, Resolution, and General Info forms.

  • Can record and manage their own campaign workflow comments.

USER STORY 285753 Resolution Manager Role

A Resolution Manager can view assigned Conflict Capture Statements to ensure any identified potential conflicts have a management plan.

  • Can access the campaign workflows where the user is added as Resolution Manager. 

  • Has read-only access to the Conflict Capture Statement and General Info forms.

  • Can record and manage their own campaign workflow comments.

  • Can add and manage their own attachments on assigned campaign workflows.

USER STORY 285931 Campaign Coordinator Role

A Campaign Coordinator can create and manage the campaigns to ensure the correct conflict capture statements are sent to the Respondents, and that statements are reviewed and resolutions are added per their organization's policies.

  • Can access all campaign workflows within the organization. 

  • Has read-only access to the Conflict Capture Statement and General Info forms.

  • Can edit the Conflict Capture Resolution form.

  • Can record and manage their own campaign workflow comments.

  • Can add and manage their own attachments on assigned campaign workflows.

USER STORY 28515 Respondent Role

A Respondent can open, view, and modify their assigned conflict capture statement so they can complete the statement and meet their employment requirements. 

  • Can access the campaign workflows where the user is added as Respondent. 

  • Can update the Conflict Capture Statement form in campaign workflows on which they are the respondent.

  • Has read-only access to the Conflict Capture General Info form.

  • Can record and manage their own campaign workflow comments.

  • Can add and manage their own attachments on assigned campaign workflows.

The Respondent cannot update the form after submitting it.

USER STORY 285930 Conflict Capture Admin Functions

A user assigned the Admin role who has access to the Conflict Capture organization can access, set up, and manage campaigns and statements, and perform tasks on behalf of the Initiator.

  • Create and edit conflict capture custom fields and form templates.

  • Create/initiate, edit, view, and cancel campaigns. 

  • Cancel individual campaign workflows.

  • View all in-progress, cancelled, and completed campaign workflows. 

  • Can record and manage their own campaign workflow comments.

  • Can add and manage their own attachments (and those added by others) on assigned campaign workflows.

USER STORY 285917 Conflict Capture Admin: Validate Conflict Capture role changes to user records and alert Admin if saving changes will affect a campaign.

USER STORY 285708 Conflict Capture Admin: Validate Conflict Capture Category changes to user records and alert Admin if saving changes will affect a campaign.

USER STORY 285656 Conflict Capture Admin: Admins can add or remove Conflict Capture roles on user records.

USER STORY 285637 Conflict Capture Admin: Admins can add or remove Conflict Capture Categories on user records.

FEATURE 297478 Conflict Capture: Updates to user account settings

Unlike contract workflow roles, Conflict Capture roles cannot be proxied.

USER STORY 285648 Conflict Capture Account Settings: Individual users can control whether they receive in-app and bell notifications for Conflict Capture.

Each user can manage their notification settings under Account Settings > Notifications > Conflict Capture Notifications:

Campaign Started

  • Respondent: Conflict Capture Statement is ready

Reminder

  • Respondent: Reminder to complete Conflict Capture Statement

Statements Submitted

  • Campaign Coordinators, Moderators and Resolution Managers: Conflict Capture Statements were submitted

Resolution Form Submitted

  • Campaign Coordinators, Moderators and Resolution Managers: Conflict Capture Resolution forms were submitted

  • Respondent: Resolution form has been submitted for your review

Workflow Cancelled

  • Respondent: Workflow has been cancelled

  • Moderator: Workflow has been cancelled

  • Resolution Manager: Workflow has been cancelled

Participant Removed

  • Resolution Manager: Removed from a campaign

  • Moderator: Removed from a campaign

Campaign Started or Participant Added

  • Moderator: You have been assigned to a campaign 

  • Resolution Manager: You have been assigned to a campaign 

FEATURE 287969 Conflict Capture: Workflows

USER STORY 387741 Conflict Capture Workflow: UI updates for Conflict Capture workflows

  • In the Resolution form phase, the Activate button is renamed Submit

  • Completed workflows show a status of Completed

  • Workflows are listed on the Conflict Capture worklist, Campaign Management Workflow tab, and Reporting > Conflict Capture.

USER STORY 288092 Conflict Capture Workflow: Workflows generated by a campaign are associated with the Conflict Capture organization in which the campaign originated.

USER STORY 285736 Conflict Capture Workflow: Conflict Capture Resolution form

The Conflict Capture Resolution form added to the campaign is displayed on the Resolution Phase.  

  • The Resolution Manager completes the Conflict Capture Resolution form and clicks Submit.

  • An Admin or Campaign Coordinator can also complete and submit the Conflict Capture Resolution form.

  • The Conflict Capture Resolution form is read-only for all Moderators and the Respondent.

  • Once the Resolution Manager (or Campaign Coordinator or Admin) submits the Conflict Capture Resolution form, the workflow status will be Completed.

USER STORY 285830 Conflict Capture Workflow: Workflow history panel

Users with access to a Conflict Capture workflow can see its history in the View History panel.

  • The history records the following actions:

    • Conflict Capture statement is completed.

    • Resolution Phase is completed.

    • Conflict Capture workflow is cancelled. 

  • The history records the following details on these actions:

    • Date/time

    • User who took action

    • Action taken

USER STORY 285765 Conflict Capture Workflow: Attachments panel

The following fields will be hidden in the attachment modal for Conflict Capture workflows.

  • Attachment Category

  • Mark as Confidential checkbox

  • Visible to External Party users

USER STORY 295300 Conflict Capture Workflow: Comments panel

Upon initial release, only the Respondent can be tagged in workflow comments. 

USER STORY 285907 Conflict Capture Workflow: Resolution Managers panel

The Resolution Managers assigned to workflow are listed in a collapsible panel on the right side of the workflow screen.

  • Their names and email addresses are visible.

  • Users with access to a Conflict Capture workflow can see its Resolution Managers.

USER STORY 285682 Conflict Capture Workflow: If a potential conflict is identified, a dismissible banner reading Potential Conflict Identified will appear on the workflow.

  • This is shown after the Conflict Capture Statement is submitted.

  • An indicator will appear next to any field that has a response triggering a potential conflict.

USER STORY 285834 Conflict Capture Workflow: Workflow summary information

Summary information section lists the following information:

  • Respondent 

    • Job title

    • Email

    • Provider or Vendor (For the associated Provider or Vendor link to appear, the Respondent must be added as a contact on a vendor record.) 

    • Conflict Capture Category

  • Campaign Name (Not a link)

  • Campaign Start Date

  • Campaign End Date

USER STORY 285835 Conflict Capture Workflow: Phases

  • The workflow has one phase if the responses to the questions do not trigger the potential conflict flag and the Respondent submits his statement.

    • The workflow moves to completed status.

    • The Resolution Phase is skipped (and hidden).

  • If a submitted response to a question triggers the potential conflict flag, the Resolution Phase starts.

USER STORY 295299 Conflict Capture Workflow: Update the Manage Attachments grid

The following columns are hidden on the Manage All Attachments table on Conflict Capture and Time Tracking workflows.

  • Category

  • Confidential

  • Visible to External Parties

USER STORY 295290 Conflict Capture Workflow: View the completed Conflict Capture Statement in the Resolution Phase.

  • The Conflict Capture Statement tab is added to the Resolution Phase.

  • Users with access to a Conflict Capture workflow can see the Conflict Capture Statement. 

    • They can click on the Conflict Capture Statement tab and view the Conflict Capture Statement form as read-only. 

USER STORY 285909 Conflict Capture Workflow: Conflict capture certification text display

Certification text appears near the Submit button on the conflict capture statement tab.

USER STORY 285735 Conflict Capture Workflow: Conflict capture general info form

In the Statement Phase, the second tab is the General Info tab. It shows the selected conflict capture general information form. 

  • This tab is optional; it will only show if the campaign includes a conflict capture general information form.

  • The conflict capture general information form is ready-only for all workflow participants.

USER STORY 285898 Conflict Capture Workflow: Generate workflow for each Respondent

Workflow participants can review the conflict capture statements and all relevant information in one place.

  • On the Send on Date selected on the setup screen, a workflow is generated for each Respondent.

  • Each Respondent can complete the conflict capture statement.

  • Moderators and Resolution Managers can review the statements and take any required action.

USER STORY 285803 Conflict Capture Workflow: Conflict capture statement form

  • In the Statement Phase, the first tab is the Statement tab.

  • The Statement tab shows the selected conflict capture statement form. 

Respondent Actions

  • Respondent can complete the conflict capture statement form.

  • Respondent can submit the form.

    • The statement form is read-only after the Respondent submits it.

USER STORY 447605 Conflict Capture Workflow: Exclude conflict capture workflows from the dashboard.

To avoid potential performance issues on the Dashboard, the Conflict Capture workflows will be excluded from dashboard widgets upon initial release.   

Bug & Defect Fixes

General

  • BUG FIX 307905 Upon uploading an attachment in the Document Source or Negotiation Phase, Admins and Phase Owners were able to edit the attachment if they opened the attachment via Manage All in the attachments accordion.
    This has been fixed; attachments will remain read-only, as expected.

Searching

  • DEFECT FIX 463427 Some contracts were not searchable from the Contract Library or from the search bar, but users could find the contracts in Reporting or in the vendor directory.
    This has been fixed; all contracts will be searchable from the Contract Library and from the search bar.

Global Search

  • BUG FIX 295138 Numerous categorizations were referred to as “Other” in the search results.
    This has been fixed; search results will be categorized properly, as expected.

  • DEFECT FIX 450376 When a user accessed a contract from an organization different than the organization in the contract location, the contract location appeared blank.
    This has been fixed; the contract location will be appear correctly when a user opens the contract summary page.

Dashboard

  • BUG FIX 436493 A loading wheel persisted on the Cumulative Flow Diagram By Workflow Template widget.
    This has been fixed; the Cumulative Flow Diagram By Workflow Template widget will load as expected.

  • BUG FIX 450790 For large organizations, the action dropdown in the Cumulative Flow Diagram By Workflow Template widget failed to load options.
    This has been fixed; the options for the action dropdown in the Cumulative Flow Diagram By Workflow Template widget will load as expected.

  • BUG FIX 460396 The Cumulative Flow Diagram by Workflow Template widget defaulted to a non-existing workflow.
    This has been fixed; the widget will be blank until the user selects a workflow template from the dropdown.

  • BUG FIX 465142 For organizations with abstraction enabled, the Cumulative Flow Diagram by Workflow Template widget defaulted to abstraction workflows.
    This has been fixed; abstraction workflows will not be included in the dropdown or in the chart.

Contract Requests

  • BUG FIX 471640 The link to request access for Contract Request redirected the user to the worklist.
    This has been fixed; the link to request access for Contract Request will redirect the user to the login page for requesting access, as expected.

Workflows & Worklist

  • BUG FIX 451224 When an Admin retracted the workflow in a phase where they are not the Phase Owner, the Admin was redirected to the worklist.
    This has been fixed; when an Admin retracts a workflow, regardless if they are the Phase Owner for the phase, they will remain within the workflow where they can proceed through the remaining phases.

  • BUG FIX 338759 In the Form Phase, clicking Save Changes returned an error.
    This has been fixed; clicking Save Changes will not return an error.

  • BUG FIX 452031 The Contract Entities, Sites, and Departments filter dropdowns on the worklist listed entities, sites, and departments more than once.
    This has been fixed; the Contract Entities, Sites, and Departments filter dropdowns will list each entity, site, and department only once.

  • BUG FIX 287385 In the Add Attachment modal, when the user checked Mark as Confidential, the Allowed Internal Users dropdown appeared, but the dropdown was not populated.
    This has been fixed; the Allowed Internal Users dropdown will populate as expected.

  • BUG FIX 457053 When a user added or edited an attachment and selected users from the Allowed Internal Viewers and the Allowed External Viewers dropdowns, the users were removed upon clicking Save.

    • When a user selected users from the Allowed Internal Viewers dropdown, those users were removed.

    • When a user selected users from both the Allowed Internal Viewers dropdown and the Allowed External Viewers dropdown, the internal users were saved, but the external users were removed.

    • This has been fixed; selected users from the Allowed Internal Viewers and the Allowed External Viewers dropdowns will remain, as expected.

  • BUG FIX 449589 When a user initiated a workflow from an existing contract and imported contract documents, the filter widget failed to filter the table.

    • The user could select filter options, but all results appeared.

    • This has been fixed; the filter widget will function, as expected.

  • BUG FIX 287700 When an Admin, who was not the Phase Owner, completed a phase, the Admin was redirected to the worklist.
    This has been fixed; when an Admin, who was not the Phase Owner, completes a phase, the page will remain within the workflow where the Admin can proceed through remaining phases.

  • BUG FIX 428937 When the first phase was Auto-Start and the first sequenced participant is the Initiator, upon initiating the workflow, the Initiator was redirected to the worklist, unless the Initiator was also the Phase Manager of the first phase.
    This has been fixed; upon initiation, the Initiator will be directed to the Form Phase.

  • BUG FIX 430783 Users were unable to delete the Effective Date or the Expiration Date on attachments in workflows.
    This has been fixed; users will be able to delete the Effective Date or the Expiration Date on attachments in workflows as expected.

  • BUG FIX 285995 The sorting functionality for the Days Active column of the worklist was inverted: the records were listed from lowest to highest when the column was sorted by DESC, and the records were listed from highest to lowest when the column was sorted by ASC.
    This has been fixed; the sorting functionality for the Days Active column of the worklist will sort the records as expected.

  • BUG FIX 455692 Attempting to retract the Signature Phase to any phase returned a There was an error attempting to retract the workflow error.
    This has been fixed; users will be able to retract the Signature Phase, as expected.

  • DEFECT 452004 For some organizations, attempting to initiate a workflow returned an error.
    This has been fixed; users will be able to initiate workflows, as expected.

  • DEFECT FIX 448921 The date and timestamp in exported files were not consistent with the date and timestamp in the worklist.

    • The format on the export was DD/MM/YYYY HH:MM, and the format on the worklist was MM/DD/YYYY HH:MM.

    • Certain timestamps on the export did not match the data listed in the worklist.

    • This has been fixed; the exported date and timestamp will match the worklist as expected.

  • DEFECT FIX 329456 When a user exported a worklist that had columns added via the Additional Columns widget, the added column(s) contained no values.
    This has been fixed; all column values will be included in the exported file as expected.

  • DEFECT FIX 338621 For some organizations, attempting to initiate a terminated workflow returned a Something Went Wrong Initiating Workflow error.
    This has been fixed; users will be able to initiate terminated workflows, as expected.

  • DEFECT FIX 418962 When a user reassigned a workflow, the link in the email notification directed the user to the worklist, and the newly-generated workflow was not accessible in the worklist.
    This has been fixed; when a user reassigns a workflow, the link in the email notification will direct the user to the workflow, and the newly-generated workflow will be accessible in the worklist.

  • DEFECT FIX 435165 When a participant was inserted into a future phase of the workflow via the Add Role to Phase trigger, and the workflow was retracted from that phase, the green circle indicating that it’s the participant’s turn remained, and users were unable to remove the participant.
    This has been fixed; users will be able to remove participants from the sequence if the phase has not been started.

  • DEFECT FIX 423031 When a user initiated a workflow from an auto-renewal contract, the Renewal Notice Days field was populated on the contract summary page but was blank in the Activation Phase, and the user had to complete the field prior to activating the workflow.
    This has been fixed; if the Renewal Notice Days field is populated on the contract summary page, the Renewal Notice Days field will be populated in the Activation Phase.

  • DEFECT FIX 295158 Comments made on a document in Word were displaced when the user uploaded the document to symplr Contract, and users experienced lagging in the document viewer.
    This has been fixed; comments made on a document in Word will remain in the same place when a user uploads the document to symplr Contract, and users will not experience lagging in the document viewer.

Contract Library

  • BUG FIX 464406 Permission checks were conducted twice, causing to lagging.
    This has been fixed; permission checks will be conducted once.

  • BUG FIX 436513 Users were unable to populate the After [#] Occurrences field in the Add Critical Date modal and the Edit Critical Date modal.
    This has been fixed; users will be able to populate the After [#] Occurrences field in the Add Critical Date modal and the Edit Critical Date modal.

  • BUG FIX 285856 Applying the Associated with a Request Workflow filter returned a Something Went Wrong Loading Contracts error.
    This has been fixed; users will be able to apply the Associated with a Request Workflow filter as expected.

  • BUG FIX 300328 CUSTOMER_ROOT_NODE appeared in the Location column on the contract summary page, and the nodes were not listed in the correct order.
    This has been fixed; CUSTOMER_ROOT_NODE will not appear in the column, and the nodes will be listed in the correct order.

  • BUG FIX 385408 In the Delete Attachment modal, the original filename of the attachment was listed instead of the filename.
    This has been fixed; in the Delete Attachment modal, the filename that was created when the attachment was uploaded will be listed.

  • BUG FIX 450233 When a user uploaded an attachment, some pages were not rendered in the PDF viewer, causing the attachment to contain blank pages.
    This has been fixed; the PDF viewer will render the attachment, as expected.

  • DEFECT FIX 340006 Admins and Editors with department-level permissions were unable to add or edit contract descriptions on contract summary pages for contracts that they have access to.
    This has been fixed; Admins and Editors with department-level permissions will be able to add or edit contract descriptions on contract summary pages as expected.

  • DEFECT FIX 426380 The Contract Entities, Sites, and Departments filter dropdowns in the Contract Library listed entities, sites, and departments more than once.
    This has been fixed; the Contract Entities, Sites, and Departments filter dropdowns will list each entity, site, and department only once.

  • DEFECT FIX 417131 When a user opened a contract, the pages loaded slowly and the pages were blank.

    • After the blank pages loaded, the pages reloaded with the correct information.

    • This has been fixed; a spinner will appear during a slow request, and blank pages will not be loaded.

  • DEFECT FIX 328390 When a user clicked the Request hyperlink in the contract header, they were redirected to a blank worklist page.
    This has been fixed; clicking the Request hyperlink in the contract header will redirect the user to the request workflow.

DocuSign

  • BUG FIX 463973 When a user clicked Done on the DocuSign envelope setup, they were redirected to a blank white page.
    This has been fixed; clicking Done on the DocuSign envelope setup will redirect the user to the workflow in the symplr Contract.

Permissions

  • BUG FIX 431091 Users with an Admin role that was not organization wide were unable to access the Workflow Templates tab, and were thus unable to add, edit, or copy workflow templates.
    This has been fixed; all Admins, regardless of the location nodes associated with the Admin permission set, will be able to access the Workflow Templates tab to add, edit, and copy workflow templates.

  • BUG FIX 456190 Users with an Admin role that was not organization wide were unable to add, edit, or delete a Provider Exclusion Verification in the provider directory.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the Exclusion Verification controls to add, edit, or delete a Provider Exclusion Verification in the provider directory.

  • BUG FIX 456185 Users with an Admin role that was not organization wide were unable to add, edit, or delete Exclusion Verification in the vendor directory.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the Exclusion Verification controls to add, edit, or delete Exclusion Verification in the vendor directory.

  • BUG FIX 456138 Users with an Admin role that was not organization wide were unable to add, edit, or delete attachments on vendor profiles.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the (+) Attachment to add, edit, or delete attachments on vendor profiles.

  • BUG FIX 456121 Users with an Admin role that was not organization wide were unable to add, edit, or delete attachments on provider profiles.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the (+) Attachment to add, edit, or delete attachments on provider profiles.

  • BUG FIX 440462 Users with an Admin role that was not organization wide were unable to add or edit vendor contacts or provider contacts.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the controls to add or edit vendor contacts and provider contacts.

  • DEFECT FIX 317660 Users with an Admin role that was not organization wide were unable to add or edit users, vendors, or providers.
    This has been fixed; all Admins, regardless of the location notes associated with the permission set, will be able to access the controls to add or edit users, vendors, and providers.

  • DEFECT FIX 452704 External party users were able to view comments in which they were not tagged.
    This has been fixed; External party users will be able to view only comments in which they are tagged.

Permission Overrides

  • DEFECT FIX 435205 Users who were granted the Editor role via permission overrides did not receive Editor capabilities.
    This has been fixed; users granted the Editor role via permission overrides will have Editor capabilities as expected.

Reporting

  • BUG FIX 313870 In the Attachments tab, when a user sorted the Attachment Name column in ascending order, then attempted to sort the column in descending order, the column would remain in ascending order.

    • The sorting arrows updated with each click.

    • This has been fixed; clicking the top arrow will sort the column in ascending order, and clicking the bottom arrow will sort the column in descending order, as expected.

  • BUG FIX 441644 Scheduled reports for Providers, Users, and Attachments failed to send.
    This has been fixed; scheduled reports for Providers, Users, and Attachments will send as expected.

  • BUG FIX 453576 Saved filters with no associated organization prevented all other scheduled reports from being sent out.
    This has been fixed; saved filters with no associated organization will be ignored, and all other scheduled reports will be sent out, as expected.

  • DEFECT FIX 295157 When a user switched organizations while on the Contracts tab of Reporting, the table reloaded, but the contracts for the original organization remained.
    This has been fixed; the contracts in the table on the Contracts tab of Reporting will reflect the selected organization.

Directories

  • BUG FIX 381257 When a user entered an email address and job title in the Add Vendor modal then saved and closed the modal, the email address and job title failed to appear on the vendor profile or in the Edit Vendor modal.

    • The email address and job title values appeared in the vendor directory.

    • This has been fixed; if a user enters an email address and/or job title, the value(s) will appear in the vendor directory, vendor profile, and Edit Vendor modal, as expected.

  • BUG FIX 355608 In the Edit Provider modal, clicking the X in the Credential field failed to remove the credential.
    This has been fixed; clicking the X in the Credential field will remove the credential as expected.

  • BUG FIX 440050 Attempting to export the user directory or the provider directory with an applied filter as an Excel file returned an error, and the file failed to download.
    This has been fixed; users will be able to export the user directory or the provider directory with an applied filter as an Excel file as expected.

  • BUG FIX 427134 CUSTOMER_ROOT_NODE appeared in the Location column of the provider directory, and the nodes were not listed in the correct order.
    This has been fixed; CUSTOMER_ROOT_NODE will not appear in the column, and the nodes will be listed in the correct order.

  • BUG FIX 337766 In the user directory, when a user sorted by a column, the rows were rearranged but not in any particular order.
    This has been fixed; users will be able to sort columns by alphabetical order, reverse alphabetical order, ascending, or descending as expected.

  • DEFECT FIX 336393 When an Admin edited a provider’s address then clicked Save, the page was returned to the Provider Details screen, but the edits failed to save.
    This has been fixed; when an Admin edits a provider’s address then clicks Save, the page will return to the Provider Details screen, and the edits will save as expected.

  • DEFECT FIX 435181 Abstraction Team users appeared in the user directory.
    This has been fixed; Abstraction Team users will be hidden in the user directory as expected.

  • DEFECT FIX 416806 In the user directory, pages beyond page 5 were blank.
    This has been fixed; all active users will be viewable in the user directory as expected.

  • DEFECT FIX 416550 When a user exported the user directory via the Export widget, the report included no more than 100 results.
    This has been fixed; reports will not be capped at 100 results.

  • DEFECT FIX 456816 Users, regardless of permissions, received a No records found. message when attempting to view the vendor directory.
    This has been fixed; the vendor directory will list all vendors, as expected.

  • DEFECT FIX 450448 When a user unchecked Department checkboxes under Contract Permissions in a user’s profile then clicked Update Permission, the changes failed to save.
    This has been fixed; edits to user permissions will save when a user clicks Update Permission, as expected.

  • DEFECT FIX 461468 In the user directory, the values for the Last Login column were inaccurate.
    This has been fixed; the Last Login column will show the date of the most recent login, excluding the user’s current login if that user is currently in a session.

Admin

User Groups

  • BUG FIX 286114 The Roles dropdown in the filter table widget of the user group page was not displayed properly, and users had to scroll down to view the dropdown.
    This has been fixed; the Roles dropdown will display as expected.

Form Templates

  • DEFECT FIX 318865 The warning modal for saving changes before navigating away failed to appear.
    This has been fixed; when a user attempts to navigate away from unsaved changes, the warning modal will appear, as expected.

Workflow Templates

  • DEFECT FIX 295164 When an Initiator was added to the Available Participants section before being added to the Participant Sequence, the Initiator did not appear in the Set Participant Sequence modal.
    This has been fixed; Initiators added to the Available Participants section will appear in the Set Participant Sequence modal, as expected.

Smart Templates

  • DEFECT FIX 447833 When a user saved a smart template with the same name as a smart template in another organization, the smart template from the original organization was deleted.

    • Smart templates must have a unique name for each organization, not each tenant.

    • This has been fixed; saving a smart template with the same name as a smart template in another organization will not delete the smart template from the original organization.

Classifications Management

  • BUG FIX 325020 The Contract Categories field failed to populate in the workflow header.
    This has been fixed; the Contract Categories field in the workflow header will populate with contract type(s) associated with the contract category.

Time Tracking (TERMS 2.0)

  • BUG FIX 440395 When adding a timesheet form to a timesheet schedule configuration, upon the user making a selection from the Add Timesheet Form dropdown, the dropdown became disabled.

    • This has been fixed; when adding a timesheet form to a timesheet schedule configuration, the Add Timesheet Form will be enabled (i.e., editable) until the selection is canceled or saved.

    • The form template cannot be changed after it is saved on a timesheet.

  • BUG FIX 449634 When the Time Reporter Cannot Certify a Timesheet Without Time Entries toggle was off upon opening the screen, clicking Save after adding or removing an email address from the Email Contacts For Locked Timesheets field returned a Something Went Wrong Saving Timesheet System Settings error.
    This has been fixed; users will be able to add or remove an email address from the Email Contacts For Locked Timesheets field, as expected.

  • BUG FIX 450932 When the Email Contacts For Locked Timesheets field was empty, clicking Save after toggling off the Time Reporter Cannot Certify a Timesheet Without Time Entries toggle returned a Something Went Wrong Saving Timesheet System Settings error.
    This has been fixed; users will be able to toggle off the Time Reporter Cannot Certify a Timesheet Without Time Entries and save changes, as expected.

  • BUG FIX 427521 Users were able to add the same user as a Timesheet Reporter and a Timesheet Assistant.
    This has been fixed; users will not be able to add the same user as a Timesheet Reporter and a Timesheet Assistant.

  • DEFECT FIX 355530 After the timesheet had been certified, the add comment button was missing for Timesheet Assistants and for Timesheet Reporters, and the add attachment button was missing for Timesheet Reporters.
    This has been fixed; the add comment button and the add attachment button will be available for both the Timesheet Assistants and the Timesheet Reporters, including after the timesheet has been certified.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.