--- language: "en" --- # Product Knowledge Base ## Articles ### [Gimmal Discover](https://kb.gimmal.com/kt/discover.md) ### [Gimmal Discovery Attender](https://kb.gimmal.com/kt/discovery-attender.md) ### [Gimmal Migrate](https://kb.gimmal.com/kt/gimmal-migrate.md) ### [Gimmal Physical](https://kb.gimmal.com/kt/gimmal-physical.md) ### [Gimmal Records](https://kb.gimmal.com/kt/gimmal-records.md) ### [Gimmal General](https://kb.gimmal.com/kt/gimmal-general.md) --- language: "en" --- # Advanced Classification Rule Options Gimmal Records automates the process of applying records policy to your content. Your end-users simply create and update content without having to assign records classification. It's the Classification rules in Gimmal Records that drive the automation of this process. In addition, everything we talk about here will also apply to your Legal Case rules! There is a lot of good information in our documentation about creating [Classification Rules](https://docs.gimmal.com/rm/Cloud/Cloud/rule-builder), but for this tip article we'll focus on some of the more advanced options. ## Managing Classification Rules To manage Classification Rules, click on Plan in the ribbon: ![image-20240719-212330.png](https://kb.gimmal.com/__attachments/a_6ebac5ff9618db98c1cefb978e3652252325a645292ac50c1fae214b28c474d4/image-20240719-212330.png?cb=0b4fe10e1a6f5f49676275bbd85ad3ea) Once you are in Plan, expand your file plan and click the pull-down menu to select Classification Rules. ![image-20240719-212402.png](https://kb.gimmal.com/__attachments/a_0a25f49bf13630a24cbf2ee1e3a641d9ed5f6fcb1e6fc3a77f4ce4369ef78ec0/image-20240719-212402.png?cb=a8d103f80e53c9e24b83f0cddd8f8f1d) ## Complex Classification Rules In the example Classification rule below, we're using 3 different operators in our 3 rules (the blue line indicates the break between the rules): Starts With, Equals and Like. ![image-20240719-212443.png](https://kb.gimmal.com/__attachments/a_e5c362d593e4749a0c653e3cc0dbe44b39ee729efcb90b5ffde7d460dd9e0620/image-20240719-212443.png?cb=a428aa3a1b91210bcd08dc505c74b078) * Equal (=) is an exact match. The value on the right must be an **exact match** for what you're looking for. One common mistake is adding or leaving off a plural on a word. Contract and Contracts are not the same when using Equal! * Like lets you [use a wildcard](https://docs.gimmal.com/rm/Cloud/Cloud/understanding-the-classification-rule-operators) to match part of a word. It's more flexible than Equal. Did you know there are different wild card operators you can use? * Starts With lets you match the first part of any word string. In this example, the following would all be matches: * All files/Public Sector/HR/Employee Files * All files/Public Sector/HR/Benefits * All files/Public Sector/HR/Hiring Docs ## **Managed Properties** What if you have inconsistency in how some property values are defined? Managed Properties let you create an alias for a number of different properties. ![image-20240719-212547.png](https://kb.gimmal.com/__attachments/a_d495defc3ad3d69a342edaf1fc3d03ae60c0fbfc8ce7837abeaf6a01801c5175/image-20240719-212547.png?cb=12d3ebd9f098af78ba5ca9d4ebfc9e8f) You then use the alias in your rules and Gimmal Records does the work of resolving the alias for you. You'll find Managed Properties in the left hand navigation under Plan. ![image-20240719-212611.png](https://kb.gimmal.com/__attachments/a_1d9aa20aa49f76440370436a21d1e20291936ccde764b3893906e1295aa563b6/image-20240719-212611.png?cb=1c6603ead24fa624b57bf8d435b5ccb1) In this example, we've created an alias called Employee Number that we use in all of our rules. Employee Number resolves to all the of the properties in the list on the right. This makes maintenance of your rules much easier! ## **Rule Sets** Do you have combinations of certain rules you use over and over again? [Rule Sets](https://docs.gimmal.com/rm/Cloud/Cloud/rule-sets) let you create them once then reuse them! You'll find Rule Sets in the left hand navigation under Plan. In this example, we created a rule set called QMS Documents that quickly takes us to a specific location and only shows documents with a metadata property of QMS_Doc. ![image-20240719-212835.png](https://kb.gimmal.com/__attachments/a_b2dce179d940edf2c01a6b5060982e2fb08524e1d5f813e17c19dcb1e57ac1e7/image-20240719-212835.png?cb=91b37e5c73b68fc12eba18f0936bd0b3) This Rule Set can be used in Classification or Legal Case Rules. Kind of like a shortcut! To use the Rule Set, Select the pull down in the rule creation dialog, pick your rule, then hit Add Rule Set. ![image-20240719-212906.png](https://kb.gimmal.com/__attachments/a_35cb582b24e6167e093836764fa057eb3ccea81c38afbc579877e61637fee88c/image-20240719-212906.png?cb=ac61b501b62451fbd44be3340d8db281) The Rule Set will be displayed in your Classification rule dialog. The Rule Set name will be displayed and the rules in the set will have hashmarks over them. ![image-20240719-212940.png](https://kb.gimmal.com/__attachments/a_48d874bc6b9bcca6c1b17698ec933362d8c69bc548d623800c42b5138d614e17/image-20240719-212940.png?cb=315f5f5f0fd3411d4c7677200abdbd12) ## **Internal Lists** A feature called [Internal Lists](https://docs.gimmal.com/rm/Cloud/Cloud/internal-lists) lets you have manageable lists of values represented by an alias in your rules. Some lists are updated on a frequent basis, think of vendor lists or lists of department names. Having list values embedded in your rules can be challenging to maintain. Internal Lists let you create a maintainable list, then use the List Name in your rules. This cuts down on the use of OR in your rules and makes updating the list really easy. Here we have a list of vendors. ![image-20240719-213036.png](https://kb.gimmal.com/__attachments/a_cbfecc913fbea338031516e37d48a2723e502401fc8ac730baad7e1840930348/image-20240719-213036.png?cb=c6eaafa45c5337e7be0b40f004b7eed5) We use Vendor in our rules and Gimmal Records automatically references the list for a matching property anytime Vendors is used in a rule. In this example, we are looking in our Invoices library but only for records where the Vendor Name property matches one of our vendors in the Vendors Internal List. ![image-20240719-213056.png](https://kb.gimmal.com/__attachments/a_0851c9f6e0977b59299e44f9c5a4b324b4927f9caefab9464dfbfe56859033c4/image-20240719-213056.png?cb=189599f321868be30ef040b1b24a0eaf) Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published March, 2024* --- language: "en" --- # ApiInitializer Error ## Problem Files or attachments are skipped with the error detail *The type initializer for 'ApiInitializer' threw an exception.\** in the log file. ## Cause Incorrect Visual C++ library DLLs are installed on the machine. Although Discovery Attender does try to install the correct Visual C++ redistributables on the first startup after installation, it is not aways able to do so. ## Solution 1. Navigate to the installation directory for Discovery Attender. 2. Run the vc_redit.x64.exe and/or the vc_redist.x86.exe to install the correct files. ![image-20221205-220148.png](https://kb.gimmal.com/__attachments/a_d0656aa656d7d67863055a3d86b1f88376dc65ff2e215370216d6ca5368f7032/image-20221205-220148.png?cb=9bcb12145fa9e80e88e294609155c8a4) \[10:53:39.7 Jul-14\] TRACE: Searching file: C:\\Exchange Test Data\\4.4 Testing\\LCaseUCaseNumericSpecial Invalid1 (1).txt \[10:53:39.7 Jul-14\] SKIP: Unable to parse text from file (C:\\Exchange Test Data\\4.4 Testing\\LCaseUCaseNumericSpecial Invalid1 (1).txt) to perform keyword search \[10:53:39.7 Jul-14\] DETAILS: The type initializer for 'ApiInitializer' threw an exception. \[10:53:39.7 Jul-14\] PATH: C:\\Exchange Test Data\\4.4 Testing Highlight important information in a panel like this one. To edit this panel's color or style, select one of the options in the menu. ## 📎 Related articles --- language: "en" --- # Application History and Application Log in Gimmal Physical Keeping track of changes and monitoring unexpected events within your Gimmal Physical application is essential for maintaining system integrity and security. The Application History and Application Log features provide detailed insights into these activities. ## Application History The Application History feature records all configuration changes made within the system, along with details such as the user who made the change and the exact date and time. **How to Access** : Navigate to the Admin page and select the "Application History" link. ![att_1_for_451739741.png](https://kb.gimmal.com/__attachments/a_89fb6c70cd5c40d89a3c32e2653be4794642cbd033f32c9dbcf030a535f23f22/att_1_for_451739741.png?cb=4688f5a6e3cd107dffd6dc372c78f608) * **Filtering Options**: You can filter the history by various categories, including Date/Time, Description, and User details, to easily locate specific changes. * **Exporting Data:** If needed, you can export the filtered history for offline analysis or record-keeping. ![att_3_for_451739741.png](https://kb.gimmal.com/__attachments/a_3ed8c6549c7b937f9ae7a36f679befb4732f173799b3ca5523f9ac02b5fbc160/att_3_for_451739741.png?cb=bc3b373c5641ba1e5dbd8316501cd92b) ## Application Log The Application Log is designed for IT professionals and support teams to diagnose and resolve unexpected application events. It provides technical details on such events, helping to pinpoint the root cause. * **How to Access**: Like Application History, the Application Log can be accessed from the Admin page by selecting the "Application Log" link. * **Use Case:** The log is particularly useful when troubleshooting issues with Gimmal Support, as it offers a detailed view of what occurred during the event. ![att_2_for_451739741.png](https://kb.gimmal.com/__attachments/a_d16626ab40eb4ed55a85fff1fad883761a57a948bd91feffa20e8762fc4c6f42/att_2_for_451739741.png?cb=9a8208ced828dbd1ab1de081413e1f1b) By utilizing the Application History and Application Log features, you can maintain a clear record of all system changes and have a reliable tool for troubleshooting and ensuring the smooth operation of your Gimmal Physical application. Don't hesitate to contact [++support++](https://kb.gimmal.com/kt/contact-information)if you have any questions. *First published August, 2024* --- language: "en" --- # Approval Workflows During the disposition process, you may want to route records to more than one user for approval prior to disposition. Approvers let you define a serial approval process that can [include users or groups](https://docs.gimmal.com/rm/Cloud/Cloud/managing-security), allowing for a structured and controlled disposition process. Creating Approvers is done in the Plan menu. ![att_1_for_369131560.png](https://kb.gimmal.com/__attachments/a_5ba3778a91aacbf45517115d244e187397251dcb2f10aa4b8c1a18379b544f1b/att_1_for_369131560.png?cb=3ec00518e7dd8e62aa7abe747107aab8) Approvers can be created on an individual record class or on a record category. If created on the category, the Approvers workflow will apply to all the child record classes. The process for creating the Approvers is identical. If Approvers are defined for a record class, you will see a checkmark next to the record class name. ![image-20240719-210034.png](https://kb.gimmal.com/__attachments/a_4cf6f064c21c733d0c95ee5b0a5ce70a5bdfb319c4320be2de0a208ba54efde4/image-20240719-210034.png?cb=c3e63d3ca955fdbab223bc507761f2aa) To create Approvers, select Approvers from the pull-down menu to the right of the record class name. ![image-20240719-205936.png](https://kb.gimmal.com/__attachments/a_e1b37b5cb05ca959e77064416c620021158d44837508d033f2bead75ee003b06/image-20240719-205936.png?cb=9fa398f262481dc44c8b645acee57110) This displays the Approvers dialog box. In this example, we have a two-level approval workflow already defined using groups. ![image-20240719-210150.png](https://kb.gimmal.com/__attachments/a_57da65f9386c35cff07a875067ce54378a3bd8ed30742ccab09751a951a5700b/image-20240719-210150.png?cb=8a7e312b070f2faf100e9474435cc157) * To remove a user or group, click the pull-down next to the name and select Delete. * To edit a user or group, click the edit icon. * To remove the Approval workflow entirely, click Revert to Parent button. * To add a new user, click the Create button. The pull-down list displays all users and groups defined in Gimmal Records. Select a username and click Add. ![image-20240719-210255.png](https://kb.gimmal.com/__attachments/a_d9b620ea275c1e4dd1b7cb82d583236e5731b33dc8927a05313f5c4243b24c1b/image-20240719-210255.png?cb=1c1aa9c92c131a4aa9586c0f617b14f0) Multiple users can be added to any step in the Approvers groups. Just keep repeating the Add step. When you have all the users added to an Approver step, click close. Here we added both Roger and Rebecca as stage 3 approvers. ![image-20240719-210539.png](https://kb.gimmal.com/__attachments/a_677b433bdd8926aceeff1c5798fae46db63ed8e331a50d7c445bb9eb13a6f065/image-20240719-210539.png?cb=c194a5f54bcf5f37aea1b57633fdbe96) **Important:** When an Approval workflow hits a step with a group or multiple users, only one user has to approve the step. In step 3, Roger **or** Rebecca can approve the step. It does not require both of them to approve it! You can view the approval history in your Inbox. For any record (or case) in the Inbox, select Approvers from the pull-down menu. A dialog box will display all the steps in the approval workflow and the user, date and time of any previous approvals. This information is also captured in the records audit trail. ![image-20240719-210618.png](https://kb.gimmal.com/__attachments/a_a0000ac7c51ec5f6f126e406dd5948705e896724fba2e505a3211ac0a8076e42/image-20240719-210618.png?cb=289fe464c96669f8ecb4dac1bf394046) You can [learn more about Approvers](https://docs.gimmal.com/rm/Cloud/Cloud/approvers) by visiting our documentation site at [docs.gimmal.com](https://docs.gimmal.com/). Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published May, 2024* --- language: "en" --- # Audit Features Discovery Attender has several features, including reports, views, and direct database access for reviewing work for investigation or audit purposes. Topics of interest may include details such as who ran a search, when it was run, the criteria which was used, any exceptions that were encountered, and an overview of basic statistics. ## Reports Discovery Attender contains several built-in reports for gathering details (inventory) or summaries of the data found in a given search. These reports can be accessed from the Result Summary screen by clicking on the 'Reports' menu item. ![att_1_for_451739682.png](https://kb.gimmal.com/__attachments/a_ef5425b84d818a4a9ae26dbe18f19338a86feb9ea4145b6cbdc4af61a173aa35/att_1_for_451739682.png?cb=ff781da3bcf867dad5cc5f13a3d3beb0) ### Summary This small, simple report provides a general overview of the search details, including criteria, statistics, and data store information laid out in an HTML format. When you choose 'Summary' from the Reports menu, you will be prompted for a location to save the report with an option to rename the file. Once the folder is chosen, the report will generate and then open in your browser. ### List Report (CSV) This report is a listing of all results and includes the commonly requested fields for each result type, including recipients. Selecting this option will open a dialog box that contains the appropriate details. You can track the progress of the report creation in the status bar. Once populated, right-click to select the 'Export to CSV' option from the context menu of the list view: ![att_2_for_451739682.png](https://kb.gimmal.com/__attachments/a_4f42146545f095b4a6e4704eb783609d0bb97812d162d0b1157b35070545c189/att_2_for_451739682.png?cb=130d6dd1dbb3ef9ae787880e2d249535) The formatting of this report is minimal by default. Users can customize the appearance in any spreadsheet program, provided the number of results fall under any application row limitations. Choose the destination folder and CSV file name, then click 'Save' to create the report. Note: The Custom List Report (CSV) allows you to choose the columns that will be included with this report. In contrast, the List Report (CSV)does not offer any options. It will contain all available columns in the output list. ### Keyword Report (CSV) This report is helpful if you need an inventory of records with a basic list of details, along with an indication for each keyword that matched that result. Users have a choice of Leaf Only (recommended), Branch Only, or Original Expression Only. The latter two options are only available if reporting brackets were used during the search. Like the standard list report (CSV), this Keyword Report exports to a CSV file that can be opened using any spreadsheet program (e.g. Microsoft Excel). Note: On larger searches, any of the list reports can take a bit of time to run. ## Views Several helpful views pinpoint details for a search. ### List View (Export to CSV) Any list view control in Discovery Attender can be exported to a CSV file which can be opened in any spreadsheet program like Excel. If you have a view that you'd like to store for reporting purposes, simply select the view, Right-Click and choose 'Export to CSV'. If this menu item is not available, there should be a sub-menu called 'Reporting' which will contain the option. Note; The Export to CSV will export the entire view, not just the selected records. ### View Search Summary Discovery Attender contains a view that can be exported to a text file. This view contains the basic details including the who, where, when and what of a given search. To access this detail, Right-Click on the search listed on the Main Console and choose 'View Search Summary'. To export to a text file, Right-Click in the detail, then choose 'Select All' and Copy. You can then paste the text into any text-based editor including Notepad or Word. ![att_3_for_451739682.png](https://kb.gimmal.com/__attachments/a_c86b688cf810d6f70a14bbcec11ba603f86075ea305b749f3803e09dd43710d3/att_3_for_451739682.png?cb=dd0642c31c2109a73cd3651c55d702be) ## Direct Access If you need more information than is available from the options provided in the User Interface, Discovery Attender's databases are open for direct connection. Each search in Discovery Attender has its own set of databases which are either in the older .mdb or newer .accdb format. The tables in these databases are self-describing, but if you need further assistance in gleaning information, please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First Published November, 2024* --- language: "en" --- # Audit Trails Audit trails maintain a permanent, immutable record of activity. Within a computer system, they record actions taken, the date and time they happened, an indication of who performed them, and additional details about each action. Useful for analyzing what led to the current state of the system or an individual record, and mandatory for demonstrating compliance with various industry regulations, they are the "smoking gun" of who did what and when. Users of Gimmal Records know that once in production, most actions taken within the system are automated. That is, via the configuration of Records Classes, their associated Lifecycles, and Classification Rules, no point-in-time human interaction is necessary. Rather, via repository-specific connectors, records are identified, classified, and advanced through the various stages of their lifecycle. In spite of all the automation however, some actions are explicit: creation of legal cases or holds, indication of event occurrences, granting of disposition approval, etc. Gimmal Records provides two separate views into all this activity, or audit trail: one from an overall system perspective and the other specific to individual records. ## **System View** From the Monitor page, click Audit within the left-hand panel. ![att_4_for_597622991.png](https://kb.gimmal.com/__attachments/a_38ea5aacb35d5be1f790258711338bea47f8a6d7b27f922ded4a1a2e45132c6a/att_4_for_597622991.png?cb=d737923474b9de609ad2f7804a4a5a33) As seen, all system activity is displayed and includes: * Date and time stamp * Details of the activity taken * Source of the activity * Type of activity (Event) * Who performed the activity (User) * Type of object modified (Target), and * Unique Id of object modified (Target ID) Note that you may also filter (by date) the audit trail as desired. ![att_5_for_597622991.png](https://kb.gimmal.com/__attachments/a_c2d7bd8a27bdbb13d8e2b7658da09be08e86cfd8347914d7093fa47d58cba8fc/att_5_for_597622991.png?cb=5c2b57442cd058ccb218345610ba1d9b) ## **Record View** Available whenever viewing an individual record, simply click Audit from the drop-down menu. ![att_6_for_597622991.png](https://kb.gimmal.com/__attachments/a_b90cd0021b428caa6d2710f22b840093c6b18c66ef155e64339a0cf2e3981af7/att_6_for_597622991.png?cb=4b4d7c16919576ae45255b59e740b3cc) As shown below, the Audit trail specific to that record will be displayed. Note you can filter the audit trail using the 'Find' search box, and you can also produce a report via the 'View as Report' link in the lower right. ![att_3_for_597622991.png](https://kb.gimmal.com/__attachments/a_591591defe36435b6a2436a2987934943d877db4973b9bb04e5049550fcd1860/att_3_for_597622991.png?cb=e6535570c665461d1b01b95aca559ce5) ## **Reports** Native stock reports may also be used to analyze audit trail information. From the Monitor page, click Reports within the left-hand panel. Click the View Report button for either the 'Record Audit' or 'User Audit' report. Each may be filtered as desired. ![att_1_for_597622991.png](https://kb.gimmal.com/__attachments/a_d86bc231710fca78659a0f38388254c7903f3591442ac366173f48223c1614ce/att_1_for_597622991.png?cb=fc313c631ea2b0d42b035a26e663024e) ## **Deleted Records** So what happens to all of this audit trail information once a record has progressed through its lifecycle and is destroyed? Well, that is up to you. Notice below, that each Record Class within the system allows you to choose what subset of records data within that class gets archived: * Record Details (meta-data about the record native to Gimmal Records) * Record Properties (meta-data about the record native to its repository) * Record Audits (audit information maintained by Gimmal Records throughout its lifecycle) ![att_2_for_597622991.png](https://kb.gimmal.com/__attachments/a_4fb8b040dc310ff3f28237689f5645e38a28754bcec47d4cb10a1f67ec7c065e/att_2_for_597622991.png?cb=76a1c5c02f6f776a1f471f11cf08bec0) Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published January, 2025* --- language: "en" --- # Auto-Logout Timer (Session Clock) This tech tip refers to a feature in versions prior to 3.15. The Auto-Logout Time has since been replaced with the Session Clock which is an application level preference. ![image-20251110-200458.png](https://kb.gimmal.com/__attachments/a_e381c461f5e0d8d6b15b7d418963460f97a9f74f1e63d35160aac1b224e21309/image-20251110-200458.png?cb=fc8df92c5f84bfefb9f05f98ac959664) Note: The actual timeout duration for the Session Clock can only be enabled when the system is updated via a change to the web configuration file. For Cloud customers, this is typically performed only during an upgrade. To enhance security and prevent unauthorized access, **Gimmal Physical** includes an **Auto-Logout Timer** that displays the remaining time before automatic logout. This feature helps ensure that inactive sessions do not remain open, protecting sensitive records and improving system security. **How the Auto-Logout Timer Works** The **Auto-Logout Timer**is now included in the latest versions of Gimmal Physical. It actively counts down the time left before a session automatically logs out due to inactivity. The timer is: * **Configurable** : The timeout duration is a system-wide setting that can be adjusted by **Gimmal** or your **IT team**if running Gimmal Physical on-premises. * **Visible**: Users can monitor the countdown timer to avoid unexpected logouts. * **Resettable**: To extend your session, simply interact with the application by clicking any button or entering data anywhere. ![att_1_for_597360736.png](https://kb.gimmal.com/__attachments/a_fce595b24284f4cf1787f84e3b255525be94bd1fdc389ec66d9441665f57a6e1/att_1_for_597360736.png?cb=d9f9adf1fd8dd84194fd5053739d795a) **What Happens if You Timeout?** If no action is taken before the timer expires, **Gimmal Physical will automatically log out the user**. A message will appear notifying you that the session has timed out, requiring you to log in again to continue working. By keeping track of the Auto-Logout Timer, users can prevent unexpected logouts and maintain workflow efficiency while ensuring system security. Don't hesitate to contact [++support++](https://kb.gimmal.com/kt/contact-information)if you have any questions. *First published February, 2025* --- language: "en" --- # Automation in Gimmal Discover Gimmal Discover has a built-in mechanism to support the invocation of a few of its powerful processes through an external trigger. This technique gives you a way to initiate Discover tasks based on an activity external to the solution without having to login through the administrative console and manually start them. For instance, if you would like the creation of a new group in your organization's directory to prompt Discover to query the directory for the group's members and add them to its set of managed users, Automation provides the means to do that. The Automation process also serves as a convenient way to create multiple process definitions and avoid having to key them in manually through the interface. The following Discover processes are available through Automation: * Creation of a Data Owner Search * Creation of a Data Target Search * Creation of a Governance Policy * Update a Governance Policy with one or more of the following options: enable/disable a schedule, reset schedule expiration, add/remove a Data Owner, add a Data Target. * Starting a Governance Policy The automation process is facilitated using Discover templates and the uploading of a parameter file to Discover through a location monitored by a Discover Connector within your environment. Discover templates provide a way to genericize the creation of Data Target \& Owner Searches and Governance Policies through tokens that are replaced during processing with values transferred through the parameter file. Gimmal's customer service team can help with creating the format of a parameter file to satisfy your particular use case. Please review the Discover documentation [here](https://docs.gimmal.com/alt/automation) for the specific configuration steps to setup the Automation process. ![att_1_for_369819653.png](https://kb.gimmal.com/__attachments/a_8a64e8ccc6d8569e9161d3656b18224547f6088993fd7b47da7ce06f77cfb0a5/att_1_for_369819653.png?cb=12bfeb12d01adbe7818c2f5e9af94788) Please reach out to the Gimmal support team at [support@gimmal.com](mailto:support@gimmal.com) with any questions. *First Published February, 2024* --- language: "en" --- # Azure Storage Account access The information in this page is provided as an aid only. While accurate at the time of publication, the details provided by Microsoft are subject to change without notice. When using the MAPIT application, access to Azure Storage is required from the machine where MAPIT is installed, and from the target SharePoint site(s). If you have enabled public access or provided white-listed IP addresses and are still getting migration errors in MAPIT, the following information may be helpful: * It may take up to 24 hours (usually less) after enabling public network access or providing whitelisted IP addresses for these changes to actually take effect. * The Azure Storage account provides options for troubleshooting. After accessing the Azure Storage account, expand Data Storage and select Queues. Select a queue on the right, click into it, then choose **Diagnose and solve problems**. There are several options to select from that may provide helpful information or answers. ![Where to Troubleshoot Azure Storage communications.png](https://kb.gimmal.com/__attachments/a_e6938e204bf6c1278a04b7de6cc6fad0e0c01b17a75a977b32ebcf8d60507edd/Where%20to%20Troubleshoot%20Azure%20Storage%20communications.png?cb=9bc0c3d4553faf7b102c4f1b189b9a2c) * The main dashboard page for the Azure Storage account also includes a link for **Diagnose and solve problems** that may be helpful. --- language: "en" --- # Best Practices * [Connector Maintenance \& Administration](https://kb.gimmal.com/kt/connector-maintenance-administration.md) * [Environment Health Check](https://kb.gimmal.com/kt/environment-health-check.md) * [How do I share my Data Governance policy with another user](https://kb.gimmal.com/kt/unable-to-view-policy-created-by-another-user.md) --- language: "en" --- # Branding and Themes You may want to personalize the look and feel of Gimmal Records for your users. Gimmal Records provides the ability to add your corporate logo to the ribbon and the login page. Plus, you can change the color scheme to one of the pre-defined themes provided. ## **Global Preferences and Themes** Changing the logo or theme is accessed in the Settings menu. ![image-20240719-210821.png](https://kb.gimmal.com/__attachments/a_b3e46bd54cacf4013b99b9f631c0179d9c3a9a198208cc70ceb53267ad547812/image-20240719-210821.png?cb=afe047ce5bfec3de6808991437e370e4) ## **Changing the Theme** To change your color scheme, you can select from any of the pre-defined color schemes in Gimmal Records. ![att_2_for_369623124.png](https://kb.gimmal.com/__attachments/a_921c3d8f127bfcaf4c724fe5ec7a1233bf8d53d27360c03b417dd03ec5cc8093/att_2_for_369623124.png?cb=a0d678f96e07a420e66bd6652d597494) Click on the theme you want to use. Then click the Update button. The user interface will refresh, and your new colors will be displayed. Creating custom themes is not currently available . ## **Changing the Logo** You can have your corporate logo (or any other image) display in the Gimmal Records ribbon and on the login page. You will notice there are two places where you can upload a logo. This allows you to have a different logo on the login screen and the ribbon if you like. The left side shows the logo that appears on the initial login screen. The right-side logo appears on the ribbon throughout Gimmal Records. ![image-20240719-211128.png](https://kb.gimmal.com/__attachments/a_32222fa6c94968f49369cebae871c428337314a48e5d17ff1dd15f4e71fe00f3/image-20240719-211128.png?cb=4aea13b536694a52426407b16fc2fb08) Click on the Upload button to upload your new logos. The Upload dialog has two Choose File options. These are: 1. Logo -- this is the main login screen logo (left in the image above) 2. Alternate Logo -- this is the logo that appears on your ribbon (right in the image above) Simply navigate to the location of the logo on your local file system and select it. The logo should be in .PNG format. Click Submit. to save your changes If your logo doesn't align itself properly, you can use the Top and Left boxes to enter offset values (in pixels). Keep modifying the values until you get a look that you like. More information on Themes and Logos can be found in our [online documentation](https://docs.gimmal.com/rm/Cloud/Cloud/global-preferences-and-theme). Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published July, 2024* --- language: "en" --- # Branding and Themes in Gimmal Records **Did you know you can personalize the look of Gimmal Records?** You may want to personalize the look of Gimmal Records for your users. Gimmal Records provides the ability to add your corporate logo to the ribbon and the login page. Plus, you can change the color scheme to one of the pre-defined themes provided. ## **Global Preferences and Themes** Changing the logo or theme is accessed in the Settings menu. In settings, look at the left navigation menu. You will see an option for Theme: ![att_3_for_452034660.png](https://kb.gimmal.com/__attachments/a_6e3ccce6a8dc655ba608447f9c388b958dbbaac417ff879143e5e50001de75fb/att_3_for_452034660.png?cb=1c52558686e44ab0e8235334fe65ccc9) ![att_1_for_452034660.png](https://kb.gimmal.com/__attachments/a_9b85979926808c8778f0c6b7e1e6637136c6dd142567835b816bd2f8f37f8f38/att_1_for_452034660.png?cb=e1b31c4e4a4ba727540b5000ab4a011e) ### **Changing the Theme** To change your color scheme, you can select from any of the pre-defined color schemes in Gimmal Records. ![att_2_for_452034660.png](https://kb.gimmal.com/__attachments/a_7054765cb8574f4915188f52296e25173d8fe109de1fcc1de6ebc4538ef91259/att_2_for_452034660.png?cb=a0d678f96e07a420e66bd6652d597494) Click on the theme you want to use. Then click the Update button. The user interface will refresh, and your new colors will be displayed. Creating custom themes is not currently available. ## **Changing the Logo** You can have your corporate logo (or any other image) displayed in the Gimmal Records ribbon and on the login page. You will notice there are two places where you can upload a logo. This allows you to have a different logo on the login screen and the ribbon if you like. The left side is the logo that appears on the initial login screen. The right side logo is what appears on the ribbon throughout Gimmal Records. ![att_4_for_452034660.png](https://kb.gimmal.com/__attachments/a_418cc9f7fcbbb54dbd0a83fc8e9b316dc3642b7ba95c6c6d3a0800a53024bf36/att_4_for_452034660.png?cb=5957f7d8139f50c153490e041d8b5858) Click on the Upload button to upload your new logos. The Upload dialog has two Choose File options. These are: 1. Logo -- this is the main login screen logo 2. Alternate Logo -- this is the logo that appears on your ribbon Simply navigate to the location of the logo on your local file system and select it. The logo should be in .PNG format. Then click Submit. If your logo doesn't align itself properly, you can use the Top and Left boxes to enter offset values (in pixels). Keep modifying the values until you get a look that you like. More information on Themes and Logos can be found in our [online documentation](https://docs.gimmal.com/rm/Cloud/Cloud/global-preferences-and-theme). --- language: "en" --- # Broadcast Notifications Most Gimmal Physical users are familiar with email notifications triggered by specific actions within the system --- such as approvals, transfers, and check-ins. But did you know that you can also send broadcast notifications to reach all users at once? Whether you need to share an important update, policy change, or system-wide alert, Broadcast Notifications let you quickly communicate with your entire user base---all within Gimmal Physical. **How to Send a Broadcast Notification** ![att_1_for_597327982.png](https://kb.gimmal.com/__attachments/a_fb354ff3cfaf6c35c713431e75d297cd053ac20b8f8fb659b493f0ff3f8599ba/att_1_for_597327982.png?cb=2fb16b427e80d485635cdab307d15e66) 1. Go to **Admin \> Broadcast Notifications** 2. **Choose a notification typ**e: Select a pre-set notification from the available options, or select General Message for a custom message. 3. **Enter your message**: Add a subject line and message content 4. **Select recipients**: Choose specific roles to receive the message 5. Click **Send** This feature is ideal for system announcements, urgent reminders, or general updates ---ensuring your team stays informed and aligned without needing external email chains. Don't hesitate to contact [++support++](https://kb.gimmal.com/kt/contact-information)if you have any questions. *First published January, 2025* --- language: "en" --- # Change the default value in the 'List' from EWS **I** **ss** **ue** Note: This article only applies to Discovery Attender 4.3 User is trying to create a list of users to search but is unable to use the selected Email Property for searching EWS data stores from the **List** generated in PowerShell. ![Screenshot 2023-09-07 155043.png](https://kb.gimmal.com/__attachments/a_02ba5f4a556cafc51e3b8bfdd1695608f4df84902e20ff3fa909935266500a08/Screenshot%202023-09-07%20155043.png?cb=25882363aca7cf6990db0b29f57b0e0d) **Cause** The rewrite of EWS properties for DA 4.3 failed to deploy this option correctly. **Resolution** A change to a value in the registry should replace the default value for the **List** option in the Wizard. 1. Navigate to the **Discovery Attender for Exchange** key in the Registry under 1. DA 64-bit: **HKLM\\SOFTWARE\\Wow6432Node\\Sherpa Software Group\\Discovery Attender for Exchange** 2. DA 32-bit: **HKLM\\SOFTWARE\\Sherpa Software Group\\Discovery Attender for Exchange** 2. Locate the string value called **PowerShell Email Property** and double click to edit the data field. 1. ![rtaImage.png](https://kb.gimmal.com/__attachments/a_823c43e66767e956893f88f1dc5fbb9a6e5a1069c5c694b02a500a153f99de66/rtaImage.png?cb=620f8b0ac518c78ab40183554942ce04) 3. Change the Value data field to the integer value that matches your choice: 1. **0** - UserPrincipalName 2. **1**- PrimarySmtpAddress 3. **2**- WindowsEmailAddress 4. Close the registry, try the **List**option again. --- language: "en" --- # Cheat Sheet for Copying Keywords One of the most common tasks a user undertakes is transferring keywords from an outside source (legal counsel, Open Records requests, etc.) and formatting them for a search in Discovery Attender. Often the original data will not be in the format needed by the application, even if it passes the integrated Keyword Tester. This could result in missed results and data integrity issues. To avoid accidentally limiting or invalidating your search from a poor transfer of keywords, we've created the following cheat sheet to follow when copying data. ## Common issues * **Proximity differences** : Other applications may use the**wordA w/# wordB** format, but Discovery Attender instead uses the **wordA NEAR(#) word B**. * **Wild Card differences** : Other applications may use an exclamation point (**!** ) for a zero or any wild card. Discovery Attender uses the asterisk (**\***) * **Wild Cards in Double Quotes**: Other search tools allow wild cards in double quotes to be treated like a wild card. Discovery Attender, on the other hand, assumes you want to find that exact wild card character. To avoid this issue, check all words or phrases which are in double quotes and verify they don't have wild cards. If they do, either remove the double quotes (for single words), or add the LIKE operator around the double quoted phrase (e.g. LIKE("my phras\* here"). ## Suggested Checks The best first step is to copy your keywords into Notepad or the equivalent and run a series of universal Find and Replace actions. 1. Replace **w/#** with **NEAR(#)** . Note: You may need to perform this action for each variant in the number(e.g. w/5, w/20) 2. Replace**/#** with **NEAR(#)** Note: You may need to perform this action for each variant in the number(e.g. /5, /20) 3. Check for Wild Cards in Double Quotes 4. Use the Keyword Tester to validate the entire expression ## Cheat Sheet |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------| | **Text to Replace** | **Description** | **DA Equivalent** | **Example** | | **w/** **w/#** | Common proximity operator where the # indicates the limit for number of words apart | **NEAR(#)** | **Old**: dog w/5 bone **New**: dog NEAR(5) bone | | **!** | 0 to many wildcard used by other systems. Can be used on either side of the word or phrase. | **\*** | **Old**: bank! **New**: bank\* | | **"word\*"** | Valid wildcards presented within double quotes. Discovery Attender would interpret this literally -- and would only return results which contained the actual wild card character | **word\*** | **Old:**"bank\*" **New:**bank\* | | **"Multi-word Phrase\*"** | Valid wildcards presented within double quotes, but with a multi-word phrase. In DA, for a list of words, the double quotes can simply be removed. However, for a Search Expression or within a function (e.g. proximity), the LIKE("phrase\*") construct must be used | **Multi-word Phrase\*** or **LIKE("multi-word phrase\*")** | **Old:**"stock market\*" **New:**stock market\* Or LIKE("stock market\*") | Please contact [us](https://kb.gimmal.com/kt/contact-information) with any suggestions to add to this list, or if you need any assistance structuring your keywords. *First Published March, 2025* --- language: "en" --- # Compliance Details not visible If you are missing **Compliance Details** in the document's context menu in SharePoint, and need it, make sure the **In Place Records Management** feature is activated. When using the SharePoint Connector, there are two site collection features involved -- **SharePoint Connector Integration** and **SharePoint Connector UI Integration**. ![image-20230512-220431.png](https://kb.gimmal.com/__attachments/a_de0d26b60ee4c57846a1f9dea04956070beb76332e4e6b9e3c8e6e1fd319802a/image-20230512-220431.png?cb=8ab43631986d8786f15b2aa4e09305d3) When the **SharePoint Connector UI Integration** feature is activated the SharePoint OOTB **Compliance Details** menu option is hidden. When the feature is deactivated, **Compliance Details** will again be visible in the document's context menu. --- language: "en" --- # Connector Maintenance \& Administration * [Restart connector without restarting the server](https://kb.gimmal.com/kt/restart-connector-without-restarting-the-server.md) * [Policy will not stop processing](https://kb.gimmal.com/kt/policy-will-not-stop-processing.md) --- language: "en" --- # Settings \& Options --- language: "en" --- # Contact Information ![image-20251110-183000.png](https://kb.gimmal.com/__attachments/a_02831b05d113a704359d5cdddf4d27e540791a21a0cc63a2eddae525abf569a3/image-20251110-183000.png?cb=3750b89741d08b4f05b42252dfacf730) ## Technical Support * **Email** : [help@morae.com](mailto:help@morae.com) ## General Information * Email: [info@gimmal.com](mailto:info@gimmal.com) * Web Page: [www.gimmal.com](https://gimmal.com/) --- language: "en" --- # Core Application The Gimmal Records Core application includes the following components: * **Manager Web** - Primary UI for the Gimmal Records application. This can be hosted on-premises, or in Gimmal's SaaS environment. * **Lifecycle Processing Service** - Windows service responsible for calculating and processing record locks/unlocks, retention expiration dates, etc. * **Migration Utility** - Used for import and migration of file plans. Please refer to the list below for the 10 most recently updated KB articles in this category. * [User unable to login to Manager Web](https://kb.gimmal.com/kt/user-unable-to-login-to-manager-web.md) * [Load Balancing the Manager Web](https://kb.gimmal.com/kt/load-balancing-the-manager-web.md) * [Gimmal Records SaaS Invitation](https://kb.gimmal.com/kt/gimmal-records-saas-invitation.md) * [Destruction Certificates](https://kb.gimmal.com/kt/destruction-certificates.md) --- language: "en" --- # Create EWS Mailbox list via PowerShell **Description** When creating a list of EWS users via Discovery Attender Settings-\>EWS Options-\>PowerShell-\>Export, the list may not be created, or another error may be encountered. The **PowerShell** button on the EWS Mailbox selection screen (see screenshot below) is populated by a .dat file created (usually) in the Settings. However, sometimes the creation of this list cannot be accomplished within the settings. PowerShell can be used to create this list. The PowerShell command to create the file is as follows in version DA 4.0 or higher: get-mailbox -ResultSize unlimited | fl RunspaceId,UserPrincipalName,PrimarySmtpAddress,DisplayName,WindowsEmailAddress > EWSAccounts.dat **Note** : If you would like to filter by department, the following command should work Get-Recipient -ResultSize Unlimited -RecipientType UserMailbox -Filter {department -eq "DepartmentName"} | Get-Mailbox | fl RunspaceId,UserPrincipalName,PrimarySmtpAddress,DisplayName,WindowsEmailAddress > EWSAccounts.dat **Note:** If you are having trouble exporting the list of mailboxes, please check these areas before attempting this PowerShell Command. 1. Azure permissions 1. Confirm these permissions are configured as specified in the Discovery Attender [Getting Started Guide](https://docs.gimmal.com/__attachments/2064437/GettingStarted.pdf?inst-v=e6a4d8b9-d225-4782-b481-ecbc9a889b1a) 2. Confirm modern authentication is correctly configured for Discovery Attender 3. ![MicrosoftTeams-image (3).png](https://kb.gimmal.com/__attachments/a_c8ff965b538a93b2b0a1d5da6b960d81a7d72d2e4c75beb1984ca587af5639c1/MicrosoftTeams-image%20(3).png?cb=45d8688e53f621bcdaf0b076e92dbd43) 2. [Default value for EWS List is incorrect](https://gimmal.atlassian.net/wiki/spaces/KT/pages/edit-v2/173801486?draftShareId=f02b391b-d361-4ecc-a03b-c4db6c4709e5) (only applies to Discovery Attender version 4.3) --- language: "en" --- # Customize Your Action Toolbar Gimmal Physical allows you to customize how your actions appear in the Gimmal Physical toolbar. You can change the order, hide options and set the hierarchy of actions as well as the captions. **Steps to customize your Action Toolbar in Gimmal Physical:** 1. Navigate to the Admin section of your Gimmal Physical application. 2. Look for the Action Toolbar option within the Admin menu. 3. Once you access the Action Toolbar settings, you'll find options to modify button captions, rearrange their order, and create new parent menus. ![att_2_for_370507785.png](https://kb.gimmal.com/__attachments/a_12c082f51047a50748bc1a51022af76eb5a6412ffcd85c5d00fce120b61475ab/att_2_for_370507785.png?cb=1e5244ff30705f2b7276093b55460604) 4. To change button captions, simply select the button you want to modify and edit the caption field accordingly. 5. To rearrange the order of buttons, use the drag-and-drop functionality to move buttons to your desired positions. 6. If you wish to move buttons between parent menus, you can easily do so by selecting the button and choosing the appropriate parent menu from the dropdown list. 7. To create entirely new parent menus and their associated child buttons, explore the options available within the Action Toolbar settings. ***Note:****It's important to remember that any changes made to the Action Toolbar will apply to****all****users of the system. Be mindful of the impact on other users when making modifications.* Don't hesitate to contact [++support++](https://kb.gimmal.com/kt/contact-information)if you have any questions. *First published February, 2024* --- language: "en" --- # Data Targets, Processing, and Scalability Gimmal Discover is scalable to any organization, regardless of the overall data size. However, steps can be taken to increase throughput. If there are no concerns with the length of time a Classification/Data Governance Policy and/or eDiscovery Search can take, a company with thousands of Data Targets does not need to deploy more than one Connector. However, if you want to decrease the amount of time that a Policy/Search takes, you do have some very viable options. This Tech Tip will cover your choices and it is recommended you leverage as many of these as you can. ## **Increase the # of Threads** For any of the Data Source agents, you have the ability to increase the # of Threads. Since each thread allows for the simultaneous processing of a Data Target, the more threads you have, the faster the Policy/Search will run. Though the maximum # of Threads is 50, it is recommended to never set it that high. Instead, the highest recommended # of Threads is 10. To set the # of Threads per Data Source, select the Connector and click More \| Connector Settings, as seen below: ![att_4_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_802dd197aa8fb11c4fac9bde550d0b8d3bf6f05f1ca074d92f5444d0494c07e6/att_4_for_369295389.jpeg?cb=5917dd2cf834632760c2bf526bd10cbc) Click on any Data Source tab, and you will see the 'Max Policy Thread Count', as seen below: ![att_5_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_0d60633731c9b5fdf26ab1f2ea44ae61c876745ca296e2a096f7154d6204a63c/att_5_for_369295389.jpeg?cb=c0b6b8cb4221f11059af8311dc79a371) Enter the value and click 'Update'. Since Gimmal Discover is a hybrid SaaS solution, the new # of Threads will not take effect immediately. Again, caution is advised when assigning more than 10 threads, because there could very well be a point of diminishing return by having too many threads. Note: The default # of Threads is 3. ## **Increase the # of Connectors** Since Gimmal Discover does not license the by the # of Connectors, you can deploy as many Connectors as you like. Once the new Connector has been deployed, you can then assign the Data Targets to the new Connector, as seen below: ![att_6_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_09069f4bccf77f837be67737a4e7f29e24df8d1ca7bf6e195ef8a45730190ca8/att_6_for_369295389.jpeg?cb=12f27657bb712a1801f5b9f1570940a3) Select the Data Targets and click Actions \| Assign Connector, which will display a list of Connectors. Select the Connector and click 'Save'. This will then permanently assign the Connector to the Data Target. So any Policy/Search that is run, the assigned Connector is the one that processes each Data Target. A Script can be created and scheduled when needing to dynamically assign the Connectors. This is useful when ensuring the Data Targets are evenly distributed across the Connectors. Contact [support@gimmal.com](mailto:support@gimmal.com) for details. Note: Only one Connector can be deployed per server/VM. So if you want five Connectors, you will need five servers/VMs. ## **Resize your Windows File Path Data Targets** The Data Targets for Windows File Paths are unique, because they can be created at any subfolder level. This means that you have the ability to control the Data Targets, For instance, if you have a UNC path (e.g., [\\\\MyData\\Departments](file:///Applications/Microsoft%20Outlook.app/Contents/Frameworks/EmailRendererKit.framework/Resources///MyData/Departments)) that is 1 TB, you could create a Data Target for that specific UNC path. But that means that only one thread will be used to process all 1 TB of the path. But if there are 10 subfolders below the [\\\\MyData\\Departments](file:///Applications/Microsoft%20Outlook.app/Contents/Frameworks/EmailRendererKit.framework/Resources///MyData/Departments) folder, you could configure the Data Target Search to create a Data Target for each subfolder. In this scenario, each of the 10 subfolders would be a Data Target. If 10 threads were assigned, all of the Data Targets could be processed simultaneously, thus increasing the throughput by 10x. ![att_1_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_8a5d6f4ff1a97444b3a7760fc757a2895b83b20680af98a85d71da98d27073cb/att_1_for_369295389.jpeg?cb=df6beb65cbd171b020640d75b7624dd5) Enter 1 in '# of subfolders to use for target data assignments. ![att_2_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_9846f059cf01d58075fb36a2ab865cf13d98d8135f8a07a56799b2b3abcafc96/att_2_for_369295389.jpeg?cb=f2706103c5cc569832a9cd488f076b48) Enter the parent UNC path. When the Data Target Search runs, a Data Target will be created for every subfolder within the parent UNC path. ## **Index your Windows File Paths** To expedite processing of the content (not metadata) of the Windows File Path Data Targets, it is recommended that you index the Windows File Path using Gimmal Discover, as seen below: ![att_7_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_aebdb06b1eacc98e256af9a02ae72afa5bcaebd373f7806e5ebc4b13c2f50759/att_7_for_369295389.jpeg?cb=40552774c847f5f70a1a36c0bb76fe3e) Once indexed, content processing by a Policy/Search will be a great deal faster. ## **Leverage the Server-side filtering** Using the 'Fast Search' (Classification/Data Governance) and/or the 'Quick Search' (eDiscovery) for EWS Archives/Mailboxes will leverage the index that Exchange-Online and Exchange 2016/2019 maintains. This will expedite processing when searching content, but also allows parameters to be passed that returns a matching subset of messages. For instance, using the 'Fast Search' within an EWS Mailbox Workflow will allow you to filter the messages using dates, types, classes, etc. When used processing a folder, instead of having to interrogate the metadata for each item, Exchange will filter the items so that it returns only the ones matching the parameters. For instance, if there are only 100 messages within a specific data range in a folder containing 10,000 messages, Exchange will only return the 100 messages, thus saving time. In the example below, the 'Fast Search' criteria has both the type of messages and a search expression. ![att_3_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_ddba66a0af9e062a410e22b1a531553c8adf1af2a4fc9e76e6f3624e667dc46a/att_3_for_369295389.jpeg?cb=2a7a92d620472e45f27cac00f0037186) Exchange will only return the items that are of type 'Message' and match the specified search expression. ## **Leverage Classification** Classifying provides a proactive method of tagging a data item based upon matching metadata and/or content. The tag can then be referenced by both Data Governance and eDiscovery to only process the data items that match the desired tag(s), as seen below: ![att_8_for_369295389.jpeg](https://kb.gimmal.com/__attachments/a_511c898ce15f68739697d1bf9e30a7677bbaa24f01d4affc0c9af73d6b50c36e/att_8_for_369295389.jpeg?cb=9bf2e6d6ced8c55b3a7ffdfd4a55631e) In this example, if a Policy/Search only wants to process the data items tagged with a specific label, instead of processing the entire set of data, you could focus a specific label. If a label has only been applied to 5% of the data, the Policy/Search will run 20x faster, since only the data items with that specific label need to be processed. Please reach out to the Gimmal support team at [support@gimmal.com](mailto:support@gimmal.com) with any questions. *First Published April, 2024* --- language: "en" --- # 'Database Error' as Task Result ## **Issue** Task status is listed (in red) as 'Database Error'. ## **Cause** The reason the database errors are thrown is to alert the user that some data may be missing from the result set. These errors happen for one of two reasons: 1. **Database size has exceeded the 2gb limit** for one of the search databases. This generally happens when the total number of search **results**exceeds \~200,000 or otherwise has excessive metadata. In this case, the search will need to be split up (generally by breaking up the data stores into two or more searches) and rerun. 2. **Malformed SQL** in a function updating the database. In this case, the task log file will list the task as having completed successfully. However, it contains warnings that some records could not be updated. The application log file from the day the search was run contains the SQL which lists the table that could not be updated . If the faulting insert SQL is to either the DA_RESULTS_COMMON or DA_RESULTS_MESSAGES tables, then some results may be missing from the result set, not all results can be exported, the count will be off or all three of these conditions may occur. If the error is for any other table, you may not be able to see some of the metadata, but the list, count and exports will be correct. In this case, the searches don't have to be rerun, see 'Solution' below. ### **To determine which type of error is being thrown, follow these steps:** 1. Turn on Debug Logging 1. Navigate to the Settings from the main Console. 2. On the default 'General' node, choose the 'Debug' option for the 'Error Logging Level' 3. Click the 'OK' button to save your changes. Note: Do not forget to reset the error logging to 'Normal' once troubleshooting is complete. 2. Check for overloaded databases 1. Select the search from the top pane of the Main Console window, 2. Right-Click and choose Debug \| Open Search Directory from the context menu. This opens the specified search directory in the File Explorer window. 3. Open the 'Database' sub directory. 1. If any of the databases are \>= 2gb, then this Database Error is **not** resolvable, The search will need to be split up and rerun. 2. If the databases are all normally sized (1.8 gb or below), then follow the solution below. ## **Solution** To resolve this issue for your current searches with SQL errors (see check above), follow the steps below for each task that has the Database Error: 1. Highlight the task with the error and Right-Click to open the context menu, 2. Select 'Reset Task Status'. Click 'OK' or 'Yes' to the prompts that follow. 3. When finished resetting all the tasks that have a database error, use the refresh button on the mid screen toolbar. 4. Select the refresh at the top (or close and re-open DA). You should now be able to see the results from tasks in all results screens and totals. Note: The actual faulting sql will be found in the application log for the day the search was run. If you would like to perform further troubleshooting, send the application log to the [support team](https://kb.gimmal.com/kt/contact-information). ![image-20240719-175941.png](https://kb.gimmal.com/__attachments/a_81b1210d9c185eda836478d00d9a8255a0f1b6697bdf1e9445f4a26115ad14b8/image-20240719-175941.png?cb=99db2b5fe3e15d2b3b2736fc0cdd2b8d) --- language: "en" --- # Default Search Options in Gimmal Discover Discover's eDiscovery module offers a comprehensive pre-review set of capabilities to facilitate efficient data collection, commensurate with the specific needs of the matter. The process of identifying relevant data and collecting it is structured around a Matter, which identifies the subject of the collection. Custodians associated with the Matter may be assigned to it through the Discover Matter configuration. Also contained within the Matter structure are Legal Holds, Searches and Collections: * The **Legal Hold** configuration in Discover provides a framework to manage the hold notifications process, ensuring your organization complies with the requirement to notify custodians of their obligation to preserve matter-related data. * An **eDiscovery Search** in Discover provides a granular and comprehensive mechanism to investigate licensed and supported data repositories for content that meets specific criteria related to the matter. * Through the **eDiscovery** **Collection** process, Discover provides a way to generate an offline corpus of the searched and identified content related to the matter to support the subsequent steps in the eDiscovery process, such as Review and Processing. eDiscovery Searching within Discover supports several criteria, filters, and automated options to facilitate a targeted and efficient process. These include: * **Content Sources:** Refine your search to specific data repositories that contain information related to the matter * **Metadata and Content Criteria:** Limit the results to content that meets metadata criteria such as file types, dates (created, modified, accessed), keywords, and patterns * **Cache Search Results:** Cache a local copy of the documents that meet the search criteria to ensure all search results are available downstream if the resulting documents are required to be collected * **Auto-collections:** Automate the collection of all content that meets the defined criteria, skipping the step of reviewing the results and specifying documents * **Retrieve Full-text:** Have Discover return and render the full text of all or a configured subset of the content matching the criteria to help validate the criteria used * **DeNIST:** Automatically exclude all system-generated and system-specific files, as defined by NIST, from being included in the search results Discover's eDiscovery Search allows for the configuration of each of the above levers to be applied for each search created in the application, as seen here on the initial screen of a new search configuration: ![att_1_for_452231212.png](https://kb.gimmal.com/__attachments/a_6f8b578559d0ed83f994ce6642942277e0bebc99db31534cfe1666b0214327d5/att_1_for_452231212.png?cb=d315c595033ea4302af93b02473911b6) Discover also provides the option to pre-define a set of default values for the options shown above. These defaults will be automatically applied to every new eDiscovery Search created in the application interface. These defaults (shown below) may be configured in the eDiscovery tab of the Settings section of the administration console: ![att_2_for_452231212.png](https://kb.gimmal.com/__attachments/a_46c76943410e66576721afb084811a658b8498be0257edfd88e586f4b8d1477c/att_2_for_452231212.png?cb=b99b6d37d294f6386ca40809b5173fdc) The File Types option offers a way to only include or exclude a pre-defined set of file types when executing the search. Configuring this list as a default, along with the other listed search options, ensures all searches are created with the defined options. Any of the default options may be modified within a newly created search by editing it and updating the necessary options. Please reach out to the Gimmal support team at [support@gimmal.com](mailto:support@gimmal.com) with any questions. *First Published August, 2024* --- language: "en" --- # Delete vs. Expunge ## Delete/Bulk Delete The delete actions perform soft deletes where the deleted items are still viewable (displayed in red italics on the home page), but no user actions can be performed on them (e.g. - a user can no longer request them). Bulk Delete is used for deleting multiple items at once. Deleted items can be restored using the **Undelete** and **Bulk Undelete** options. ## Expunge/Bulk Expunge Expunging an itemcompletely removes it from the application and is irreversible. An expunge action is retained in Gimmal Physical's audit trail and record history. **Bulk Expunge** is used for expunging multiple items at once. --- language: "en" --- # Destruction Certificates Gimmal Records can provide basic destruction certificates with a few simple settings: * For each Record Class you want to create destruction certificates for, change the record class property **Destruction Certificates** to **Yes**. ![image-20230605-224538.png](https://kb.gimmal.com/__attachments/a_547334cf1d00561d9df00f17376e6f24c99939bb7851b151c3fd5db6a2b691da/image-20230605-224538.png?cb=1c77deb9ef8da6dc52e5b0dd8d23e78f) * The lifecycle attached to the record class must require approval in its final phase. These destruction certificates are generated for each unique combination of approver/record class/disposition date - i.e. Two people approving dispositions for the same record class on the same day would generate two different certificates. ![image-20230602-192047.png](https://kb.gimmal.com/__attachments/a_6a4a4165668223df9e532547e2cd844acfe48530d9ee3ad427508c22eb6b611f/image-20230602-192047.png?cb=05e1cdd68d868f370c07b440a1e21321) The destruction certificate is created **AFTER** the deletion of the item from its repository. After the connector's retention job has processed the final disposition action (which successfully deletes the document from its repository), a "success" event is then reported back to Gimmal Records. When that event is received, the pending action item is completed, and Gimmal Records generates the destruction certificate. --- language: "en" --- # Gimmal Discover [Best Practices](https://kb.gimmal.com/kt/best-practices.md) [Error Messages: Causes and Resolutions](https://kb.gimmal.com/kt/error-messages-causes-and-resolutions.md) [Tips, Tricks and FAQs (Discover)](https://kb.gimmal.com/kt/tips-tricks-and-faqs-discover.md) * [Education Sessions (Discover)](https://kb.gimmal.com/kt/education-sessions-discover.md) --- language: "en" --- # Gimmal Discovery Attender [Settings \& Options](https://kb.gimmal.com/kt/console-main-interface.md) [Errors](https://kb.gimmal.com/kt/errors.md) [MAPI and .PST's](https://kb.gimmal.com/kt/mapi-and-pst-s.md) [Tips, Tricks and FAQs](https://kb.gimmal.com/kt/tips-tricks-and-faqs.md) --- language: "en" --- # Disposition in Gimmal Records Disposition is the final decision about whether to dispose of records or keep records permanently. In Gimmal Records, this is managed in the Inbox. Click Dispose in the Gimmal Records Ribbon to see your Inbox. ![image-20240719-211613.png](https://kb.gimmal.com/__attachments/a_bd913f39195c7bcfb78c044a197cee24aba7d4826d990756bd3ea0787dcb1cb2/image-20240719-211613.png?cb=0aeccfcd2d247a865a5ca1c5c98ed351) ## **Disposition Inbox** The default view in the Dispose section is your inbox where you can only see records in your Inbox that have reached their expiration date, and for which you have Disposition Authority. This means records for which you can approve the disposition. In the bottom right corner of your screen there is a count of the total number of records in your Inbox. To see all the records in Gimmal Records that have reached their expiration, including records you do not have authority for, click [**Expired Records**](https://docs.gimmal.com/rm/Cloud/Cloud/expired-records) in the left navigation bar. Now you will see every record that has reached expiration. The count in the bottom right corner may differ from your Inbox count due to: * Records in a Disposition Approval workflow assigned to a different records manager * Records in records classes you do not have disposition authority for ## **Disposition Workflows and Approvers** Disposition [Approval workflows](https://docs.gimmal.com/rm/Cloud/Cloud/approvers) can be defined in the File Plan menu for any record class or record category. You can see if a record is part of an approval workflow by clicking the pull-down menu to the right of the record and selecting **Approvals**. You will see the list of previous and future approval steps. ![image-20240719-211736.png](https://kb.gimmal.com/__attachments/a_f61ec8bcb14868b0b27148987dd86d65c5b9aab135e8e0a0298d4b22b8c693fe/image-20240719-211736.png?cb=401df03e1d0ac749fa9b168752ee6c7d) ## **Approving Disposition** To approve a single record for disposition, select the pull-down menu to the right of the record and select **Approve \& Submit.**Gimmal Records will either submit the record for disposition or move it to the next stage of the approval workflow. Multiple records can be [selected for approval](https://docs.gimmal.com/rm/Cloud/Cloud/approving-records) by clicking the check boxes to the left of the record. When you are done selecting records, click the **Approve** button at the top of the page. Approved records display a check mark indicating their approval. ![image-20240719-211938.png](https://kb.gimmal.com/__attachments/a_1d7943aedd50f4d4341606089daf2f06c44183279cfa83291801901ebaa07d8b/image-20240719-211938.png?cb=746abb093d97bbc38beac99bdfd214a1) To submit the records for disposition processing, click the **Submit Approvals** button in the upper right of the screen. ## **Exploring Alternatives** Perhaps you are not sure if a record is ready for disposition. You have two options to choose from. The first is to Pause the disposition process using the appropriate button at the top of the view. This action sets the record aside for a period of time. It's removed from your Inbox while it's paused. The amount of time depends on what is configured in the records [retention lifecycle](https://docs.gimmal.com/rm/Cloud/Cloud/lifecycles). ![image-20240719-212029.png](https://kb.gimmal.com/__attachments/a_3e6c7446bd0453227a938e4ed230c6087eba56554bc0e4d87c5a8591e39d1ced/image-20240719-212029.png?cb=1516d727ef962de6c7c4934279af7a1d) The second is the Reject the record for disposition. To reject a record, you select the pull down menu (or the check box) and then select **Reject** . Upon rejection, the record is moved to the Expired Records area where it remains until action is taken on the record. To see the rejected records, simply click **Rejected Records** on the left navigation. To act on the rejected record, click the pull-down (or check boxes) and select one of the following: * [Reinstate](https://docs.gimmal.com/rm/Cloud/Cloud/rejected-records#id-(Cloud)RejectedRecords-ReinstatingRecords) -- moves the record back to the Inbox for disposition processing * [Classify](https://docs.gimmal.com/rm/Cloud/Cloud/legal-holds-and-reclassification-during-dispositio) -- lets you reclassify the record to a new record class. The record has it's expiration date recalculated based on the new record class lifecycle * [Legal Hold](https://docs.gimmal.com/rm/Cloud/Cloud/legal-holds-and-reclassification-during-dispositio) -- adds the record to a Legal Hold, suspending it's disposition while on hold Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published January, 2024* --- language: "en" --- # Education Sessions (Discover) Gimmal regularly hosts sessions to educate users on topics associated with our products. Please review the topics below to view the sessions available for Gimmal Discover: * [Identifying sensitive data \& ROT](https://www.youtube.com/watch?v=33fN69qMtBg&t=32s) * [Email Retention policies](https://youtu.be/lxp83SSRBgg) * [Data Classification](https://www.youtube.com/watch?v=_RQFdV7MZ88) * [Search syntax \& complex searching](https://youtu.be/bvYfPaQ2fco) * [Endpoints](https://youtu.be/kBVUOld3QAw) * [eDiscovery Searching](https://youtu.be/i4HyuzOKPQg) * [Report Building \& Advanced Options](https://youtu.be/QhDHulGX06k) * [Workflow Builder: Part 1](https://youtu.be/_jEOSmQevpY) * [Workflow Builder: Part 2](https://youtu.be/_dD42xBFvSM) * [Interpreting Log Files](https://youtu.be/6K9MPJUSr3g) * [Assessing RIOT Data](https://youtu.be/bhWQ3hKuCgI) * [Email Compliance \& Retention Policy Enforcement](https://youtu.be/rQpY7iW8HXM) * [AI Readiness](https://www.youtube.com/watch?v=aMYFmARfkfc) * [Breach \& Beyond: Session 1](https://youtu.be/5m2RJ2AhTrw) * [Breach \& Beyond: Session 2](https://youtu.be/TrkT6a6-GOE) --- language: "en" --- # Education Sessions (Physical) Gimmal regularly hosts sessions to educate users on topics associated with our products. Please review the topics below to view the sessions available for Gimmal Physical: * [Conditional Field Display](https://youtu.be/P__Ua_qtdRs) * [Data Focus (Creating, Updating, Deleting)](https://youtu.be/vgtYbXX5bIA) * [Disposition Workflows](https://youtu.be/D6ZHo7rYtHs) * [eDocs](https://youtu.be/owq_zrfKzlE) * [Importing Records](https://www.youtube.com/watch?v=1gTVLThxIUA) * [Legal Holds](https://youtu.be/GOOm2uVEUhI) * [List Values](https://youtu.be/s9tab68F6VA) * [Notifications](https://youtu.be/ISF6BDJ4q78) * [Preferences](https://youtu.be/PdAfa1Rh2to) * [Records Requesting](https://youtu.be/sH-OQvEG_tM) * [Sequencing](https://youtu.be/6tAynuo3pQc) * [Synonyms](https://youtu.be/6cOLWndICDk) * [SQL Operators and Searching](https://youtu.be/k5Oon0bUISY) * [Transferring](https://youtu.be/anbHguzuWt4) * [UI Configuration](https://youtu.be/tOQybtDQszY) --- language: "en" --- # Education Sessions (Records) Gimmal hosts monthly live sessions to educate users on a variety of topics associated with our products. Please review the topics below to view the sessions available for Gimmal Records: * [Managing the Disposition Box](https://youtu.be/XOtA65p9S3A) * [Custom Dashboards / PowerBI Reporting](https://youtu.be/DBCXiFr-8VE) * [Creating Record Classes and Categories](https://youtu.be/B_OQj4t0kY8) * [How Approval workflows work](https://youtu.be/pWueZDLiYAw) * [Managing File Shares](https://youtu.be/U6Uzv9vxhDI) * [Managed Properties and Rule Sets](https://youtu.be/4GZsekaicxw) * [Inbox: What's New?](https://youtu.be/V4h1t114YNE) * [Managing and Using Legal Holds](https://youtu.be/4Y_IHAscaU4) * [How Records and Discover Work Together](https://youtu.be/R_gHuwh7sD0) * [Applying Records Policy to Emails](https://youtu.be/EuUECC_N4Rc) * [Rule Based Retention](https://youtu.be/NcHF8FEB-lQ) * [Why Deletion is as Important as Retention](https://www.youtube.com/watch?v=qfV_i5pNgKU) --- language: "en" --- # Enabling TLS 1.2 As a security best practice when using the .NET Framework, Gimmal recommends that you enable Transport Layer Security (TLS) 1.2, which provides communications security for client/server applications. To enable TLS 1.2, you must add the following Windows registry settings to the Records Management Core server(s) and the servers of any Records Management connectors you are using (if applicable), and then reboot your system. * HKLM:\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319 "SchUseStrongCrypto"= dword:00000001 * HKLM:\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319 "SystemDefaultTlsVersions"= dword:00000001 * HKLM:\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319 "SchUseStrongCrypto"= dword:00000001 * HKLM:\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319 "SystemDefaultTlsVersions"= dword:00000001 Note that some operating systems require additional steps to enable TLS 1.2. For more information, see [Microsoft's TLS documentation](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions) To verify that your operating system supports TLS 1.2, read the [Support for TLS 1.2 section of Microsoft's documentation](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#support-for-tls-12). --- language: "en" --- # Enhancing Information Flow with Email Notifications Want to improve the information flow within your records management program? Consider email notifications. Gimmal Physical allows you to configure a variety of notifications, automatically triggered when certain actions are taken. These notifications can enhance communication and ensure that relevant parties are always informed. ## **Benefits of Notifications** * **Improved Communication**: Ensure that records management personnel, end-users, and supervisors are kept informed about key actions and changes. * **Enhanced Accountability**: Keep track of records requests, deletions, and approvals, ensuring accountability throughout the records management process. * **Efficient Records Management**: Streamline operations by automating notifications for critical actions, reducing the need for manual follow-ups. ## **Configuring Notifications** ![att_1_for_451772474.png](https://kb.gimmal.com/__attachments/a_b38df12bf064880c486731e40ab44f0e558fe22570e66e55efa6a4e9e0772873/att_1_for_451772474.png?cb=e1d10c7740a8a2a28f0e65abbd7b2eb1) 1. Navigate to **Admin \> Configure Notifications**. 2. Select the type of notification you want to configure (see below). 3. Choose the appropriate action and specify the recipients. ## **Types of Notifications** ### **Box Expungement Notifications** : * **Purpose**: Alert administrators when boxes are expunged. * **Recipient**: Administrators. ### **Pending Approval Notifications** : * **Purpose**: Notify administrators when a box has the Box Status field set to '2 - Pending Approval'. * **Recipient**: Administrators. ### **File Deletion Notifications** : * **Purpose**: Send a notification when files are deleted. * **Recipient**: Administrators. ### **Post Due Box Notifications** : * **Purpose**: Inform administrators when boxes in their possession are past due. * **Recipient**: Administrators. ### **Box Request Fulfillment Notifications** : * **Purpose**: Notify general users when a request for boxes is performed. * **Recipient**: General users. ### **Box Fulfillment Notifications** : * **Purpose**: Send a notification when requests for boxes are fulfilled. * **Recipient**: General users. ### **Box Request Notifications** : * **Purpose**: Alert administrators when another user requests boxes in their possession. * **Recipient**: Administrators. ## **Notes and Important Items** * **Important**: Regularly review and update your notification settings to ensure they align with current operational needs. * **Reminder**: Test notifications to confirm they are being sent and received as expected. * **Tip**: Use specific and clear descriptions for each notification type to avoid confusion among recipients. By leveraging the notification capabilities in Gimmal Physical, you can ensure that your records management processes are more efficient and responsive. --- language: "en" --- # Enhancing User Experience Through Preferences Adjusting the preferences in Gimmal Physical can significantly improve the end-user experience. These settings allow you to tailor the interface and its behaviors to better suit the needs of your user base. ## **Wildcard Behavior** Tailor search functionalities with options like 'Auto Beginning and Ending Wildcard' to streamline finding records in the quick search. ![att_3_for_370147355.png](https://kb.gimmal.com/__attachments/a_88cbcb9866c0964fb9de54f826a6e953ec2fd20d93415663518295aaebe2c8dd/att_3_for_370147355.png?cb=b5b5f350f1f31f7abbf90a15ac6d5be9) ## **Records per Page Limit** Configure how many records appear per page for easy viewing. ![att_1_for_370147355.png](https://kb.gimmal.com/__attachments/a_6cd56ae466b68d1b6c8befe8273ec9d3ca2981173a62284b1757d484bdae138c/att_1_for_370147355.png?cb=daf0ac7dd29c769fe8361b726da82f9b) ## **Default Locations** Set up default locations for current, home, transfer, and request operations to speed up day-to-day tasks. ![att_4_for_370147355.png](https://kb.gimmal.com/__attachments/a_cdaac96bb659130eb54ad0623131e0cc69fae1f26d76cb7bcd34700a53fac99a/att_4_for_370147355.png?cb=4ba4b39d6f8c3d539eb58fbec59e4a30) ## **Scope Settings** Determine whether a preference applies system-wide, by user role, or for individual users to provide a consistent or customized experience as required. Experiment with various settings and combinations under each category to create the most effective environment for your users. ![att_2_for_370147355.png](https://kb.gimmal.com/__attachments/a_1857cb85de06011f63924e1eb743de7c683322d3642a7fa864d3edd960121292/att_2_for_370147355.png?cb=45d8d713a36ff5cc0c941de9785dcf7f) Don't hesitate to contact [++support++](https://kb.gimmal.com/kt/contact-information)if you have any questions. *First published April, 2024* --- language: "en" --- # Environment Health Check It is often beneficial when starting a new task or project in Discover to quickly review the status of your environment. Connectors and Agents form the core of any environment so checking their status is the most efficient way to do this. Once you are logged in to the console, select the "Administration" module near the top right-hand corner and then on the left-hand side navigation menu, select "Connectors" to bring up the screen below. Alternately, you can click on "Connectors" on the Main Menu Grid after logging in. ![image-20230421-213534.png](https://kb.gimmal.com/__attachments/a_efda6e9be7b66704514d77e6958b852d295e918f300c7109a659f63d1d779f40/image-20230421-213534.png?cb=1fd7efacba1bc6149ebcb527026b8c8c) Connector Summary showing Column Headers ++**Column Headers and Definitions:**++ 1. **Connector Name**- Shows the name of your installed connectors - i.e., your Computer Name on the Windows Domain. 2. **Version**- The current version of Discover installed on the connector - if "Update Available" is displayed, that connector is not on the latest version of the software. 3. **Auto Updates**- Shows whether automatic updates are enabled. 4. **Assembly Version**- A detailed version number of the Discover installation including mid-release updates. 5. **Category**- Whether the connector is designated as a server or desktop. 6. **Sources**- The number of Data Sources assigned to this connector - e.g., EWS/M365 Mailboxes, .PST Files, SharePoint sites, etc. 7. **Targets**- The total number of Data Targets assigned to this connector across all Data Sources. 8. **Owners**- The total number of Data Targets assigned to this connector that also have Data Owners assigned - Needed for assigning Targets by email address. 9. **Last Updated**- The last time that the connector has checked in with the hub where Discover is hosted. ++**Performing the Health Check:**++ 1. **Verify the version is current for any active connectors**. If "Update Available" is showing, this connector is not on the latest version of Discover and may not have the latest fixes or have other communication problems with the cloud. 2. **Check the "Last Updated" time stamp** to see when the connector has last checked in with the hub server. By default, all connectors check in every 30-60 minutes so this time should be very recent. If this time is more than 60 minutes behind, this could indicate an issue on your connector, network, or even with Discover itself. 1. The most likely reasons that this time stamp would not be current is: 1. The server/desktop is offline or not connected to the network. 2. The security settings in your organization may have a firewall rule blocking access to https://discover.gimmal.cloud/. You can test this by entering that URL in a browser and confirming if the site can be reached. If you receive an error with our URL but can reach other sites, please contact your company's Network Administrator or Help Desk to confirm they allow connections to our site. 3. If either of the above are not the cause, try restarting the server/desktop and seeing if it updates within 15 minutes of rebooting. 3. **Review the status of your agents** - from "Configuration"-\>"Connectors", select "Agent List" from the orange "More" drop-down menu. If you select an individual connector prior to choosing "Agent List", the browser will show you only the agents installed on that particular connector. ![image-20230426-173324.png](https://kb.gimmal.com/__attachments/a_33abc91846bd346fe659fae1351b12d8e9f756e2a4aa257e663ef9b093b87c7d/image-20230426-173324.png?cb=0ba536c594f1a7c797bfb7ef0beb47ba) Agent List selection from Configuration-\>Connectors Once your agents are displayed, you can review what Connector (item 1 in Agent Summary below) the agent is installed on, what type of agent (2) it is and what data it handles, and the current version of the agent (3). You can also see if the agent is available for work in the "Status" (5) column and the last time that it checked in with the hub server (6). As with the connectors above, the most important items to review in the context of a health check are the agent version (3), the agent's current status (5), and the "Last Updated" time indicating last check-in with the hub (6). ![image-20230426-152009.png](https://kb.gimmal.com/__attachments/a_ffdfc10518c4a7ed75553d8ab7514047f8d3d595dff3cf32bba15e6dfbb17e47/image-20230426-152009.png?cb=bb7fc56a76066725f84e1b61434b7eff) Agent Summary If during your health check you have any questions/concerns based on the information you are seeing, contact us at [support@gimmal.com](mailto:support@gimmal.com) and a ticket can be opened to assist you further. --- language: "en" --- # Error Messages: Causes and Resolutions * [System.Exception: There was a problem getting people from the AD organizational unit...](https://kb.gimmal.com/kt/system-exception-there-was-a-problem-getting-peopl.md) * [Web service communications error(31): There was no endpoint listening at https://discover.gimmal.cloud/saigws](https://kb.gimmal.com/kt/web-service-communications-error-31-there-was-no-e.md) --- language: "en" --- # Errors --- language: "en" --- # FAQs (Records) Please refer to the notes or articles listed below for the answers to frequently asked questions. If you have further questions, please [contact support](https://kb.gimmal.com/kt/contact-information). ## General Questions ### What is the difference between a document and a record? Aren't they the same thing? * Strictly speaking, a record is an entry you see in Gimmal Records that, in turn, links to a document (the thing that is being managed). Although the UI in the Manager Web includes all associated metadata of, and a clickable link to, the document, the two terms are not synonymous. Another common point of confusion - there can be an additional distinction between a record (an important document that is subject to records' retention requirements) and a Record (a document that has been declared a record and made immutable as a result). If/when in doubt, it is best to ask for clarification. ### What information does Gimmal Records store? Does it store sensitive information? * For both SaaS and on-premises implementations, Gimmal Records will store the metadata, which is information about the document, but not the document itself. If a document stores sensitive information, Gimmal Records will be unaware of it. ### Why didn't my invitation for Gimmal Records arrive? * Please see . ### What is the order of precedence for classification rules? * For a record that matches the classification rules of multiple record classes, it will be classified to the record class with the highest priority (1 is a higher priority than 100). Record classes have a default priority of 100 that can be changed at any time to any value equal to 1 or greater. If all priorities are equal, the record is classified into the first record class whose classification rules match. ### Is there a way to bulk-update record classes? * Some record class properties can be inherited by child record classes as long as those settings are configured on the parent before creating the children. * Inherited by children of case-based record classes: * Archive Record Details * Archive Record Properties * Archive Record Audits * Destruction Certificates * Record Declaration Rule * Vital Rule * Approvers * Permissions * Lifecycle automatically applies to cases (i.e., the children of case-based record classes) and cannot be set uniquely for each child. * Inherited by children of non-case-based record classes: * Archive Record Details * Archive Record Properties * Archive Record Audits * Destruction Certificates * Record Declaration Rule * Vital Rule * Approvers * Permissions * Lifecycle - if the lifecycle of the parent is changed, the child record classes' lifecycles are updated. ### Why don't my documents appear in the Manager Web? * There could be several different reasons for this, depending on what repository the documents are located within (Filesystem, SharePoint, etc.). Please refer to for more information. ### Does Gimmal Records support Single Sign On (SSO)? * Yes, Gimmal Records supports SSO for our SaaS clients. Gimmal Records uses Azure AD External Identities B2B Collaboration for authentication. On a user's first login, Gimmal Records redirects the guest user's authentication request to their "home" Azure AD tenant for authentication. Gimmal does not store users' credentials. ### How can I see/understand what is happening with Gimmal Records, or its Connectors? * Please refer to for more information. ### How do I know if my Client Secret has expired? * When the Client Secret for the SharePoint Online Connector expires, it can become apparent in several different ways. Please see for more information. ### What is the*Recent Records* view for in the Manager Web Dashboard? * The Recent Records list on the Dashboard corresponds to the 20 most recently ingested documents by Gimmal Records. ### Where can I find the application logs? * The log files for the core application and each of the connectors are generally created in the installation directories for each of those components, usually similar to: * **Core Application**: C:\\Program Files\\Gimmal\\Records Management\\Logs * **SharePoint Online Connector**: C:\\Program Files\\Gimmal\\SharePoint Online Connector\\Logs * **Universal File Share Connector**: C:\\Program Files\\Gimmal\\Universal File Share Connector\\Logs * **Box Connector**: C:\\Program Files\\Gimmal\\Box Connector\\Logs * Due to the way they are installed, some logs are generated in other locations: * **SharePoint Server Connector** : Product may be referred to as *RecordLion-Records Manager* ### Why aren't my records being classified (correctly)? * Please refer to ### How can I clean up/remove records in Gimmal Records (e.g., after testing)? There are a few ways to remove records from the Manager Web, depending on your goal: * Remove test documents and recordizations, method 1 - Delete the documents in their native location. The connector for that location will process the deletion and remove the corresponding recordization entries from the Manager Web. Gimmal Records will continue to manage this location until the location is unregistered from the appropriate connector. * Remove test documents and recordizations, method 2 - Create a record class with a lifecycle that immediately disposes and deletes the records, and ensure your test records (only) are classified to it (you can classify them manually or using Classification Rules). When the Dispose and Delete action is executed, the test documents will be removed from their repository, and the corresponding recordizations will be removed from the Manager Web. Gimmal Records will continue to manage this location until the location is unregistered from the appropriate connector. * Keep test documents and remove recordizations, unregister method * **SharePoint Online Connector** - Navigate to the site contents of the desired site collection and access the SharePoint Online Connector app. Click the button to **Unregister** . The test documents will remain on the site, and the corresponding recordizations will be removed. Note: Any locking actions (record, vital declaration, or legal holds) will NOT be undone. * **Universal File Share Connector** - On the server where the connector is installed, open the Gimmal Universal File Share Connector Configuration utility. On the Servers tab, remove the managed location corresponding to your test documents, and save the configuration. Note that any locking actions (record or vital declaration, or legal holds) will NOT be undone. In addition, ALL records in the Manager Web corresponding to the documents in that managed location will be removed. ### What file share repositories are supported in the Universal File Share Connector - e.g., NFS, mapped drives, etc.? * In general, any file share repository that emulates NFS should work. It must be navigable via a UNC path. ## Destruction Certificates ### When are Destruction Certificates created? * Gimmal Records provides a basic Destruction Certificate. This Certificate requires a Record Classes Destruction Certificate setting to be set to **Yes,** and that the Lifecycle attached to that Record Class requires approval in its final phase. For more information, please see [Destruction Certificates](https://kb.gimmal.com/kt/destruction-certificates) ### Can the Destruction Certificate include the record URI? * If the Archive Record Details record class property is enabled, then the out-of-the-box Destruction Certificate Records report can include the URI. If you view the destruction certificate via the Dispose page in the Manager Web, the URI can be displayed separately from the certificate. ### What happens to the PFX after it is uploaded to SPOC? While in Gimmal's environment, the data is fully encrypted at rest (in the database) and in transit. No .pfx file exists on the server. The PFX content is stored in the database using this process: 1. The PFX file is read into memory and validated 2. The complete PFX binary content(which includes both the public certificate and private key) is re-exported in PFX format as a binary byte array 3. That binary data is encrypted using AES-256-GCM encryption 4. The encrypted binary data is Base64-encoded (converted to text) 5. The text is stored in your tenant's SQL database and is: 1. Encrypted using military-grade AES-256-GCM encryption 2. Stored as text (Base64) 3. Indexed by the certificate's thumbprint for retrieval 4. Never written to disk as a file --- language: "en" --- # File Plan Visual Indicators Central to the architecture of Gimmal Records are the Record Classes. And as would be expected in a records management solution, everything revolves around them. When fully configured, a record class consists of multiple components essential for applying records retention policy and facilitating disposition approval. But did you know, especially for the visual learners among us, Gimmal Records provides a handy set of icons for quick reference, indicating just how configured the record class is? Especially helpful when first building your file plan, the icons can be used to alert you to what still needs to be configured. Each icon may be clicked directly, or may also be found within the dropdown menu for the class. ![att_7_for_597721362.png](https://kb.gimmal.com/__attachments/a_c54669cd2fe484190b498cbc80b908e0ad757d262387bfcc1e40a2ad9f4ffcb9/att_7_for_597721362.png?cb=e7917b3209855c8e92b28949ffd4ac77) ## **⚙** ++**Classification Rules**++ Gears indicate logical rules have been configured, enabling the Gimmal connectors to auto-classify content into this record class. ![att_1_for_597721362.png](https://kb.gimmal.com/__attachments/a_e064beb206cd01f0a4bb49ae7c3b6b016da59092b2aa7a02966421e91323c936/att_1_for_597721362.png?cb=94f96de8a982caadd006127f5c5dd38e) ## **📆** ++**Lifecycle**++ The calendar icon indicates that a lifecycle, consisting of one or more actions, stands ready to apply a retention policy to records within this class. ![att_2_for_597721362.png](https://kb.gimmal.com/__attachments/a_266c2f64ac9873d08503259548625521002df1f9b8e9d28d2d64a2337ac05da3/att_2_for_597721362.png?cb=23ead9c0e7a414a7454acc522416d482) ## **✅** ++**Approvers**++ The checkmark indicates that approvals are required before records in this class can be dispositioned. ![att_3_for_597721362.png](https://kb.gimmal.com/__attachments/a_9eed5cef78dd4768ca3dab6f562444b0af45dc6debb38f16fe062db44241a592/att_3_for_597721362.png?cb=7496033a30e48c3b0b6ac2ff2be8f559) ## ++**📥 Inbox View**++ The inbox icon means specific metadata properties will display in the Disposition Inbox when records are ready for review --- helpful for surfacing key context. ![att_4_for_597721362.png](https://kb.gimmal.com/__attachments/a_defdd911c5314becede7026d0bb8a924a488f42bf80f78474e93986295c4d4df/att_4_for_597721362.png?cb=85eff19c2038c8f81a1348fd7eb0413d) ## **🔐** ++**Permissions**++ Want to restrict what users can do with records in this class? The lock indicator specifies that one or more individuals or groups have been configured with View Properties and/or Declare rights for records within this class. ![att_5_for_597721362.png](https://kb.gimmal.com/__attachments/a_20f231bd21342cd706925ba447e8e4666c590e85110ba849222788dc19ddac9d/att_5_for_597721362.png?cb=4063761408af89cc88624a8dc338f058) ## **👁️** ++**Filters**++ The eye icon tells you that visibility filters are in place, restricting which users can see records within this class. ![att_6_for_597721362.png](https://kb.gimmal.com/__attachments/a_446581faa13464fc402259db2ead688227fbd1b32c25e815b8a65fbefe45b807/att_6_for_597721362.png?cb=f8d2a7fc5c5ea93a13e75ca0fde6e74c) Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published April, 2025* --- language: "en" --- # Filters in Gimmal Records If you have multiple Records Managers, Filters allow you to control what records each Records Manager can view or approve. By default, Records Managers see all record classes. By using Filters on a record class, you can restrict (or filter) the ability to view records in the record class to a specific user(s). ## Manage Filters To manage Filters on a record class, click on Plan in the ribbon. Once you are in Plan, select Record Filters in the left hand navigation pane. ![image-20240719-213450.png](https://kb.gimmal.com/__attachments/a_5afa684e37de3d14364bed22adb64790522940df6965b3e1eea0ae2b4e91a91e/image-20240719-213450.png?cb=8a53a4f303c7d924fc9a54f42cd80bfc) ## **Configuring Filters** The first step in using Filters is to configure the settings for the Filter. Click the +Create button and give your new Filter a descriptive name. Your new Filter will show up in the list of Record Filters. Now that we have a new Filter, we need to configure it. We will need to set up the group membership and the rules for the Filter. Click the pull-down menu next to your Filter name. ![image-20240719-213547.png](https://kb.gimmal.com/__attachments/a_69edd88f442c5a87e1d3bfd9878da330f63f7b7a0c6c2b3bfb0345fe06bc1491/image-20240719-213547.png?cb=2d08a5b4abfb1350f3c7baa3a9206ff1) * The group membership controls what Gimmal Records users are part of this filter. Any users in the filter group can view records the filter is applied to. * Filter rules are similar to Classification Rules. They allow you to set up a rule set, using the record properties, which identifies what records are under this filters control. ### **Group Membership** Use the pull-down menu to select individual users or groups in Gimmal Records. Select the user and then click +Add. Only users in your Group Membership will be able to view records the filter is applied to. ![image-20240719-213729.png](https://kb.gimmal.com/__attachments/a_e74508395c832654d3e2606ec23105e64d5d6eb06660e475615af0e6325c511a/image-20240719-213729.png?cb=869ee3b07b7aee1d6393cc919839b0c2) Users can be removed from the Filter Group by clicking the trashcan to the right of their name. ### **Record Filter Rules** The rules allow you to specify what records are under the control of this filter. In this example, we'll set up a rule that includes any record in the Legal SharePoint site that is in the Contracts library and the metadata property Contract Type is not Real Estate. ![image-20240719-213804.png](https://kb.gimmal.com/__attachments/a_9bdbbd0bd0fe2f39cae8e69b4c2ea41d0bf9fb6f42c9c051870efed4ddf3ca2b/image-20240719-213804.png?cb=cb0074ca4394de647cf81da7a97848af) This rule applies the filter to records in a specific location. Now only Rebecca and Roger will be able to view Contracts Records in this location with one exception: if a contract is in this location and it's a Real Estate contract, any Records Manager can view it. A filter does not have to be location specific. Here we removed the SharePoint site and library requirement. Now any record with a content type of Contract that is not a Real Estate contract will be controlled by this filter. The records can be anywhere in SharePoint! ![image-20240719-213825.png](https://kb.gimmal.com/__attachments/a_a69b9d277c8cae60f42728233d89b14860a46e8643030403e3305329df17ceed/image-20240719-213825.png?cb=44e05f1b1f98ba77af5f295f81067724) ## **Applying the Filter** Filters have to be applied to each record class you want them to apply to. They do not inherit from the parent record category. To apply a filter, go to Record Classes in the left hand navigation, then navigate to the specific record class you want to apply your filter on. Click the pull-down menu for the record class and select Record Filters at the bottom of the menu. ![image-20240719-213906.png](https://kb.gimmal.com/__attachments/a_4895de8eebdf93e8946e752817529b81fc18834731aa44f22563f7462019d21a/image-20240719-213906.png?cb=c9a399985cf6bdcbab3a86061b83cacc) ![image-20240719-213947.png](https://kb.gimmal.com/__attachments/a_ec557977beb0df107a0dd14a156845b20313d17fbd0fa1eb2413bb09101d4ce1/image-20240719-213947.png?cb=33019943d4a3cd2fb1c016506a0e495b) From the pull-down menu, select your filter and click +Add. You can apply multiple filters to a record class if desired. When a filter is applied, you will see the ![image-20240719-214040.png](https://kb.gimmal.com/__attachments/a_107bc438ed588d91d240c2d6d7bd87c35c00244cafabc2a8b94f3c5cc6eb21b1/image-20240719-214040.png?cb=1e5f5b749c6a8535f3c04a8aa495168f) icon next to the record class name. To remove a filter, click the trash can next to the filter name. Please contact [technical support](https://kb.gimmal.com/kt/contact-information) with any questions. *First published April, 2024* --- language: "en" --- # Finding Conversations between Addresses When performing an e-Discovery search, you may need to find conversations between two or more persons of interest. Discovery Attender has several options to assist with these types of searches. ## Wizard Based Filters The Discovery Attender Search Wizard provides several options to search for conversations between two addresses using either the Find Conversation Between Any Two Addresses option or the Find Conversation Between Different Sender and Recipient option as seen below: * "**Find Conversation Between Any Two Addresses**" Option requires that the sender and at least one recipient must be in the address list. * **"Find Conversation Between Different Sender and Recipien**t" Option locates results where the sender is from one list and at least one recipient is from the other. These options may not always be ideal. For instance, * If your custodians are in the habit of copying themselves (CCs or BCCs) on an email, it may generate a false-positive hit. * If one of the addresses belongs to the custodian whose email you are searching. In this case, all messages in those data stores will be to or from that address leading to redundant searching. To correctly search in this instance, it is more efficient to use the correspondent's addresses in a standard address search. To help avoid generating false positives and false negatives due to these factors, you may want to consider breaking down your search into separate searches per number of custodians and addresses being searched: 1. Perform a search against the first custodian's data stores searching for all additional correspondent addresses 2. Perform a search against the second custodian's data stores searching for all additional correspondent addresses 3. ... and so on with any additional custodians For instance, let's say you are trying to find conversations between John Doe, Robert Jones, and Jane Smith, where John Doe and Jane Smith are custodians in my organization. Assuming you want all instances of the conversations between any of these persons of interest, you would first search all of John Doe's mail stores (mailbox, online archive, and/or PST files) for both Jane and Robert's email addresses. For the second search, you will search all of Jane Smith's data stores (mailbox, online archive, and/or PST files) for John and Robert's email addresses, and so on. ## Additional Address Considerations ### Property Options * There are three properties Discovery Attender scans for each address: * Display name (e.g. Jeffrey Lebowski) * Exchange Internal address (e.g. /O=FIRST ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=JeffreyLebowski) * SMTP address (Lebowski @exchangelab.local) Too often, users will enter just the SMTP address in their search criteria and forget that internal communications (especially for sent messages in Exchange-based data stores) often depend on the other properties. To counteract this option, including both the display name and SMTP address for internal senders and recipients will guarantee the most expansive results. ### Wildcards with Addresses When searching addresses in general, please remember that to be considered a hit, the address search terms must match the entire address property text. Therefore, the use of wildcards like the asterisk is encouraged. However, pattern matching may not always work with your criteria. If the name is too common, your search will result in numerous false-positive hits. (That is, you probably do not want to search for just \***smith\***). In addition, the Exchange and SMTP addresses may not include the full name either, therefore causing an incomplete result set. To get around this, make sure to verify you have all the address properties using the PreSearch Tool's snapshot option. ### Result Management Filters Although finding a conversation between two addresses is easier using the search wizard, the same result can be achieved using Marks and Filters with the Address view in the Result Management Screen. ![att_1_for_452231170.png](https://kb.gimmal.com/__attachments/a_d7c24d7a4aa6c622cb594068c59639ef200f265569579e17aaf79690f86a9594/att_1_for_452231170.png?cb=934cb092bd03f6d95f881ae24a330e88) Don't hesitate to contact [support](https://kb.gimmal.com/kt/contact-information)if you have further questions on searching for conversations in Discovery Attender. *First Published July, 2024* --- language: "en" --- # Gimmal General --- language: "en" --- # Gimmal Migrate * [User's OneDrive Documents Library does not appear in MAPIT](https://kb.gimmal.com/kt/user-s-onedrive-documents-library-does-not-appear-.md) * [Gimmal Migrate Frequently Asked Questions](https://kb.gimmal.com/kt/gimmal-migrate-frequently-asked-questions.md) * [Override Key Registration](https://kb.gimmal.com/kt/override-key-registration.md) * [Connection settings information for Content Server](https://kb.gimmal.com/kt/where-can-i-find-the-connection-settings-informati.md) * [Whitelisting IPs for Migration jobs](https://kb.gimmal.com/kt/whitelisting-ips-for-migration-jobs.md) * [Azure Storage Account access](https://kb.gimmal.com/kt/azure-storage-account-access.md) --- language: "en" --- # Gimmal Migrate Frequently Asked Questions * Why does my Gimmal Migrate product tell me my license is invalid? * If you have been using the product for some time successfully, the most likely causes are that the license has expired, or that the designated number of instances has been exceeded. * If this is the first use of the license key and it fails to register, it may be possible that the license server is inaccessible from your location. Ensure the Migrate tools have outbound internet access. If Internet access cannot be enabled, please contact Gimmal or your account manager to obtain an override key. * What permissions do I need to use Gimmal Migrate? * **Exporting from Documentum** : As a best practice to ensure no content is missed -- use of a Documentum Superuser account is recommended where possible. The [product documentation provides the minimum requirements](https://docs.gimmal.com/migrate/documentum-exporter-version-2-x). User account should have admin or superuser privileges. User account must be a member of Local Users and Groups in Documentum server. * **Exporting from Content Server**: As a best practice to ensure no content is missed -- grant System Administration Rights to the user/service account so that it can access all RM and PhysicalObject Workspaces. * The first time MAPIT is run, the **db_owner** role is needed for the person running it. Their credentials are required to create the SQL tables that the tool needs. After those are set up, only **db_reader** and **db_writer** are needed. * Additional information for MAPIT can be found here: [Migration API Tool (MapIT) for Microsoft 365 (gimmal.com)](https://gimmal.atlassian.net/wiki/spaces/Migrate/pages/69926913/Migration+API+Tool+MAPIT+for+Microsoft+365) * Can I still access/use my original documents after migration? * Yes, although generally not recommended (best practice is to make the originals read-only), the original documents are not modified in any way. * I don't have SQL Server, IT is still setting it up. Can I use Azure SQL? * No, Azure SQL is not currently supported but SQL Express can be used for testing and initial setup while waiting for SQL Server. SQL Express is not recommended for production migrations. * What Content Server tables does the Content Server Discovery and Analysis tool query? The Gimmal Analysis tool accesses four different database tables in the Content Server database: * DTree * DTreeSub * DTreeAncestors * DTreeACL * How do I turn on Logging for MAPIT? Where are the logs? * Edit the MAPIT configuration file (**Gimmal.Migrate.MAPIT.exe.config** ) and ensure the **EnableMonitorLogging** node is set to **tru** **e** . This file is located with the MAPIT executable in a directory similar to **C:\\Program Files\\Gimmal\\Migrate\\MAPIT**. * ![2023-08-17_16-54-38.png](https://kb.gimmal.com/__attachments/a_bb1a24cca30bd0606736770e332f857622d13ecde1289658ca14452cddf556ed/2023-08-17_16-54-38.png?cb=26f0635ea5f6eedafd4df3aa85dc1616) The Analysis, Migration, and Validation logs are created in the **Packaging and Log folder**path specified in MAPIT in a sub-folder for each migration profile. * ![2023-08-17_16-57-30.png](https://kb.gimmal.com/__attachments/a_542c4895dd55ef7297d9a5d54a3fad734941598e883938cd05406ad2e69d4805/2023-08-17_16-57-30.png?cb=a1dfd1ecbb5a992da9577f7fcf44316f) * Can the Content Server Collections object type be migrated? * No, Content Server Collections are not currently supported. For a current list of supported Content Server object types please visit: * Are Cyrillic or Chinese characters in supported? * Cyrillic/Chinese alphabet should be supported in both Content Server and Documentum. Gimmal has tested a wide variety of language sets and special characters such as Arabic and Japanese. The metadata file created for each export is a CSV file that preserves any language/special characters. We recommend you do not open those CSV files in Excel as this can automatically reformat some characters. * Are there any file size limitations? * There are no built-in limits in the Gimmal Migrate tools. Additionally, your source and target repositories may have specific size limits configured by your administrator. However, a number of variables could affect the performance of your migration and may be exacerbated by significantly large files - e.g., network speed, workstation memory/CPU, SQL configuration, etc. * I'm migrating to SharePoint Online, are content types and metadata columns created during the migration? * No. The content types and metadata need to exist in SharePoint Online prior to running MAPIT. In addition, the metadata properties from Content Server, and those in the destination must be mapped to each other to retain the original metadata values. * We have a FIPS Compliant environment. Will MAPIT work with FIPS? * MAPIT uses an MD5 checksum for migration which is currently required by Microsoft. MD5 is not FIPS compliant - you will need to grant an exception for migration workstations. --- language: "en" --- # Gimmal Physical * [Gimmal Physical FAQs](https://kb.gimmal.com/kt/gimmal-physical-frequently-asked-questions.md) * [Tips \& Tricks (Physical)](https://kb.gimmal.com/kt/tips-tricks.md) * [Education Sessions (Physical)](https://kb.gimmal.com/kt/education-sessions-physical.md) --- language: "en" --- # Gimmal Physical FAQs * Why can't I log in? * How do I export data? * How do I create a new label? * How can I view my pending requests? * How do I set up email notifications? * What does the cart function do? * [What does the cart do?](https://kb.gimmal.com/kt/what-does-the-cart-do.md) * What is the difference between Delete and Expunge? * [Delete vs. Expunge](https://kb.gimmal.com/kt/delete-vs-expunge.md) * What's the difference between requesting delivery and requesting pickup of items? * [Request Delivery vs. Request Pickup?](https://kb.gimmal.com/kt/request-delivery-vs-request-pickup.md) * What is the difference between the Current, Home, and Hub locations? * [What are the Current, Home, and Hub Locations?](https://kb.gimmal.com/kt/what-are-the-current-home-and-hub-locations.md) * Where are my disposition reports? * Why are my labels not printing? * Why aren't my scheduled destruction dates calculating correctly? * Why did my item request get waitlisted? * [Why was my request waitlisted?](https://kb.gimmal.com/kt/why-was-my-request-waitlisted.md) --- language: "en" --- # Gimmal Records * [Tips, Tricks and FAQs (Records)](https://kb.gimmal.com/kt/gimmal-records-frequently-asked-questions.md) * [Tech Tips (Records)](https://kb.gimmal.com/kt/tech-tips-records.md) * [Education Sessions (Records)](https://kb.gimmal.com/kt/education-sessions-records.md) * [Modern Authentication in SharePoint Online Connector (SPOC) Cloud](https://kb.gimmal.com/kt/modern-authentication-in-sharepoint-online-connect.md) [Next Page](https://kb.gimmal.com/llms-full.txt/1)