The issues listed below are fixed in the 21R1 release.
| Description |
Issue No. |
|
Admins can delete a group even if the group is used in a document lifecycle role’s default and override rules.
|
DEV-295604 |
|
When importing an inbound package, validation incorrectly identifies some objects with a status of Missing – Block.
|
DEV-328442 |
|
The default field labels display the ID value instead of the Name value on the Field Rule Detail page.
|
DEV-343872 |
|
Using the in-line editor to update the Actual Start Date of a Milestone results in an error.
|
DEV-344068 |
|
When a user loads object records with Vault Loader, Vault returns a “Success” message but does not update document reference fields.
|
DEV-347238 |
|
Vault does not display a default value for the Rendition Status dropdown menu.
|
DEV-347865 |
|
Users with delegates do not receive the delegate version of the notification.
|
DEV-349506 |
|
In some cases, Vault may fail to export a CSV domain users list that includes a large number of columns.
|
DEV-352957 |
|
Using the Create button to add data to a newly created Audit record may result in an insufficient privileges error and inability to save changes.
|
DEV-359354 |
|
Saving a question design results in a server error if the checklist design field is empty.
|
DEV-359751 |
|
Clicking an Action menu for Report records may result in an exception written to the logs.
|
DEV-359970 |
|
For groups with 200 or more profiles, the group detail page may not correctly display all profiles in the group.
|
DEV-361054 |
|
In some cases, clicking the Select All button on the Review and Select Steps page when deploying a configuration migration package may not correctly select all items.
|
DEV-362030 |
|
The Vault Memberships list on the Domain User details page list may incorrectly show membership in vaults that are marked for deletion.
|
DEV-362198 |
|
In some scenarios, jobs stay in “Running” status and do not succeed or fail.
|
DEV-362366 |
|
In some cases, clicking on a Web Action record results in a server error.
|
DEV-364404 |
|
In some cases, the Filter Tab field on custom tabs does not display the filter value, though the filters are applied as expected.
|
DEV-365468 |
|
In some cases, deleting custom Document Types also deletes document relationships on standard Document Types with similar names.
|
DEV-365973 |
|
If a job condition references a deleted record, the job and associated audit trail may not update properly.
|
DEV-366315 |
|
The wrong error message is returned when migrating an object package containing blank default values.
|
DEV-366368 |
|
Under certain conditions, users are unable to use the “Allow selection in configuration” flag for an auto-managed group that references outdated data.
|
DEV-366705 |
|
Under certain conditions, some audit data may be missing due to improperly handling null values.
|
DEV-367335 |
|
The Maximum Length field on Formula types of object fields are locked and can only be updated via MDL
|
DEV-369886 |
|
Under certain conditions, Admins cannot download or delete overlay overrides.
|
DEV-370027 |
|
In some cases, Vault Comparision reports fail if the source vault has several workflow definitions with the same Modified Date and one is missing a public key.
|
DEV-370134 |
|
When using Vault Loader to update user records, Vault sometimes fails to add users to groups based on security profile.
|
DEV-371164 |
|
In some cases, Vault Loader fails to extract object records when the Include Non-Editable Fields checkbox is selected.
|
DEV-371223 |
|
The copyright date displayed in the Vault Loader CLI is incorrect.
|
DEV-372191 |
|
When using Vault Compare, errors comparing individual components cause the entire comparison to fail.
|
DEV-372296 |
|
Formatted output reports fail to generate when the template includes a document relationship that references an object.
|
DEV-373447 |
|
Vault creates duplicate folders on the FTP Staging Server.
|
DEV-374134 |
|
Users who are not Vault Owners experience a server error when editing filters on object tabs.
|
DEV-374261 |
|
When Internet Explorer 11 users generate a Vault Comparison or Vault Configuration report, Vault does not apply proper bullet formatting to the resulting notifications.
|
DEV-376768 |
|
When a user loads an invalid mapping file to Vault Loader, Vault displays an Uploading File pop-up with a continuously looping progress bar instead of an error message.
|
DEV-378542 |
|
Users are unable to deploy Inbound Packages containing Object type Tab or Subtab components with multiple Object Type values.
|
DEV-380048 |
|
Deployment fails for inbound packages containing complex join objects with name__v fields where both unique and system_managed_name are set to true.
|
DEV-380859 |
|
Users who do not have Read permission on the Users and Groups objects are unable to open the Vault Loader Extract page.
|
DEV-384172 |
|
When extracting data with Vault Loader, users are able to see and select fields on objects for which they do not have read permission. Vault does not include data for these fields in the resulting extract.
|
DEV-384685 |
|
Deployment fails for rows containing picklist or boolean fields when deploying inbound packages containing data steps.
|
DEV-386277 |
|
When a user’s first or last name is updated through the Vault UI, the new name is not reflected in the Created By and Last Modified By fields of object records.
|
DEV-387438 |
| Description |
Issue No. |
|
In some cases, creating a CrossLink results in a server error.
|
DEV-288670 |
|
In some cases, the Calculate Cycle Times job does not create Cycle Time records as expected.
|
DEV-340188 |
|
Users that don’t have permission to view the Expected Documents tab cannot access the Review Overcount or Review Pending Decisions links from the eTMF Homepage.
|
DEV-344322 |
|
In some cases, CTN Data Change Log records do not contain Study, Study Country, or Study Site values.
|
DEV-349227 |
|
Activating an Agreement may cause performance issues.
|
DEV-353675 |
|
After certain configuration changes to an existing workflow in vaults using Multi-Site Document Distribution, Vault displays an error when attempting to distribute documents to specific sites.
|
DEV-356859 |
|
Inactive values are included in the Milestone Category picklist on Homepages.
|
DEV-357207 |
|
In some cases, the Previous Monitoring Event field on an active Monitoring Event is being populated with an inactive Monitoring Event record.
|
DEV-357870 |
|
The default value of the Active Agreement field on a Site record may be removed when you import a VPK file to update the Site object.
|
DEV-360623 |
|
In some cases, the Last Modified Date on a document audit trail updates in spite of no changes to the Milestone field.
|
DEV-361554 |
|
In some cases, creating a new Product record results in a server error.
|
DEV-362302 |
|
Saving Study Product or Study Person records without a value in the Study Role field results in a server error if EDL creation is triggered on that record.
|
DEV-363832 |
|
In some cases, executing the Generate CTN user action results in an unexpected error.
|
DEV-364245 |
|
In some cases when users select a Study in the Study Selector in the Library before creating a document, Vault populates the document’s Study field with the Study value.
|
DEV-364276 |
|
Users who do not have Trip Report Answer create permissions no longer have the ability to edit Responses and Comments on Trip Report Questions.
|
DEV-364885 |
|
Performing the “Create Protocol Deviation Log” user action on a Site results in a server error
|
DEV-365006 |
|
In some cases, Vault does not create CDX Issues when Configuration Mapping records have invalid field mappings.
|
DEV-365388 |
|
In some cases, copied documents do not retain the Product value.
|
DEV-365474 |
|
In some vaults, attempting to open the Selected Study Organization Role Detail Page Layout results in an error.
|
DEV-366211 |
|
Users cannot enter Trip Report responses for empty Answer Sets with no available Answer records on multiple-choice questions
|
DEV-366444 |
|
Users cannot use the “Create Fees from Template” action without adding “Create” permission on the “Additional Fees” object type.
|
DEV-368858 |
|
In some cases, completion metrics on Milestones with Actual Finish Dates are updated unexpectedly.
|
DEV-369039 |
|
Documents transferred from SiteVault via Veeva Site Connect do not include Product values.
|
DEV-369261 |
|
Error messages on Distribution Tasks do not match the error message on the corresponding CDX Issue records.
|
DEV-374798 |
|
Documents transferred to a target vault via TMF Transferred do not include the audit trail from the source vault.
|
DEV-375454 |
|
Vault does not allow users to save Studies for Study object types that are not associated with the CDX ID field
|
DEV-376639 |
|
When EDLs are configured with custom lifecycles, sending the records to sites via Veeva Site Connect results in an unexpected error.
|
DEV-377159 |
|
In some cases, scheduling multiple Change Milestones to Complete jobs may result in performance issues and delays in job execution.
|
DEV-379165 |
|
After accepting and approving a study Agreement, distribution tasks and document IDs are not logged correctly.
|
DEV-379364 |
|
In certain scenarios, the Create Milestone from Template job fails with the error message “As an Owner of this job, this notification is to inform you that the job was unable to complete its execution (ID: 107024), and ended with a status of: Errors Encountered.”
|
DEV-379584 |
|
Vault does not create Study Sites via Vault Loader if they reference an organization with an invalid USN.
|
DEV-379828 |
|
In some cases, selecting “TMF RM 2.0” from the drop-down menu in the TMF Viewer results in a network issue error message.
|
DEV-380013 |
|
When users add new research sites to a document in a source vault, Veeva Site Connect creates duplicate profile documents rather than upversioning existing documents in the target vault.
|
DEV-380432 |
|
The Update Metrics and Update Monitored Metrics jobs may not be able to recover data upon encountering an error.
|
DEV-380806 |
|
In some cases, the Update Metrics job fails when a study’s Metric Calculation value is Date Based and Subjects have a Screen Failed Date without a Screen Date or a Withdrawn Date without an Enrolled Date.
|
DEV-380826 |
|
The Create Metrics Over Time job fails if there are more than 500 planned rollups for metrics over time.
|
DEV-381427 |
|
When multiple profile documents are transferred to SiteVault via Veeva Site Connect, Vault may not create Distribution Tasks for all relevant records.
|
DEV-381429 |
|
In some cases, TMF Transfer does not transfer placeholder documents.
|
DEV-382001 |
|
In some cases, sending an Agreement to a target vault results in multiple server errors.
|
DEV-382002 |
|
In some scenarios, users receive a “server having problems” error when trying to send a document through Veeva Site Connect.
|
DEV-382391 |
|
Clinical User Tasks with blank Categories are not included in view when users click on the Not Applicable category from the Study Quality widget on the CRA Homepage.
|
DEV-384152 |
|
Users with the Business Admin security profile see a server error when they attempt to execute the Distribute to Sites user action.
|
DEV-385383 |
|
Some users without the Manage Archive permission are able to add a document to an archived study.
|
DEV-387286 |
|
Vault may display a server error when users hover on the Completeness field on Milestone records list pages if the Milestone has no Sum of Actual Total Document Field value.
|
DEV-387507 |
|
When safety letters are transferred to SiteVault vaults via Veeva Site Connect, the related Safety Distribution records do not update from Ready to Distributed state, and Vault does not populate the Initial Distribution Date field.
|
DEV-388034 |
|
In some cases, document transfer fails for Site Connect Renditions.
|
DEV-389963 |
|
In some cases, Vault may not create Distribution Tasks in target vaults for documents transferred via Veeva Site Connect. Related Distribution tasks in the source vault are in the Failed lifecycle state in spite of successful document transfer.
|
DEV-389964 |
| Description |
Issue No. |
|
In some cases, Digital Publishing for Documents fails and URLs are not generated.
|
DEV-336334 |
|
In some cases, the Production CDN URL field remains populated when the document is Retired.
|
DEV-346153 |
|
In some cases, Vault does not display values for production URL tokens in notifications.
|
DEV-346624 |
|
If the latest version of a Multichannel Slide is in Draft state, and the slide is expired, the corresponding record is not withdrawn from the production CLM.
|
DEV-348293 |
|
Vault incorrectly changes the state of a regenerated compliance package.
|
DEV-353780 |
|
When a user attempts to add a document on which they don’t have the Edit Fields permission to a Portal widget, Vault displays a “server having problems” error instead of a more helpful message.
|
DEV-354077 |
|
Vaults using non-standard Material Type fields and picklists do not pull in material type when generating an eCTD compliance package.
|
DEV-362189 |
|
eCTD binder generation fails if there are required filters on the Linked Document relationship type.
|
DEV-366109 |
|
When a user updates an existing cover letter template to the new Medical Inquiry Case Response Cover Letter document type, Vault sometimes incorrectly maps existing custom document fields with similar names to the Related Case Request and Related Case Response fields, and cover letter generation fails.
|
DEV-367288 |
|
When generating an eCTD Compliance Package, Vault does not include the promotional document number and version on Form 2253 or the Supplementary Form.
|
DEV-367291 |
|
Content Filters based on a previously created Saved View from a different portal do not filter or display results correctly.
|
DEV-369417 |
|
Vault fails to generate folders in eCTD Compliance Package binders.
|
DEV-370028 |
|
Users experience an error when triggering the Create Presentation action via the Multichannel Loader.
|
DEV-374796 |
|
When performing a bulk action on documents in a Portal, Vault does not apply filters.
|
DEV-376814 |
|
Standard Metrics fields are updated on the audit trail but are not updated and show as blank in the Standard Metrics section of the document.
|
DEV-379738 |
|
Users encounter a server error when adding a related Portal to a Portal record.
|
DEV-380115 |
|
eCTD document filenames exceed 64 characters in length.
|
DEV-385839 |
| Description |
Issue No. |
|
Vault does not log a “SUCCESS” in the api_response_status column of the API Usage Log after making API calls to retrieve audit trails.
|
DEV-208629 |
|
Using JSON to bulk delete by unique field value for a number containing a decimal place returns an error.
|
DEV-348858 |
|
Some API users are able to assign workflow tasks to inactive or pending users.
|
DEV-351314 |
|
The Update Single Document endpoint does not return a response status if the request fails. This fix only affects API v21.1+.
|
DEV-352915 |
|
Under certain conditions, using the API to update a study object reference field utilizing a VQL constraint may result in unexpected behavior.
|
DEV-355279 |
|
Using the API bulk upsert API may result in unexpected behavior if the CSV payload contains a trailing whitespace fo non-system managed name fields.
|
DEV-356532 |
|
In API v20.2+, the executable__v attribute returned for document/binder lifeycle action APIs sometimes returns as false for executable actions.
|
DEV-357418 |
|
Under certain conditions, some audit data may be missing due to improperly handling null values.
|
DEV-362646 |
|
The wrong error message is returned when using Vault Loader to create a record for an event package.
|
DEV-365223 |
|
If an object has a unique number field, for example, num__c, an UNEXPECTED_ERROR may occur when updating a record using the bulk upsert API.
|
DEV-365895 |
|
Vault does not prevent the creation of object types on objects that do not have object types enabled. Users encounter server errors when attempting to open these objects in Vault.
|
DEV-370702 |
|
When a user retrieves document audit trail metadata, the Retrieve Audit Metadata endpoint returns a version value of “-.-” instead of “0.0” for events attributed to a document but not tied to any particular version.
|
DEV-370903 |
|
When extracting documents with the Extract Data Files endpoint, if a user selects the include_source__v or include_renditions__v extract options, and no documents match the VQL criteria, or if all documents in the vault are placeholders without renditions, the extract fails instead of succeeding and returning an empty CSV.
|
DEV-371163 |
|
When exporting documents with the Vault API’s Extract Data Files endpoint, if a user selects the include_source__v or include_renditions__v extract options and does not include id in the fields array, Vault returns an error and the job fails.
|
DEV-371930 |
|
The “Assign Users & Groups to Roles on Multiple Documents” API (/api/{version}/objects/documents/roles/batch) allows setting more than one user as the document owner.
|
DEV-379658 |
|
The Update Object Records endpoint does not accept integer values for the id parameter when updating user__sys records if the Content-Type is application/json.
|
DEV-382301 |
|
The Job Status endpoint sometimes returns a status of “PROCESSING” for Vault File Manager jobs which have already completed successfully.
|
DEV-382575 |
|
Upserting object records through the API sometimes results in an METHOD_NOT_SUPPORTED error.
|
DEV-384881 |
|
When creating user_role__sys records in bulk through the API, if the first item in the request body fails for permission checking reasons, the rest of the request will also fail.
|
DEV-386399 |
|
When a user attempts to Create Multiple Document Versions through the API, in some scenarios the CSV response identifies an error but no error message appears in the response.
|
DEV-386690 |
|
API header responses include an unexpected “Set-Cookie” header.
|
DEV-390790 |
| Description |
Issue No. |
|
After deleting a Viewable Rendition, some Linked Document relationships may remain in use.
|
DEV-178457 |
|
When a user checks in a document via Office Online, Vault does not accurately capture changes in file size.
|
DEV-277386 |
|
Inline text attachments are missing as Vault attachments from .MSG files.
|
DEV-325528 |
|
In some cases, Vault does not display annotations when sorting by author.
|
DEV-328882 |
|
In some cases, Vault displays incorrect field dependency rules.
|
DEV-330415 |
|
The document viewer and viewable rendition differ and display content from different versions of the source document.
|
DEV-330492 |
|
In some cases, Microsoft Word™ documents fail to render.
|
DEV-341002 |
|
In some scenarios, merge fields resolve as blank (tokens do not resolve).
|
DEV-346729 |
|
In some cases, a page with a list of font names is added to rendered documents.
|
DEV-346939 |
|
In some cases, Microsoft Word™ documents in Compatibility Mode fail to render.
|
DEV-349659 |
|
Documents with Read-Only protection fail to render.
|
DEV-351423 |
|
Under certain conditions, the hierarchical document type picker may display document types, subtypes, or classifications to which the current users do not not have create permissions, resulting in an error upon saving.
|
DEV-351694 |
|
In some cases, the internal structure of renditions includes an extra line preceding the end of file marker in the file trailer.
|
DEV-352405 |
|
Documents fail to render if a user uploads a DOTX file as a new version and attempts to merge fields.
|
DEV-352584 |
|
Under certain conditions, documents may take an inordinate amount of time to load in searches.
|
DEV-353161 |
|
Under certain conditions when creating a binder, users are unable to edit the binder structure due to an unresponsive UI.
|
DEV-353521 |
|
The error message when attempting to delete a document from an archived binder does not contain a reason.
|
DEV-353820 |
|
In some cases, Microsoft Word™ documents with SEQ fields fail to render.
|
DEV-353885 |
|
When adding references to Claim records, users experience an error when selecting anchors with titles that are 135 characters or longer.
|
DEV-354399 |
|
In some cases, bringing forward the same annotation multiple times may result in lost tag values on annotations.
|
DEV-360256 |
|
Vault incorrectly allows the Archive Document and Unarchive Document actions on prior document versions.
|
DEV-361507 |
|
For documents created by bulk API import with unexpected date formatting, for example, 2020-12-4 instead of 2020-12-04, when a user edits another document field, Vault creates an audit trail entry showing an update to the date field where the old and new values are the same.
|
DEV-361856 |
|
In some cases, after rendering a Microsoft Excel™ document, Vault displays text in empty table cells.
|
DEV-362037 |
|
Vault may display an error when attempting to bring forward annotations for documents with certain font configurations.
|
DEV-362521 |
|
Removing the Document Version value from a Claim Reference results in an error.
|
DEV-362668 |
|
Documents do not appear in the Document Change Control “Documents to Be Released” section several days after being added.
|
DEV-362683 |
|
The second time a user brings forward an annotation and selects “Do not bring forward page-level annotations”, Vault does not bring forward the replies.
|
DEV-362953 |
|
After adding a rendition through bulk API to a document with an existing rendition, the Audit Trail incorrectly states that a viewable rendition was successfully added.
|
DEV-364633 |
|
When users Download Notes to export annotations, the Subtype field in the CSV file is blank for sticky note annotations.
|
DEV-365511 |
|
After creating a placeholder and adding content, the size attribute is missing from the Audit Trail.
|
DEV-366779 |
|
In some cases, Vault generates zero byte files when downloading a PDF with annotations
|
DEV-367323 |
|
Documents fail to render if the source document contains invalid merge field content.
|
DEV-368345 |
|
Internet Explorer users experience incorrect cursor focus when adding text annotations to a document.
|
DEV-368745 |
|
In some cases, Vault incorrectly renders citations as bookmarks.
|
DEV-370039 |
|
In some cases, merge fields that are unavailable on the active document type display an error instead of leaving the token blank.
|
DEV-370235 |
|
Attempting to upversion a document results in a server error if the document has target version-specific document relationships with archived documents.
|
DEV-370249 |
|
Collaborative Authoring does not work as expected after a prolonged period of disuse.
|
DEV-371274 |
|
Vault fails to create and render CrossLinks for large documents.
|
DEV-371684 |
|
After updating documents using Vault Loader, Vault does not update the Timeliness document field.
|
DEV-371926 |
|
Empty Microsoft Excel™ worksheets fail to render.
|
DEV-373986 |
|
In some cases, fields do not populate with default values during document classification if DAC is configured on the document.
|
DEV-374453 |
|
In certain circumstances, more than one version of a document may be returned by Vault search as the latest version.
|
DEV-374550 |
|
In some cases, Vault does not render Microsoft Word™ documents with tracked changes enabled as expected.
|
DEV-374785 |
|
In some cases, tokens in letter templates are not populated.
|
DEV-375767 |
|
In some cases, the Where Used view displays the incorrect document count and pagination when the document is associated with archived documents.
|
DEV-376623 |
|
Users may see a previously deleted rendition in the document viewer if the user uploaded renditions manually and the rendition is a protected PDF.
|
DEV-376631 |
|
Bookmarks in Microsoft Word™ documents navigate to the wrong place after rendering.
|
DEV-377366 |
|
When a user without the correct permissions attempts to re-render an annotated document and does not select “Preserve my annotations”, Vault displays an error but deletes the relationships.
|
DEV-378017 |
|
Checking documents in or out may result in performance issues.
|
DEV-378474 |
|
In some cases, Vault does not display images in renditions when images are embedded in Microsoft Word™ documents.
|
DEV-379849 |
|
The filename extension of PDF documents is case sensitive, which prevents PDF files from being displayed in the document viewer if the extension is not exactly “.pdf”.
|
DEV-380224 |
|
When a user navigates to document using a URL containing a version number that does not exist, Vault generates a duplicate “View document” event in the audit trail.
|
DEV-380249 |
|
Microsoft Excel™ worksheets without a header or footer are incorrectly rendered.
|
DEV-380716 |
|
In some cases, Vault fails to render Thai language characters.
|
DEV-380804 |
|
In some cases, there is a delay when adding a new section to very large binders.
|
DEV-381412 |
|
When a user attempts to open a Linked Documents section that contains over 1000 document relationships, a network issue occurs.
|
DEV-382240 |
|
Vault fails to render video files with long duration times.
|
DEV-382482 |
|
In some cases, the “File doesn’t exist in remote but exists in local” error dialog shows the file paths of the file involved.
|
DEV-383214 |
|
After an .RTF file fails to render, Vault displays an “unsupported file type” error message and does not allow the user to re-render.
|
DEV-384095 |
|
Users are unable to upload a viewable rendition of password-protected PDF documents.
|
DEV-384582 |
|
When uploading a rendition, the Upload Rendition progress dialog is missing the header.
|
DEV-384621 |
|
When a user moves an annotation, the annotation becomes unselected and remains unselected when the user clicks it.
|
DEV-385362 |
|
In cases where integrations update binders using the “Overwrite existing bindings if a newer version is available” option, Vault records the update even if nothing has changed.
|
DEV-385380 |
|
Users are unable to upload a video file that is 3 GB or larger using the drag-and-drop action.
|
DEV-386820 |
|
When downloading very large files from Vault, there is a long delay before the download begins.
|
DEV-389411 |
|
In the Select Targets dialog, if a user unselects certain nested targets using the mini-browser, the list under the target document will render incorrectly.
|
DEV-389731 |
|
The Select Targets dialog incorrectly displays long document names that do not contain whitespace.
|
|
| Description |
Issue No. |
|
Initiating workflows has decreased performance.
|
DEV-361728 |
|
In certain cases, the participant selection dialog box may not allow the user to continue when there are ineligible participants selected.
|
DEV-362565 |
|
Vault may display an error when attempting to change a Content Plan object record to a Locked lifecycle state.
|
DEV-364107 |
|
In vaults with the “Atomic Security for Documents: Active Workflow Actions” feature enabled, Workflow Initiators do not have automatic access to actions for active workflows, such as Cancel Workflow or Reassign Task. Workflow Initiators need to have the correct security profile to access these actions, including the Update Due Date action introduced in 20R3 for multi-document workflows.
|
DEV-364187 |
|
In certain cases, the timeline view may not display the most recent effective version of a document if there was a state change by the Change State of Related Documents entry action, or triggered due to removal of documents in a multi-document workflow.
|
DEV-366073 |
|
Vault users’ ability to use a bulk state change action may incorrectly be blocked by the Start Workflow permission.
|
DEV-367522 |
|
After an auto-start workflow is initiated, the task bar loads slowly.
|
DEV-370986 |
|
In some cases, users receive a server error when attempting to “Add Participant” on an active object workflow.
|
DEV-371769 |
|
In some cases, a user may see multiple instances of the same active workflow.
|
DEV-371943 |
|
The error message displayed upon failing to meet entry criteria for a lifecycle state may incorrectly show the state key value instead of the state label.
|
DEV-372062 |
|
In some legacy workflows, when a user executes the Update Workflow Dates action on a workflow task with multiple participants, the workflow task participants continue to receive notifications that the task due date has been updated.
|
DEV-373480 |
|
In certain multi-document workflow configurations, after creating an optional workflow task via Add Participants, the optional workflow may be unexpectedly completed upon completion of a parallel required task.
|
DEV-374039 |
|
If permissions are updated between adding a document to the Cart and starting a multi-document workflow, a user may potentially start a multi-document workflow for documents they cannot view.
|
DEV-375208 |
|
Vault may display a server error when trying to delete a custom object with Atomic Security configured for a field in the object’s lifecycle.
|
DEV-376007 |
|
Vault may display a server error when a record state change triggers a related document state change with failing entry criteria.
|
DEV-378708 |
|
In certain cases, participants added to a workflow with the Add Participants function may not properly receive the workflow task.
|
DEV-380069 |
|
Certain verdict configurations in multi-document workflows may result in unexpected verdicts.
|
DEV-380491 |
|
Vault may not correctly send a notification to the user in the role configured in a Notification step of a multi-document workflow when this step occurs after a State Change step triggering the Set new major version entry action.
|
DEV-387906 |
|
When a lifecycle state contains the same user action more than once, the state’s Atomic Security page may not load properly.
|
DEV-390756 |
|
When some lifecycles have duplicate names and identical states, Vault is unable to generate Atomic Security for user actions in those states.
|
DEV-391335 |
| Description |
Issue No. |
|
Adding a long-text field to a high-volume object may fail due to improper indexing.
|
DEV-346203 |
|
When setting an object type-specific field default, Vault sets the default field value for inactive fields.
|
DEV-353908 |
|
In scenarios where unique values do not make sense, selecting the “Values must be unique” option on an HVO object’s document reference field causes a server error. Instead, the error should tell the user why this option does not make sense.
|
DEV-357102 |
|
In some cases, attempting to create a Deep Copy of a secured parent object record causes an unexpected error.
|
DEV-364684 |
|
In some cases, a Content Plan may incorrectly show that an EDL Item is still in progress after it has completed.
|
DEV-367481 |
|
In some cases, EDL Item continuous matching is not triggered when a document is updated.
|
DEV-368552 |
|
In some cases, users cannot save a field value which contains an apostrophe.
|
DEV-371408 |
|
Vault does not populate values for some Lookup fields on object record detail pages.
|
DEV-382396 |
|
Users may require Read access on object fields in order to edit user profile fields that are configured as editable in the profile layout configuration.
|
DEV-384333 |
|
When deploying a migration package, deleting a field used in a default value expression via MDL and then viewing the Object Types tab results in a server error.
|
DEV-386256 |
|
Under certain circumstances, when users encounter an “SDK_ERROR:OPERATION_FAILED” error when querying a high volume object record, the error message suggests their changes will be reverted but the changes are committed instead.
|
DEV-387515 |
|
If the first field a user edits on their user profile is a text field, long-text field, or rich-text field, the Save button does not become enabled until the edited field loses focus.
|
DEV-389037 |
|
When a user attempts to edit a controlled object reference field in bulk, it remains disabled even if the user edits all controlling fields.
|
DEV-389100 |
| Description |
Issue No. |
|
In some scenarios, the hover tooltip text for Auto Managed Groups appears in the top-left of the page.
|
DEV-274380 |
|
Automated Image Rendition Density is defined in pixels per cm, rather than pixels per inch.
|
DEV-300499 |
|
Under certain conditions, Related Object and Document sections may take an inordinate amount of time to expand.
|
DEV-341914 |
|
Accessing a Safety case record may take longer than expected because the initial load includes data from collapsed sections.
|
DEV-347010 |
|
Expanding or collapsing a related object section has decreased performance.
|
DEV-347552 |
|
Under certain conditions, users are unable to start a workflow action.
|
DEV-351813 |
|
Some vaults may experience slowness or data errors for PDF and InDesign renditions due to a configuration error.
|
DEV-353348 |
|
Pressing the Page Down key on the document viewer may cause the page to continuously scroll up and down.
|
DEV-356399 |
|
In some cases, hovering over a group label may display an incorrect count of members.
|
DEV-357563 |
|
When a user receives the error “Another record has the same value” when editing a picklist, the error message is displayed twice.
|
DEV-360296 |
|
In some cases, inline editing a cell on an object record page may freeze the page, making other actions impossible
|
DEV-360594 |
|
In some cases, Vault errors when attempting to display a user group with a very large number of members (3,000+ members).
|
DEV-362855 |
|
Custom object notifications sometimes have missing values for tokens for some users
|
DEV-365458 |
|
The “Back to previous page” link does not work as expected.
|
DEV-365921 |
|
In some cases, the My Vaults page fails to load.
|
DEV-368760 |
|
When viewing all records for a custom object, extremely large numbers of records (1.5 million+) may take a very long time to display or timeout without displaying.
|
DEV-370585 |
|
In some cases, Vault does not track the Avg Time Login performance statistic.
|
DEV-371091 |
|
Notifications for Vault Loader jobs are missing bullets when viewed in Internet Explorer 11.
|
DEV-371996 |
|
Updating relationships related to a document version during a state change may have slow performance when there are many relationships.
|
DEV-376014 |
|
When used in notification templates, Rich Text field values display as plaintext, including HTML tags. In 21R1.0, Rich Text fields will still display as plaintext, but without any HTML markup.
|
DEV-378613 |
|
Fonts and icons are larger in size on some Admin pages.
|
DEV-387099 |
|
In some scenarios, Long Text fields do not display hovercards.
|
DEV-386598 |
|
If a report contains duplicate prompts and a user attempts to run the report from a dashboard, Vault displays a “Server having problems” error.
|
DEV-389030 |
|
On the user details page, section help icons (?) are mispositioned.
|
DEV-389231 |
| Description |
Issue No. |
|
E-learning files may not play in the Safari browser without the ‘Prevent cross-site tracking.’ setting disabled.
|
DEV-315852 |
|
In certain cases, Vault displays a server error instead of a detailed error message when a user attempts to view a Training Assignment without the necessary permissions.
|
DEV-348519 |
|
In some cases, moving documents associated with a Training Assignment to Steady state does not issue Training Assignments as expected.
|
DEV-352857 |
|
In some cases, the Sibling Check Related Record State Change entry action may trigger unexpectedly if there are large numbers of related records.
|
DEV-354626 |
|
Vault cannot launch e-learning content in Internet Explorer 11 browsers.
|
DEV-365048 |
|
Document icons may not correctly appear in related document sections on Training Assignment or Training Requirement Impact Assessment object record details pages.
|
DEV-366755 |
|
In certain Substitute Training configurations, a substitute training assignment which should be canceled may not be correctly canceled by the nightly Update Training Assignments job.
|
DEV-368030 |
|
Admins can assign the Learner license type to users in vaults where Vault Training is not enabled
|
DEV-368735 |
|
In some cases, the Learner Homepage may fail to completely load.
|
DEV-369388 |
|
In Vault Training, the entry action for Training Assignment records sometimes does not copy all fields.
|
DEV-371201 |
|
Users are unable to open Facilitated Training Request records if they contain formula icon fields
|
DEV-374990 |
|
In certain cases, Vault may not correctly close a Document Change Control when it enters a state with the Check and Close Multi-Document Change Control entry action configured. This primarily occurs when a document is added to the Documents to be Made Obsolete section of a Document Change Control and a new version of a document is created and then deleted prior to the entry action executing.
|
DEV-375591 |
|
In Vaults using the Preview E-Learning Content user action, Vault comparisons may report an unexpected discrepancy due to XML values which differ between individual vaults.
|
DEV-378874 |
|
Some SCORM 2004 e-learning content does not play as expected with the Preview E-Learning Content action.
|
DEV-379257 |
|
In Vault Training, E-learning videos do not play on iOS (iPad, iPhone).
|
DEV-381236 |
|
In vaults using the Audit Program Planning feature, Vault may not correctly populate the Quality Team for additional Audit records after the first created from a Proposed Audit record.
|
DEV-382251 |
|
In circumstances where multiple Training Assignments have been created from a Training Requirement, removal of that Training Requirement from the relevant Curriculum may not correctly cancel all of the affected Training Assignments.
|
DEV-384792 |
|
The self-registration page for classroom training may not correctly sort available classes by date.
|
DEV-385462 |
|
In vaults using Prerequisite Training, under certain circumstances, a Training Assignment may not appear as expected in the Add to Class Roster dialog.
|
DEV-385546 |
|
The “incomplete team” warning icon in a Quality Team section may be misaligned.
|
DEV-386185 |
|
When Admins attempt to save changes to custom user actions in the TA Checklist object lifecycle’s Passed state, Vault displays an error dialog and fails to save the changes.
|
DEV-387178 |
| Description |
Issue No. |
|
Vault incorrectly reports link and bookmark PDF rules for older published documents rather than the most recent published document.
|
DEV-254217 |
|
In some cases, Vault reports PDF rules after continuous validation jobs even if there is no matched document.
|
DEV-257929 |
|
Vault doesn’t update tracking fields when a user removes a matched document from an inactive Content Plan Item record in the Hierarchy Viewer.
|
DEV-301515 |
|
For EU submissions, the 1.3.1 section of Module 1 does not display correctly in the published binder.
|
DEV-331229 |
|
During the Create Content Plan, Update Content Plan, Split Content Plan, and Update Token actions, Vault fails to replace some periods with hyphens.
|
DEV-339782 |
|
Vault does not publish some Vault links when users match source documents to content plan items that are initially publishing the submission.
|
DEV-341238 |
|
Users experience slow performance after running the Create Related Records wizard when constraints are configured on join objects.
|
DEV-345236 |
|
If a source document is matched in separate submission content plans for different regions, continuous publishing does not always publish links if the link target exists is only one of the submissions.
|
DEV-348656 |
|
Vault performance is slow when creating or updating many records from the Manage Registered Details wizard.
|
DEV-350357 |
|
After users unlock a previously locked matched document, continuous publishing does not publish links in the latest document version.
|
DEV-350527 |
|
After applying an advanced filter in the Submissions Archive Viewer, when users open a document, Vault navigates them to the Notifications page.
|
DEV-351995 |
|
Applying column filters for some field types in the Content Plan Hierarchy Viewer results in a Vault error.
|
DEV-353561 |
|
In some cases, Vault cannot render or re-rend the Index XML file properly.
|
DEV-355621 |
|
When updating registration fields in the Manage Registered Details wizard, users cannot update custom document reference fields.
|
DEV-358348 |
|
In some cases, the removal of manually matched documents fail and result in an error while the daily automatching job is running.
|
DEV-358364 |
|
In the Gateway Submission dialog, Vault includes Correspondence documents in the count of files being submitted.
|
DEV-358375 |
|
Vault does not resolve permalinks correctly after published documents have been merged.
|
DEV-359651 |
|
After users delete a Content Plan section or Content Plan Item and continuous publishing runs, Vault fails to delete the related Submission Validation Result records.
|
DEV-359731 |
|
When Submission Contact join records only have the Full Name field populated, the Submission Publishing job fails and Vault creates the binder with placeholders for the XML files.
|
DEV-361165 |
|
Users can import submissions via the API using incorrect folder paths.
|
DEV-361515 |
|
After submitting XEVMPD data to the EMA, Vault does not receive acknowledgment responses.
|
DEV-362199 |
|
Create from Document jobs in RIM vaults do not complete as expected.
|
DEV-362362 |
|
Validation rule CA F09 fails for some sequence descriptions.
|
DEV-362498 |
|
In RIM Submissions or RIM Submissions Archive vaults that had the RIM Registrations application added later, the Registration Data Verification workflow is missing.
|
DEV-363293 |
|
When users run the Create Related Records wizard, Vault sometimes names newly-created Regulatory Objective records incorrectly.
|
DEV-363297 |
|
In some cases, submission removals fail.
|
DEV-364623 |
|
Vault does not populate Archive Sections correctly when concurrent submission imports occur.
|
DEV-365740 |
|
In some cases, submission files don’t appear in the Submissions Archive Viewer after import.
|
DEV-365931 |
|
When replicating Content Plan sections, Vault does not propagate blank values on join records.
|
DEV-366346 |
|
In some cases, Sequence IDs with hyphens causes continuous publishing to fail.
|
DEV-367255 |
|
Vault sometimes handles missing nodes improperly when determining the content plan hierarchy path.
|
DEV-367309 |
|
Users sometimes see a server error when attempting to import a submission ZIP file.
|
DEV-368111 |
|
When validating the US Form filename as part of US 5029, Vault expects no characters to exist before the form number.
|
DEV-368618 |
|
While generating Product Data Messages, Vault fails to load an XML attachment and message number if the Product Report Item’s Language Code field is blank, causing the XEVMPD submission to fail.
|
DEV-369059 |
|
The Manage Registered Details wizard does not allow the addition of new Registered Product records that contain a comparator product to an Investigational Product registration that has a different non-comparator product.
|
DEV-369419 |
|
Permalinks to Submissions Archive content are not resolved if the published version is deleted.
|
DEV-370910 |
|
When Dossier Formats are defined, Vault does not load STF files to the correct folders during submission import, and users see warnings in the import notification.
|
DEV-371068 |
|
An error occurs when users export the Excel Tree with All Descendants from a content plan that contains placeholder documents after adding the Matched Document Size column in the Content Plan Hierarchy Viewer.
|
DEV-372121 |
|
Users cannot add a Unit of Presentation into a denominator when working with XEVMPD data.
|
DEV-374164 |
|
Some submissions imported through Vault File Manager get stuck in the TRANSFER_INITIATED status.
|
DEV-374543 |
|
The audit trail does not include an entry for the user who initiates a submission import via Vault File Manager.
|
DEV-374784 |
|
After an Admin disables the Show Correspondence in Viewer setting, correspondence folders still appear in the Submissions Archive Viewer and when users export the submission.
|
DEV-375418 |
|
Users can proceed in and complete the Create Related Records wizard without populating required fields, even though Vault cannot create the new records.
|
DEV-376644 |
|
When a matched document contains a link targeting another matched document, continuous publishing does not up-version the source document when the document containing the link target moves from inactive to active.
|
DEV-377931 |
|
An extra Actions menu appears on the right side of the screen when users hover over module sections in the Submissions Archive Viewer.
|
DEV-378258 |
|
In some cases, publishing jobs take longer than expected to complete.
|
DEV-379033 |
|
In some cases, users see unexpected leaf node warnings in the submission import notification, and some documents don’t appear correctly in the Submissions Archive Viewer.
|
DEV-379716 |
|
The EMA rejects XEVMPD messages that contain the GB country code due to Brexit.
|
DEV-379815 |
|
Enabling the Enable Submission based Viewer Filters setting on the Application Settings page does not remove values from the object reference fields used for submission metadata mapping.
|
DEV-379975 |
|
Errors occur on submission imports when an Admin enables the Show Correspondence in Viewer setting but doesn’t select a Document Type.
|
DEV-380364 |
|
When the XML Operation is set to Delete on a link target document, Vault publishes the target document as a placeholder but does not remove the link on the source document.
|
DEV-380746 |
|
The Registration Wizard Job In Progress notification template is missing from some vaults.
|
DEV-381039 |
|
In some cases, the Merge PDF action fails, and Vault publishes all files separately rather than creating a single merged PDF.
|
DEV-381115 |
|
During continuous publishing, Vault does not report Rule US5200 correctly.
|
DEV-381961 |
|
The Truncate Cell Text and Wrap Cell Text options do not work correctly in the Content Plan Hierarchy Viewer.
|
DEV-385166 |
|
The “RMS Integration and Synchronization” job title does not appear on the Job Definitions page.
|
DEV-385467 |
|
Users cannot filter on the Notes field on the Content Plan or Content Plan Item objects in the Content Plan Hierarchy Viewer.
|
DEV-385476 |
|
Vault incorrectly replaced periods within tokens, causing the tokens to no longer be valid when running the Update Tokens in Field action.
|
DEV-385916 |
|
The Manage Registered Details wizard does not launch the registration verification workflow or capture changes in the Unverified Data object if document fields are required on the registration details or registered details.
|
DEV-391403 |
|
The user running a Configurable Impact Assessment Report is added to the report copy as a Viewer instead of as an Editor.
|
DEV-390890 |
| Description |
Issue No. |
|
Fixed an issue that resulted in the E2B R3 export - wrong Case Identifier element # in comments.
|
SAF-5061 |
|
Fixed an issue where the ACK 2 record was not created when the record was received at the same time as an ACK 1 record.
|
SAF-10286 |
|
Fixed an issue where a decrease in system performance would occur during Assign Due Date on the Case lifecycle.
|
SAF-11086 |
|
Fixed an issue that would prevent users from creating a picklist custom entry with a name that already exists.
|
SAF-11309 |
|
Fixed an issue where the system contained a validation criteria (ICH.F.r.3.2-3) that could not be verified since the nullflavor field did not exist for Test Result (value / qualifier). This validation criteria has been removed.
|
SAF-11528 |
|
Fixed an issue where the Audit Trail did not record the number of results returned by duplicate detection.
|
SAF-11957 |
|
Fixed an issue where the Create AER from Document Action would be displayed before the document rendition was completed.
|
SAF-12004 |
|
Fixed an issue where an error would occur when creating an AER from an imported E2B file.
|
SAF-12826 |
|
Fixed an issue where a duplicate CIOMS document was created when the Generate CIOMS Preview action was performed.
|
SAF-13016 |
|
Fixed an issue where users could not generate transmission documents on Promotion-type Transmissions.
|
SAF-13232 |
|
Fixed an issue with E2B validation where the Validation Result Summary did not list vault fields evaluated with the ICH.D.10.3-3 and ICH.D.10.8.r.5-3 validation rules.
|
SAF-13421 |
|
Fixed an issue with E2B validation where the Validation Result Summary did not list IDs for records evaluated with the ICH.G.k.4.r.1a validation rule.
|
SAF-13424 |
|
Fixed an issue where gateway transmissions with validation errors became stuck in the Sending ICSR state.
|
SAF-13432 |
|
Fixed an issue where the ICH.F.r.4/5 E2B validation rule did not allow decimal numbers.
|
SAF-13435 |
|
Fixed an issue that resulted in the FDA3500 Date of Onset being Blank instead of "**-***-****" when If AE.Event Onset was Masked.
|
SAF-13456 |
|
Fixed an issue where the MedDRA browser version was using the active version in Business Admin instead of using the Case MedDRA Version for Case Drug History and Case Diagnoses records.
|
SAF-13462 |
|
Fixed an issue where the ICH.D.2.1-2 E2B validation rule failed for Date of Birth referring to a future date when the Case Date of Birth field was not set to a future date.
|
SAF-13463 |
|
Fixed an issue where the ICH.E.i.5-2 E2B validation rule failed for a valid Case Adverse Event Cessation Date.
|
SAF-13478 |
|
Fixed an issue that would result in a date validation error on other sections not being removed after removing DoD.
|
SAF-13482 |
|
Fixed an issue where the medical review timeline was not loading.
|
SAF-13507 |
|
Fixed an issue where duplicate dosages were created when a follow-up is created from a Case with Blinded Study Arms.
|
SAF-13600 |
|
Fixed an error that would occur while creating follow up from a Case with study arms, where Snapshotting is set to When case is opened.
|
SAF-13601 |
|
Fixed an issue where Optimistic Lock errors were included on the Customer Email Statistics log.
|
SAF-13719 |
|
Fixed an issue where an error would prevent a FDA VAERS R3 file from being generated.
|
SAF-13855 |
|
Fixed an issue where the Medical History, Race, and Ethnicity fields on a case were not exported to a submitted report with Vaccine information included.
|
SAF-13909 |
|
Fixed an issue where transmissions with the Auto-submit feature enabled would transition to the Ready state when validation errors were present.
|
SAF-13925 |
|
Fixed an (FDA VAERS scenario 3) issue where, if the Patient Initials/ID field was blank for a malfunction case with a patient, then E2B file generation fails without notifying the user.
|
SAF-13926 |
|
Fixed an issue where a Case may be rejected by VAERS when the Case contained a Malfunction without an Adverse Event, or Patient Info, and the Drug Role was set to "Drug Not Administered."
|
SAF-13931 |
|
Fixed an issue where, when the AI service is skipped (skip_api = true) to create an inbox item via API, the Type field on Product and Event records from structured data were not being autopopulated.
|
SAF-13996 |
|
Fixed an issue that resulted in the ICH: Validation Summary Downloaded CSV converting text to characters.
|
SAF-14019 |
|
Fixed an issue that resulted in a conflict snippet not being crossed out after a user deletes > undo record.
|
SAF-14116 |
|
Fixed an issue with all malfunction, no patient FDA VAERS scenarios, where VAERS E2B R3 files contained Middle name and street line 2 data. These fields will now be set to None in these scenarios.
|
SAF-14213 |
|
Fixed an issue where a Duplicate Key error could occur when promoting an AER to a Case.
|
SAF-14225 |
|
Fixed an issue with E2B (R3) exports where a blank autopsy section (D.9.3) was included when there was no death, causing submissions to the EMA Gateway to be rejected.
|
SAF-14235 |
|
Fixed an issue where the E2B Import would not proceed and would not display an error message.
|
SAF-14306 |
|
Fixed an issue that resulted in, Non-Clinical Trial EMA Submissions destination defaulting to EVCTM.
|
SAF-14310 |
|
Fixed an issue where the destination for non-clinical-trial EMA Submissions defaulted to EVCTM
|
SAF-14310 |
|
Submissions are generated when the Case Product Drug Role is set to Concomitant or Drug Not Administered.
|
SAF-14314 |
|
Fixed an issue where a system error would occur when adding an External Product to a Case while in the Medical Review lifecycle state.
|
SAF-14337 |
|
Fixed an issue during automated intake where an Inbox Item was not created if Case Contact information was extracted from unstructured data.
|
SAF-14365 |
|
Fixed an E2B import issue where certain FDA VAERS units of measurement could not be mapped to a valid UCUM code and fields were instead being mapped to free text.
|
SAF-14377 |
|
Fixed an (FDA VAERS scenario 6) issue where the blinded section in generated VAERS E2B R3 files caused XSD validation to fail.
|
SAF-14385 |
|
Fixed an issue where an error appeared when evaluating reporting obligations for a Case with registrations to an inactive agency without submission rules configured.
|
SAF-14396 & SAF-14639 |
|
Fixed an issue that resulted in the Case contact subheadline not updating to 'Reporter'.
|
SAF-14402 |
|
Fixed an (FDA VAERS scenario 6) issue where CBER VAERS E2B transmissions were rejected for missing medical history even when the file contained medical history.
|
SAF-14444 |
|
Fixed an issue that resulted in a Vault Field being empty for FDA.D.1j.
|
SAF-14459 |
|
Fixed an (FDA VAERS scenario 9/10) issue where you could not create Study Products of the type Combination Product.
|
SAF-14460 |
|
Fixed an (FDA VAERS scenario 10) issue where you could not create Study Products of the type Combination Product.
|
SAF-14476 |
|
Fixed an issue where potential matches were not ordered by matching score during duplicate detection.
|
SAF-14528 |
|
Fixed an issue by updating the hovercard for meddra control to state "Parent MedDRA Version" instead of Case Meddra Version.
|
SAF-14633 |
|
Fixed an issue where the E2B ACK warning is unexpectedly displayed when an EMA submission is submitted to gateway.
|
SAF-14651 |
|
Fixed an issue where an SDK error could occur when validating a Case with the Evaluate Regulatory Conformance action.
|
SAF-14703 |
|
Fixed an issue where, if a Safety.AI vault received an Inbox Item from the API with a time specified in the Receipt Date structured data (JSON), users could not verify the Details section on the Inbox Item.
|
SAF-15082 |
|
Fixed an issue where the Gestation value would appear as "Null" on a potential match when the Gestation field has no value.
|
SAF-15143 |
|
Fixed an issue where the "Unit" placeholder text was missing on certain unit measure fields.
|
SAF-15151 |
|
Fixed an issue where the Receipt Date is not applied to the New Info Date on the Inbox Item upon Case Promotion.
|
SAF-15278 |
|
Fixed an issue causing a server error to appear when accessing a Case Product.
|
SAF-15400 & SAF-16919 |
|
Fixed an issue where, after editing the Inbox Item Reciept Date and Report Type (for the first time) and refreshing the page, the changes are not saved.
|
SAF-15418 |
|
Fixed an issue that resulted in an error which made users unable to Process EMA R3 Date.
|
SAF-15570 |
|
Fixed an issue where the system sent ACK responses in E2B R3 format, regardless of the format of the received E2B file.
|
SAF-15651 |
|
Fixed an issue where product indications were not being imported and duplicate Case Products were being created.
|
SAF-15685 |
|
Fixed an issue where the MedDRA coded term was not being cleared when the reporter term value was cleared.
|
SAF-15691 |
|
Fixed an issue where, when both an active and inactive Transmission Profile exist for the same reporting destination, the system incorrectly matched Cases with the inactive Transmission Profile, causing validation errors.
|
SAF-15841 |
|
Fixed a UI issue by adjusting confidence Icon size UI issues on IE.
|
SAF-15858 |
|
Fixed an issue where empty Case Product Dosage records were being added after opening a Case with Study Arms.
|
SAF-15867 |
|
Fixed an issue where Dose units and Parent Route of Admin were not being mapped during E2B R2 import when the leading 0's were missing from those data elements in the E2B file.
|
SAF-15905 & SAF-16183 |
|
Fixed an issue where a server error appeared when saving a Case Product after deleting a Dosage and the Case Product, and then undoing the delete of the Case Product.
|
SAF-15929 |
|
Fixed an issue where the regulatory conformance of a follow-up Case could not be evaluated, resulting in an error.
|
SAF-16023 |
|
Fixed an issue where regulatory conformance rules would not validate a Case with the country code XI (Northern Ireland).
|
SAF-16031 |
|
Fixed an issue where Facility Type validation failed for a valid selection.
|
SAF-16132 |
|
Fixed an issue that resulted in the terms from the new MedDRA version 24.0 not showing up on a search result.
|
SAF-16194 |
|
Fixed an issue where the PBRER Summary Tabulation was counting Case Adverse Events multiple times when there were multiple Case Products with multiple Case Assessments.
|
SAF-16342 |
|
Fixed an issue where E2B import through either the Receive E2B API or AS2 Gateway failed if the file name was greater than 96 characters.
|
SAF-16402 |
|
Fixed an issue where Product (Coded) was not being snapshot to Study Arm Case Products unless the Product Registration was removed.
|
SAF-16445 & SAF-15869 |
|
Fixed an issue where E2B imports could not complete successfully for ICSRs with chunk encoding.
|
SAF-16735 |
|
Fixed an issue where certain EMA units of measurement codes were not mapped in Vault Safety.
|
SAF-16992 |
|
Fixed an issue with submissions to FDA CBER/CDER gateway, where if a Case had multiple attachments, a single attachment was sent multiple times instead of sending each attachment.
|
SAF-17144 |
|
Fixed an issue where case_number_v.name_v could be set to a custom configuration that prevented generation of Case Assessments due to record names exceeding the maximum character limit.
|
SAF-17287 |