> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/releases/server-plugin/v1.0.md). # v1.0 ## Release - v1.0 Release Date - 08 Nov 2020 Release notes - IZ Analyzer - v1.0 * Task * \[MSQA-1] - Integrate IZ License server into Studio Plugin * \[MSQA-2] - Integrate IZ License server into IZ Analyzer Plugin * \[MSQA-3] - IZ Analyzer analysis shows only configuration level information. Complete project scan to be included * \[MSQA-4] - Studio Plugin to submit mule project to IZ Analyzer server for analysis * \[MSQA-5] - Simplify license management screen in studio * \[MSQA-7] - Missing 'notes' section are highlighted as Major severity. Might be good to have a lower severity level * \[MSQA-8] - Rule to avoid hardcoding * \[MSQA-9] - Generic errors like display name, notes etc. are not coming up for other components like FTP, SFTP etc * \[MSQA-11] - Impose rule to use standard naming convention * \[MSQA-13] - Implement component level design * \[MSQA-14] - Updated rules sheet macro to incorporate component level design * \[MSQA-15] - Rules added to scan project, property, flow components * \[MSQA-16] - Setting up RAML parser to cover RAML rules * \[MSQA-17] - Rule Generation UI to be created for easy rule editing * \[MSQA-21] - Create Common Library that will be used by all core engines of IZ Analyzer * \[MSQA-23] - Lines of Code Calculation * \[MSQA-24] - Test out CircleCI Build for the projects * \[MSQA-25] - Mule Sonar Rules to be created - trying to create a task with subtasks for easy capture * \[MSQA-58] - Development and Naming guidelines for Integral Zone (Across All products) * \[MSQA-59] - Set up Bitbucket Pipelines * \[MSQA-60] - Fix Sonar Bugs and Vulnerabilities * \[MSQA-66] - Rule UI category update * \[MSQA-71] - Refactoring within core engine code * \[MSQA-74] - Sync Rules - IZ Analyzer APIs Basic Authentication * \[MSQA-75] - Add Support For Mule 4.x * \[MSQA-76] - License Validation Fails With Proxy * \[MSQA-77] - Javadoc to core engine classes * \[MSQA-78] - Sonar Server Plugin - Remove .xml Predicate For Mule Extension * \[MSQA-79] - Templates Release v1.0 IZ Analyzer rules * \[MSQA-94] - Documentation around new features * \[MSQA-95] - Integrate Template Rules Functionality - Studio * \[MSQA-96] - IZ Analyzer Analysis - License Server Integration * \[MSQA-105] - UI - Create Organization - Description (missing Tool tip ) * \[MSQA-119] - Document - Override an existing rule using rule template * \[MSQA-127] - Support for adding custom rules * \[MSQA-128] - Studio reload issue in Linux * \[MSQA-130] - Fixes After First Demo * \[MSQA-131] - Property Keys - Get Line Number * \[MSQA-132] - Property File Cache Issue * \[MSQA-133] - API scanner implementation * \[MSQA-134] - Merge API Scanner * \[MSQA-135] - IZ Analyzer - Fetch Project Settings per Project * \[MSQA-136] - Fix - Studio Editor Marker Errors * \[MSQA-139] - Fetch Default System Tags * \[MSQA-160] - API - Add additional rules for RAML/OAS * \[MSQA-167] - GitHub OAuth - Project Creation Issue * \[MSQA-168] - Studio Plugin - Performance Enhancement * \[MSQA-170] - Create Rule - Update documentation with available variables * \[MSQA-171] - CLI Scanner - Error Scanning Non Mule Projects * \[MSQA-177] - RAML GET resources should not have get or query or read when querying a resource * \[MSQA-178] - RAML POST resources should not have save in the resource name * \[MSQA-179] - Create RAML Core Base Engine to cater to RAML language analyzer to be built * \[MSQA-181] - RAML PUT resources shouldn’t have update in the resource names * \[MSQA-183] - SSL Certificate - Update Studio Jar Signer with latest IZ SSL certificate * \[MSQA-184] - Migrate Host - sonar-cloud.integralzone.com to analyzer.integralzone.com * Story * \[MSQA-12] - Component based design to enable engine to scan all moving parts of given project. * \[MSQA-116] - UI - Organization upgrade * Bug * \[MSQA-6] - IZ Analyzer dashboard default project page is empty * \[MSQA-61] - Fix issue with Sonar Scanner URL Location error * \[MSQA-63] - Fix Pipeline build for Sonar Plugin by fixing dependency on core engine properly * \[MSQA-103] - UI - Create Organization - Avatar (Tooltip file formats and Browse to local folder) * \[MSQA-104] - Email Notify - Sent from "Meaning Full" * \[MSQA-106] - UI - Create Organization - URL Missing ToolTip * \[MSQA-108] - UI - On upgrading, still unable to add new project * \[MSQA-109] - UI - Organization Setting - Count * \[MSQA-110] - UI - Organization Settings Specify project Private or Public * \[MSQA-114] - UI - Private - Public count mismatch * \[MSQA-115] - UI - Unable to upload a new project Public * \[MSQA-120] - UI - Browser Compatibility issue on Mac Chrome browser * \[MSQA-121] - IZ-Unable to delete Custom Rule * \[MSQA-124] - UI- Upgrade Payment Gateway invoice * \[MSQA-129] - Studio - scanner additional options * \[MSQA-137] - M00181: XML - All connector configurations NOT in global.xml * \[MSQA-142] - M00023: Logger with a payload or message logging should be in DEBUG/TRACE level * \[MSQA-145] - M00017-HTTPS - Listener HTTP methods are NOT locked down * \[MSQA-182] - IZ Analyzer Plugin - Create a RAML project scanner Plugin * Sub-task * \[MSQA-33] - No Java Rule: No Java code has to be written in mule projects * \[MSQA-35] - Mule Flow: Dataweave should be used to set payload instead of set-payload * \[MSQA-36] - Exception checking shouldn’t use internal class apart from java.\* or javax.\* * \[MSQA-46] - TEMPLATE RULE: Maximum number of flows per mule configuration XML should not exceed 10 * \[MSQA-50] - All Logger components should have a mandatory category in them * \[MSQA-80] - \ APIkit was used to auto-generate an implementation interface * \[MSQA-81] - \ Rule to check implementation logic. * \[MSQA-82] - \ Rule to check exception handling aspects and validations. * \[MSQA-83] - \ Rules to check tools and secured configurations. * \[MSQA-84] - \ Rules to check audit and logging setups. * \[MSQA-85] - \ Rules to check Mule 4 deprecated components usage. * \[MSQA-86] - \ Rules to check correct use of Mule components supporting optimized CPU and memory usage. * \[MSQA-87] - \ Rules to check best use of Mule unit testing. * \[MSQA-88] - \ Rules to check overall security setups covering endpoints, properties and connectors. * \[MSQA-89] - \ Rule to check Mule runtime version. * \[MSQA-90] - Flows should have documentation attached to them * \[MSQA-91] - prefixes for flows, sub flows and private flows * \[MSQA-92] - Dataweave Transformations are always stored in DWL files --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/releases/server-plugin/v1.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.