This version of the plugin provides 42 quality rules and 10 metrics. Note that not all of the rules will be available by default. Some rules are disabled - as they may not be applicable to all installations - and some are templates. These must be instantiated as required and configuration parameters provided.
| Name | Type | Has Parameters | Initial State | Description |
|---|---|---|---|---|
CustomHardCodedActivity |
Process | No | Enabled | Check if a configuration value is hard coded in a specific activity type |
CustomProcessCatch |
Process | No | Enabled | Check if a custom catch activity is present in process file |
DeadProcessCheckForStarterProcess |
Process | No | Enabled | Check the unused starter process( Dead Code). |
DeadProcessCheckForSubProcess |
Process | No | Enabled | Check the unused sub process( Dead Code). |
HTTPRequestHostHardCoded |
Process | No | Enabled | Check if host is hard coded in HTTP Request Reply activities |
HTTPRequestPortHardCoded |
Process | No | Enabled | Check if port is hard coded in HTTP Request Reply activities |
HTTPRequestTimeoutHardCoded |
Process | No | Enabled | Check if timeout is hard coded in HTTP Request Reply activities |
HTTPRequestUriHardCoded |
Process | No | Enabled | Check if URI is hard coded in HTTP Request Reply activities |
JMSQueueReceiverDestinationHardCoded |
Process | No | Enabled | Check if destination queue is hard coded in JMS Queue Receiver activities |
JMSQueueReceiverMaxSessionsHardCoded |
Process | No | Enabled | Check if max sessions is hard coded in JMS Queue Receiver activities |
JMSQueueRequestorDestinationHardCoded |
Process | No | Enabled | Check if destination queue is hard coded in JMS Queue Requestor activities |
JMSQueueRequestorTimeoutHardCoded |
Process | No | Enabled | Check if timeout is hard coded in JMS Queue Requestor activities |
JMSQueueSenderDestinationHardCoded |
Process | No | Enabled | Check if destination queue is hard coded in JMS Queue Sender activities |
JMSTopicPublisherDestinationHardCoded |
Process | No | Enabled | Check if destination topic is hard coded in JMS Topic Publisher activities |
JMSTopicSubscriberDestinationHardCoded |
Process | No | Enabled | Check if destination topic is hard coded in JMS Topic Subscriber activities |
NoOtherwiseCheck |
Process | No | Enabled | This rule checks multiple transition from an activity at least exists one path for no matching condition |
NumberOfActivities |
Process | No | Enabled | This rule checks the number of activities within a process |
OnlyOneOtherwiseCheck |
Process | No | Enabled | This rule checks multiple transition from an activity only one for the paths are for no matching condition |
ProcessCatchAll |
Process | No | Enabled | Check if a catch all activity is present in process file |
ProcessNamingConvention |
Process | No | Enabled | This rule ensure the naming convention for process names |
ProcessNoDescription |
Process | No | Enabled | Check if a description exists in process file |
RenderXmlPrettyPrint |
Process | No | Enabled | This rule checks for inefficiencies on using tib:render-xml function specifying the pretty-print option to true |
SOAPReceiverSoapActionHardCoded |
Process | No | Enabled | Check if soapAction is hard coded in SOAP Receiver activities |
SOAPRequestSoapActionHardCoded |
Process | No | Enabled | Check if soapAction is hard coded in SOAP Request Reply activities |
SOAPRequestTimeoutHardCoded |
Process | No | Enabled | Check if timeout is hard coded in SOAP Request Reply activities |
SOAPRequestUrlHardCoded |
Process | No | Enabled | Check if URL is hard coded in SOAP Request Reply activities |
SapFileSinkFileCountHardcodingCheck |
Project | No | Enabled | Check hard coded fileCount in FileSink in SAP Adapter file |
SapFileSinkFileLimitHardcodingCheck |
Project | No | Enabled | Check hard coded fileLimit in FileSink in SAP Adapter file |
SapRPCClientSubjectHardcodingCheck |
Project | No | Enabled | Check hard coded Subject in RPC Client in SAP Adapter file |
SharedHttpHardCodedHost |
Project | No | Enabled | Check hard coded host in shared HTTP resource file |
SharedHttpHardCodedPort |
Project | No | Enabled | Check hard coded port in shared HTTP resource file |
SharedJdbcHardCodedPassword |
Project | No | Enabled | Check hard password value in shared JDBC resource file |
SharedJdbcHardCodedUrl |
Project | No | Enabled | Check hard coded url in shared JDBC resource file |
SharedJdbcHardCodedUser |
Project | No | Enabled | Check hard coded user in shared JDBC resource file |
SharedJmsHardCodedJndiPassword |
Project | No | Enabled | Check hard coded JNDI password in shared JMS resource file |
SharedJmsHardCodedJndiUrl |
Project | No | Enabled | Check hard coded JNDI url in shared JMS resource file |
SharedJmsHardCodedJndiUser |
Project | No | Enabled | Check hard coded JNDI user in shared JMS resource file |
SharedJmsHardCodedPassword |
Project | No | Enabled | Check hard coded password in shared JMS resource file |
SharedJmsHardCodedUrl |
Project | No | Enabled | Check hard coded url in shared JMS resource file |
SharedJmsHardCodedUser |
Project | No | Enabled | No description available. |
TransitionLabels |
Process | No | Enabled | This rule checks whether the transitions with the type 'Success With Condition' (XPath) have a proper label. This will improve code readability |
XPathCheck |
Project | No | Disabled | This is a template rule that allow to add custom XPath Checks if required |