Checkout this page for the frequently asked questions. Please contact us if you still have more questions.

  • 01

    Who do you think are target users of this tool.

    Anybody or everybody who has an interest in the quality of the code being developed, maintained or supported.

  • 02

    What all I need to review my workflow.

    To start running you reviews, you just need your workflow XML exported from repository manager. You can go to code review page and select any predefined rule profile and run your code review by uploading your workflow XML.

    Once you sign up, you can create your own review profile and start running your project specific code reviews. Your code review results will be stored for historical analysis and accessible from the dashboard.

  • 03

    What are the Informatica components reviewed for violations in the review process by the tool.

    This tool supports the review of all informatica workflow components, which includes workflow, worklet, session, all workflow tasks, mapping, mapplet, reusable transformations, shortcuts.

  • 04

    Can we review multiple objects same time.

    Yes, you can review multiple mappings or workflows at the same time. You should export an XML file from repository manager with all the objects required for review and provide it to the tool for review from review page.

  • 05

    What kind of Rules and Checks are covered.

    There are various rules that we provide. These are based our industry experience and our research and interaction with the ETL Development community. Rules are classified the rules into different categories and criticality. Our rules address a range of categories and criticality including data quality, performance, readability, maintainability etc...

  • 06

    I do not see a rule, which I would like to use in my project. Can I get the new rule added into the system.

    We are continuously working to enrich the rule set available for you. However, if you see any missing rules which is of your project interest, please leave us a note. We will happily include them in the upcoming releases.

  • 07

    Is there any limit for the number of rules that can be added into a code review process.

    You can add as many as rules as you like to a rule profile and run your code review. However, we recommend to limit the number of rules in each rule profile by logically group rules into smaller rule profiles.

  • 08

    Why should I sign up and sign in to tools.disoln.org.

    All signed in users get capability to

       1. Create your own rule profile, accessible just for you.
       2. Customize rule properties to suite your project.
       3. Create a your own ETL team.
       4. Get customized reports.
       5. Assess your team and individual performance.

  • 09

    What all I can do with out sign up and sign in to tools.disoln.org.

    All non signed in users get capability to 

       1. Ability to review your workflow XML.
       2. Use any predefined rule profile for your code

  • 10

    What is a rule.

    A rule is a single best practice. You can pick the rule or group of rules you want your code to be checked against and create a rule profile.

  • 11

    Can I customize the rule to suite my project needs.

    Yes, you can customize the rules while you create your rule profile. Rule profile creation wizard will guide you through the steps to create your rule profile and customize your rules.

  • 12

    What is rule property.

    Rule property is an attribute of a rule, which will help you configure the way each rule suits your project. For example, your project might need to a rule to check that the commit interval is set to 10000, rule property will let you set the rule to have this attribute.

  • 13

    What is rule profile.

    A rule profile is a group of rules or checks that you would like to use to measure your code against. A rule profile can have one or more rules. This is a good way to group rules that perform a particular set of checks.

  • 14

    What is rule Category.

    Each rule or best practice has a reason or area that it will impact if not followed. We refers to them as Category. Examples of Categories are data quality, performance, readability, maintainability etc...

  • 15

    What is rule Criticality.

    Criticality is a way of assessing the impact of violating a best practice. We have classified the criticality as High, Medium, Low and Info.

  • 16

    What happens to my the XML files I upload, after the review process is done.

    We use the XML file uploaded by you just for the review process, we remove the file from our system as soon as the review process is done.

  • 17

    What information about my workflow or XML will be stored in the system.

    If you are a logged in user, we store your workflow name, name of the components in the workflow such as session name, mapping name and different review rules run on the workflow as part of the review process and the outcome of each review. This information is stored in the system to generate dashboard for you.

  • 18

    How is the "team top rule violations" is identified.

    This report identifies the rules which is violated for the maximum numbers for the last 3 months period.

  • 19

    How is the report "team rule violations over 3 months" is build.

    Report is build based on the historical review performed by any one in the team.  We calculate one week rolling average of rule violations by all the team members, which gives a good trending of how the team is performing as a whole. This gives a god idea about how the team is performing over the past three months. This report is only available for logged in users.

  • 20

    How is the report "individual rule violations over 3 months" is build.

    Report is build based on the historical review performed by individuals in the team.  We calculate the one week rolling average of rule violations by individual team members, which gives a good trending of how individuals are performing and how much improvement each team members making over the period of time. This report is only available for logged in users

  • 21

    How is the report "individual rule violations by criticality" is build.

    This report gives a good idea about how individuals are performing in each area ETL area.  Identify individual who needs special attention and training in specific area and help improve the over all ETL quality.

  • 22

    I am getting "504 Gateway Time-out" error why is this ?.

    Our services are running from the free servers provided by openshift which has only limited resources. If you are running code review for large workflows using a review profile having too many rules, there are chances that the server might run out of resources and an error will be thrown. As a solution to overcome this resource crunch, please split your rule profiles into smaller rule profiles containing less number of rules. Thank you for your co-operation.

  • 23

    I am getting "500, server error" why is this ?.

    Most of the time this issue happens when the XML uploaded is not exported from repository manager and all dependent components are not included in the XML. So the code review process is not able to navigate through the workflow XML. Please check in all the dependent components of your workflow and export the workflow from the repository manager and run the code review. If the issue persist please contact us with workflow name and rule profile used to run the code review process.