Unearthing Salesforce Platform Capabilities

If you are on Trackwise Digital [TWD] Platform Summer 23 or highier and come across an error ' E-Signature doesn't work ' for username / password with OAuth connected app . Check the Login History of the user and confirm you see the error ' Username-Password Flow Disabled ' . If this happens then you need to enbale the ' OAuth Username-Password Flows ' which will be disabled by default for Summer 23 platform or highier . Steps to enable : 1. Setup ==> search ==> OAuth and OpenID Connect Settings 2. Enable - Allow OAuth Username-Password Flows Reference https://lnkd.in/giVuzGbs

When your org fulfilment is completed by salesforce through honeywell sparta systems, its time for you to perform TrackWise Digital (TWD) platform package installation in your sandbox org . Before you install other TWD packages, its mandatory you need to install TWD platform packages. During TWD platform package installation, you can receive failed package notification error via email sent to your mailbox. The error would be as shown in screenshot. Error : Dependent class is invalid and needs recompilation Class CMPL123.Mocks : Invalid type : Content Note Resolution to fix the failed package error : You can get rid of this error by enabling notes in your org . Steps to enable notes 1. Go to setup 2. Under search section , type notes as shown :   3. Click on ' Notes Settings ' option . 4. You will see below screen with ' Enable Notes ' parameter unchecked . 5. Check( enable) the ' Enable Notes ' parameter and click save. 6. Re try installing the TWD platform pac...

Extension Requests are TWD records which are used in situations where a time-sensitive record cannot be completed on time. Extension Requests contain information about the change, a proposed due date, Justification for Extension, justification for No Impact and Requested by fields. When Extension Requests are approved in the workflow the proposed due date from extension request record should be updated on parent record. The parent record can be one of the following (Action, Audit, Quality Event, CAPA, Change Control, Standalone CAPA, or Complaint) and shown in the screenshot. The defect as a patch is not made available in latest versions of release but only through QPA installation only. For customers upgrading to Summer 21 and later this patch cannot be used directly through URL installation but needs manually intervention and hands-on customizations to take advantage of the patch. Root cause of the issue: The process builder automation responsible to update Parent Due Date from Exte...

A Document Management System (DMS) is Sparta TWD managed package application which is used to manage all corporate document with activities such as create, edit, upload, and manage the corporate documents. The application comes with pre-defined workflow process like review and approval process which could be used to make document effective before the document is made available to all the business users. The TrackWise Digital Platform application must be installed for DMS to work, and TWD platform application must be installed prior to installing DMS application. With Salesforce has three major releases per year, Sparta also releases 3 releases in a year with major enhancements and features. With such releases more and more features are made available to their customers without impacting business. With DMS packaging being upgraded thrice a year there could be possibility the administrator could face one of the known errors during DMS package upgrade in salesforce orgs which is:...

Document management systems (DMS)   is one of the known solutions pharma organization use to manage their internal quality processes and store/ track all documentation related to quality. By using cloud-based product we have advantages over documents getting lost, outdated version rendered to stakeholders, irregular audit tracking like who made the changes and when. These qualities are necessary for good quality software as part of internal adulting process. The document are uploaded into the DMS system by DMS administrators. The document must go through a pre-defined workflow review process before it is made EFFECTIVE and made available for end users for training reference. The workflow lifecycle for DMS workflow approval cycle includes a) Draft, b) In Review, c)Under Approval and d) EFFECTIVE. Once the document is EFFECTIVE, the document is locked for further editing. The document is later used for internal training and can be printed and shared with internal users for performing...