Feature Enhancements

Button Field Type: A new field type labeled ‘Button’ has been added. This field can be used to trigger a variety of actions at the stage level, including both out of the box and custom API calls/integrations, notifications, child workflows, and form mappings. For more information on the button field, visit our success center page here.

Multiple API Calls on Stage/Relationship: Users can now configure up to 5 API calls on a given stage or relationship. Calls on a relationship are executed in series and can use values returned from previous calls in the series. Stage calls can be executed in series, or linked to specific actions/fields. For more information on configuring custom API calls, visit our success center page here.

Workflow Flags: Users can now create Flag Conditionals and apply them to stages. When triggered, workflow records will highlight on the dashboard according to the color/rules setup in the Conditional. For more information on Workflow Flags, visit our success center page here.

Conditionally Hide Submit Bar: The submit button can now be included in show/hide conditions. The submit bar will appear as its element ID when configuring show/hide conditions on a stage.

Copy/Paste Stages and Relationships: When configuring a workflow template, users can now copy and paste stages and relationships. To copy a stage, select a stage and use right click, then select 'Copy. To paste, right click and select ‘Paste’. If two or more stages are copied/pasted, the relationship(s) connecting those stages will also be copied/pasted.

Workflow Email ID Available in Form Mapping: The email ID that allows a user to send notifications and attachments directly to a workflow record is now available to be used in form mapping. When configuring a form mapping rule, users can select workflow email ID as the value to be entered into the child field. This will allow users to automatically include this ID in notifications.

User Search: Search functionality has been enabled for the ‘Users’ page in Administration. Admins can search on any field contained within a user’s profile, and can search on up to five fields at a time.

Show in Audit Trail Toggle: A new field option called ‘Show in Audit Trail’ has been added to all TAP Fields. This will allow users to hide the field value in the audit trail to all users, or to conditionally hide a field value based on a user's role.

Prevent Save Option: A new field option called ‘Required for Save’ has been added. When checked, the designated field(s) must be filled before a user can save the form.

Configure ‘Save Workflow’ Email: Users can now configure the email that is sent when using the ‘generate as draft url’ option for saving workflows.

Link Records Through Workflow Lookup: The workflow lookup field can now be used to link records. When configuring that field, users will have the option to check ‘Link Records’. When checked, a record that is entered into this field will be linked to the record that was created using that field. Linked records will display within the audit trail of all records they have been linked to. For more information on the workflow lookup field, visit our success center page here.

Linked Records Action: A new dashboard action has been created labeled ‘Show Linked Records’. When selected, the dashboard will filter to display all records which have been linked to the selected record.

Current Assignee in Audit Trail: The current assignee of the stage will now be displayed in the audit trail.

Form Map Tables: Tables can now be used in form mapping. Individual table cells can be form mapped into text fields, and vice versa. Entire tables can be form mapped into child tables.

Prepopulate Tables: Tables can now be prepopulated when using prepopulation with workflow records field. Tables can only be mapped to other tables when configuring a workflow records prepop rule.

Resend Notifications: A new dashboard record action has been added labeled ‘Resend Notification’. When selected, the last ‘Next Action’ notification for that record will be resent. This functionality is tied to a new permission and is only available to users who have been granted that permission within the admin section.

 

Bug Fixes

Issue: Able to download a file using API endpoint
Tracking Code: TAPSUP-2593
Salesforce Case Number: 2020-1021-690638
Expected Result: Security concern, files are no longer able to be downloaded through certain API endpoints.

Issue: Unable to export data from dashboard
Tracking Code: TAPSUP-2877
Salesforce Case Number: 2020-1117-699441
Expected Result: Fix for issue that occurred when trying to export large amounts of records from the dashboard.

Issue: Validation bypassed when field is conditionally hidden
Tracking Code: TAPSUP-3471
Salesforce Case Number: N/A
Expected Result: Validation will trigger correctly when configured on fields which are hidden by conditions, but which have the ‘submit even if hidden’ checkbox checked on the condition configuration for that field.

Issue: Pre- population of fields from contacts in TC not consistently working for each contact
Tracking Code: TAPSUP-2976
Salesforce Case Number: 2021-0203-728094
Expected Result: Fields within a contact object in TC will now prepopulate correctly into TAP

Issue: Request ID different from workflow ID when generated through mapping
Tracking Code: TAPSUP-3008
Salesforce Case Number: 2021-0223-737897
Expected Result: Issue was related to form mapping during first stage of the workflow. Correct request ID will populate when form mapping request ID into a field during the first stage of a workflow. 

Issue: Department Permissions set by dropdown field does not work when used with "visible to requester's department" or "show previous result" form access
Tracking Code: TAPSUP-3342
Salesforce Case Number: 2021-0430-77444
Expected Result: Departments Dropdown field can now be used in conjunction with ‘visible to requester’s department’ permission. Form can be submitted when that field is set to ‘show previous result’.

Issue: Unable to send document field to e-signature using Docusign
Tracking Code: TAPSUP-3356
Salesforce Case Number: 2021-0521-783427
Expected Result: Document field type can be used with Docusign now.

Issue: Custom values in TC support disappear after closing and reopening WF template
Tracking Code: TAPSUP-3470
Salesforce Case Number: N/A
Expected Result: Custom values entered into a TC Integration field mapping will be retained when saving and closing/reopening the mapping popup.

Issue: Formula doesn't work when value is set to empty string
Tracking Code: TAPSUP-3472
Salesforce Case Number: N/A
Expected Result: When using the value ‘’ as the end value in a formula, the field will be cleared.

Issue: Unable to see audit trail for child workflows
Tracking Code: TAPSUP-3474
Salesforce Case Number: N/A
Expected Result: The audit trail is accessible for child workflows that were initiated by a parent workflow.

UPDATE - TAP 1.7.1 Bug Fixes

Issue: API Broken with 1.7.0.0 Release
Tracking Code: TAPSUP-3670
Salesforce Case Number: N/A
Expected Result: Workflows initiated by an API will not throw an error when the relationship being submitted to has an external api configuration added.

Issue: Relationship preceeding the last stage has next action notification
Tracking Code: TAPSUP-3671
Salesforce Case Number: N/A
Expected Result: Relationships leading into completed stage will not have next action notification.

Issue: Auto submit with delay not working
Tracking Code: TAPSUP-3672
Salesforce Case Number: N/A
Expected Result: Workflows scheduled to autosubmit on delay with submit according to autosubmit configuration.

Issue: Non Super Admin Dashboard Screen Never Loads
Tracking Code: TAPSUP-3673
Salesforce Case Number: N/A
Expected Result: Non super admins will not experience time outs when loading different dashboard views/searches.

Issue: Existing and new SFDC setup broken
Tracking Code: TAPSUP-3674
Salesforce Case Number: N/A
Expected Result: Salesforce matter 'type' dropdown will display correctly and will not clear all mapping fields.

Issue: Workflow load error
Tracking Code: TAPSUP-3737
Salesforce Case Number: N/A
Expected Result: Workflow specific. Workflow will load correctly and should load quicker.

Issue: Unable to save workflow after modifying in staging
Tracking Code: TAPSUP-3739
Salesforce Case Number: N/A
Expected Result: Workflows with external api configurations will save.