These items were deployed on the morning of Thursday, December 9th, 2021.
Our release nomenclature has changed. We have retired mountain names for a simple numeric system. As this is the first major release of the year using our new nomenclature, it is called 2021.1. Our first major release next year will be 2022.1, and the second will be 2022.2.
Logo and Color Updates
As you may be aware, TractManager (MediTract) joined the symplr family in December 2020. We have updated the application to reflect this. You’ll see the symplr Contract logo in place of MediTract and TractManager logos, as well as a few color changes (to a different shade of blue).
FEATURE 285655 MediTract and TractManager logos and references throughout the application will be replaced with the symplr Contract logo and name. These changes will be be visible in the following places:
USER STORY 285660 Login screen
USER STORY 288146 Favicon and text in your browser bar and bookmarks
USER STORY 285776 Application header
USER STORY 285715 System email notifications
USER STORY 285806 Knowledge base
FEATURE 287977 The color scheme of the application will be updated to symplr colors.
The most conspicuous change will be the header, which will change from vivid blue to charcoal blue.
Form Data Ordering
FEATURE 288008 The Form Data panel on the workflow page will list form fields in the order they appear on the form.
User Story 285799 The field layout in the Form Data panel will reflect the field layout of the form.
The column layout in the Form Data panel will reflect the column layout of the form.
Field sections and their names in the Form Data panel will reflect the field sections and their names on the form.
Users will be able to expand and collapse individual sections. Sections will be collapsed by default.
User Story 285934 A search bar will be added to the top of the Form Data panel.
The search feature will support type-ahead searching.
Field names and field values will both be searchable.
If the search term doesn’t exist within the form data, “No results found” will appear below the search bar.
FEATURE 287818 SmartTemplates allow Admins to configure document templates to automatically insert data elements and approved language into the correct points throughout a contract. The feature will automatically merge form data and approved language, producing a finished contract during the workflow’s Document Source Phase.
A SmartTemplate is a document template containing SmartTags.
A manual template is an ordinary document template without SmartTags.
A SmartTag is a system-generated, unique ID for a field name or approved language record that can be read by the in-app document editor upon merging.
Merging is the action a user will take to replace the SmartTags in a SmartTemplate with their associated field data and/or approved language.
A SmartTag that was not merged during the merge operation may be caused by blank form fields.
USER STORY 285679 Within the document template library, Admins will be able to create SmartTemplates.
There will be two Add buttons: Add SmartTemplate | Add Manual Template
Clicking Add SmartTemplate will open the Smart Templates page, where the Admin will be prompted enter and/or select general information:
At least one Contract Type
Upload a source file
The source file must be a DOC or DOCX.
The SmartTemplate cannot be saved until the required general information has been entered.
The SmartTemplate cannot be deleted until it has been saved.
The SmartTemplate will be unpublished by default. It will be unavailable in all workflows unless the status is set to Published.
The SmartTemplate attributes will be editable and the source file will be replaceable.
Replacing the source file will overwrite any SmartTags applied to the previous source file. The Admin will have to apply SmartTags in the new file.
USER STORY 285678 Within the document template library, an Admin will be able to insert SmartTags into a source file, creating a SmartTemplate.
When inserting SmartTags into a SmartTemplate, consider when the corresponding field values will be populated in a workflow. Key terms that will be entered during the Activation Phase will not be available for merging during the Document Source Phase.
Clicking on the instructional text will reveal the file contents.
The document will be editable.
To add a SmartTag, the Admin will click inside the document where the tag will go, search for and select the field name or approved language record, and then click Add.
The Admin will be able to remove and replace SmartTags as well.
BUG FIX 320984 Within the SmartTemplate editor, the Save button is failing in the Tagging Section. As a workaround, return to the General Information section, and click Save there.
We are actively working to fix this; we plan to deploy a fix in the near future.
USER STORY 285761 If an Admin deletes a SmartTemplate, then a warning message will list all active workflows using that SmartTemplates.
There will be an option for the Admin to receive an email listing the affected form templates.
The Admin will be able to cancel or save their edits.
USER STORY 285796 If an Admin deactivates or edits an approved language record that is part of a SmartTemplate used in an in-flight workflow, then a warning message will list the affected workflows and SmartTemplates.
There will be an option for the Admin to receive an email listing the affected workflows and SmartTemplates.
The Admin will be able to cancel or save their edits.
USER STORY 285762 If an Admin deactivates a custom field that is part of an in-flight workflow or SmartTemplate, or triggers a document template, then a warning message will list the affected form templates, workflow templates, and SmartTemplates.
There will be an option for the Admin to receive an email listing the affected form templates, workflow templates, and SmartTemplates.
The Admin will be able to cancel or save their edits.
If an Admin attempts to delete a custom field that triggers a document template, then they will see a modal stating that they must deactivate the custom field before it can be deleted.
SmartTemplates in Form and Workflow Templates
USER STORY 285828 Within the workflow template editor, Admins will be able to select one or more templates (manual or SmartTemplate) to automatically appear in the Document Source Phase.
If a workflow template has multiple Document Source Phases, then Admins can configure the template so that different templates automatically appear in different phases.
Within individual workflows, users with adequate permissions can delete or alter the templates.
If a user deletes an automatically added document template, and the Document Source Phase is retracted, then that document template will reappear when the Document Source Phase is reinitiated.
USER STORY 285818 Within the form template builder, a new trigger action, Add Template(s) to Phase, will allow Admins to configure custom field triggers to add a document template to the Document Source Phase of a workflow based on a value entered in the Form Phase.
This trigger action can be configured for all data and input types except attachment fields.
The Admin will select the document template in the workflow template builder.
SmartTemplates in Workflows
USER STORY 285746 Starting a Document Source Phase will automatically check for the trigger type Add Template(s) to Phase.
If any triggers of this type exist within the workflow and the trigger conditions are met, then the appropriate document templates will be added.
USER STORY 285827 Within the Document Source Phase of a workflow, a user with adequate permissions will be able to add a SmartTemplate by clicking + Add Document.
A new selection, Choose SmartTemplate, will be available under Document Source.
USER STORY 285763 In workflows containing SmartTemplates, the Phase Manager or Admin will be able to merge the data one or more times.
The Phase Manager or Admin must be sequenced into the workflow to merge the data.
If a SmartTemplate document contains at least one SmartTag, the Merge button will be available, and it will show the number of SmartTags that haven’t been merged.
If there are no SmartTags to be merged, the button will update to Merged and be unavailable.
Any merged fields and approved language in the document will be highlighted in yellow.
Remaining fields will retain their original tagged appearance.
After the first merge, a feedback bar will appear, showing the number of fields merged and the number of fields remaining to be merged.
In the feedback bar, clicking Learn More will open the merge status modal.
The modal will list SmartTags and their merged values, so the user can reconcile the data.
Fields remaining to be merged will be highlighted as “Merge Pending.”
Clicking Undo will remove the merged fields from the document.
Editing the Organization Hierarchy
Feature 285948 Super Admins will be able to edit the organization tree.
Locations will be movable within their parent nodes. The application will prevent moving location nodes to other parent nodes to avoid problems with permissions, workflow templates, etc.
Super Admins will be able to edit the display name and the sort name of each location node, i.e. Entity, Site, and Department, within the organization tree.
The display name will determine the label the end user will see within the organization tree.
The sort name will determine the order in which the child node appears within the organization tree.
Super Admins will be able to toggle individual location nodes to inactive status, preventing them from being selected throughout the UI, except for non-new workflows on existing contracts.
Alphabetization will be enforced within Department lists in the organization tree.
To accommodate acronyms, alphabetization will be case-insensitive.
Updates will be applied everywhere the organization tree appears within the application.
To avoid disruption, we will not enforce case-insensitive alphabetization for existing customers' organization trees. If you would like alphabetization enforced within the Departments in your organization tree, contact a symplr Contract representative.
USER STORY 288087 Super Admins will be able to edit the organization tree under Admin > Organization Management > Locations.
USER STORY 285884 Super Admins will be able to export the organization tree as a CSV or XLSX file, using the same Export widget used throughout the application.
USER STORY 287649 Selecting a node in the organization tree within the Locations tab under Organization Management will open the Edit Location Details panel for that node.
USER STORY 287646 Clicking the Edit Location Details button within the Edit Location Details panel will show the location details for the selected node.
Super Admins will be able to add optional location and contact information:
City, State, Zip
USER STORY 285670 Super Admins will be able to toggle location nodes to Inactive/Active.
If a location node is inactive, then it will be unavailable in all instances where a user would select a contract location.
Toggling a location node to inactive will not affect in-flight workflows or previously activated contracts.
USER STORY 307310 Inactive location nodes will be hidden on the organization tree except in previously activated contracts using the inactive location node.
On previously activated contracts and their workflows (i.e., amend/extend/terminate/renew), (Inactive) will appear next to any inactive location nodes.
USER STORY 285902 Alphabetization will be case-insensitive, so that abbreviations and acronyms can be recognized and sorted appropriately.
USER STORY 287623 Super Admins will be able to apply custom nomenclature to the levels of the organization tree, i.e. rename Entity, Site, and Department.
Custom names will apply to column headers, filters, and other column management terminology.
Within the organization tree, iconography (colored circles with initials) will reflect custom names.
USER STORY 285710, 285901 Super Admins will be able to edit the display name and the sort name of each Entity within the organization tree.
Each Entity will have a display name and a sort name. Tooltips will explain the difference between them.
End users will see the display name in the organization tree and wherever contract locations are shown, including column headers, filters, and other column management terminology.
The sort name will determine the order in which the Entity appears within the organization tree.
Sorting is case-insensitive and alphabetical.
For example, if the display names are North Campus, South Campus, East Campus, and West Campus, and their respective display names are Entity_D, Entity_C, Entity_B, and Entity_A, they’ll appear in the organization tree in the following order: West Campus, East Campus, South Campus, North Campus.
USER STORY 285929 Within their account settings, individual users will have the option to see the organization tree expanded by default throughout the UI.
Under Account Settings > User Profile, there will be an Expand Org Tree by Default toggle.
This toggle will default to showing the organization tree collapsed.
Contract Categories: Assigning Contract Types
FEATURE 302830 Super Admins will be able to assign existing Contract Types to new and existing Contract Categories.
Admins have read-only access to the Contract Categories sub-tab.
USER STORY 300525 When creating a new Contract Category, Super Admins will be able to select existing, active Contract Types to assign to that Contract Category.
Only active Contract Types can be assigned to a Contract Category.
USER STORY 300526 Super Admins will be able to edit Contract Type assignments under the Contract Categories tab.
Clicking on a Contract Category in the table will open a fly-out window, where the Super Admin can select one or more active Contract Types to assign to the selected Contract Category.
USER STORY 300524 Users will be able to see and select active Contract Categories when:
Initiating a workflow
Adding a document template
Adding a workflow template
For a Contract Category to appear, it must have at least one assigned Contract Type.
Bug & Defect Fixes
BUG FIX 295140 Including some special characters in a search returned an error.
This has been fixed; special characters in a search will not return an error.
BUG FIX 312542 When users attempted to access the dashboard via Explore > Dashboard, the page failed to load.
This has been fixed; users will be able to access the dashboard as expected.
Workflows & Worklist
DEFECT FIX 300528 When users exported the Worklist, the Excel report included only the first 100 workflows.
As part of this fix, when the Include Previously Completed Items toggle is off (its default setting), the filter for Status: In Process and Blocked will appear above the table, showing that it has been applied (via the toggle).
This has been fixed; all workflows will be included on the report as expected.
BUG FIX 320784 If you toggle Include Previously Completed Items ON, which removes the Status: In Process and Blocked filter, the worklist table will appear as expected.
However, if you click the x to remove the Status: In Process and Blocked filter, or click Clear All, then the filter will be removed, but the Include Previously Completed Items toggle will still appear off. The results will still include previously completed items, but without the visual indicator.
We are actively working to fix this; we expect to deploy a hotfix sometime next week.
DEFECT FIX 305187 Approvers with correct permissions to view the workflow appeared in the User dropdown of the Add Phase Participant modal, but selecting the Approver and clicking Add failed to actually add the Approver to the workflow.
This has been fixed; Approvers with correct permissions to view the workflow will appear in the User dropdown of the Add Phase Participant modal, and users will be able to add them as a participant.
BUG FIX 285782 The Location column in the timesheet grid was mislabelled as CUSTOMER_ROOT_NODE.
This has been fixed; the organization hierarchy will be shown in the Location column as expected.
DEFECT FIX 295171 In the contract library table, the Associated Workflows in Progress column failed to populate.
Note that this column is excluded from the table by default. The defect was observed when a user added the Associated Workflows in Progress column to the table using the Manage Columns widget.
This has been fixed; when present, the Associated Workflows in Progress column will populate as expected.
BUG FIX 285858 When a user clicked the edit pencil or Save, a blank phase is shown, and the phases, workflow template name, and Contract Type cannot be edited.
This has been fixed.
When a user clicks the edit pencil on an existing workflow template, the phase to be edited will retain all of the values that were previously saved to it.
When a user clicks Save, the user can enter or edit the workflow template name and contract types.
BUG FIX 308304 Filter dropdowns were empty, causing filter dropdowns to be non-functional.
This has been fixed; filter dropdowns will populate and function as expected.
BUG FIX 308308 When an Admin adds a new user, the user does not appear in the filter until the page is refreshed.
This has been fixed; the newly added user will appear in the filters as expected.
DEFECT FIX 288798 When a user retracted the survey from the Complete Phase, the survey retracted, but the survey was uneditable.
The phase tracker highlighted the Complete Phase, despite the Pulse Check Phase being the active phase.
The survey was inaccessible to the Initiator, and attempting to access the survey via a notification returned an error.
The survey failed to appear in the worklist for the Initiator and the Admin.
This has been fixed; the survey will retract to the previous phase and user as expected.