We just imported our flow from test box to our production box and started our ru

1. The suggestion to update the plug-in was so you can see an exception in the server.log if the plug-in is not printing it out or if you want it to print more information when the constant is not found.

2. You can still make your design compliant with the Dependency Checker without making any code changes. Let me explain how. The Dependency Checker (base product) is based on UUIDs which are unique identifiers for objects within Appian. What makes this plug-in non-compliant with this approach is that it references constants by name and the name is a simple string which could be anything there's no way the Dependency Checker knows that string is a constant name since the plug-in says it expects a simple string.

But that's not a problem:

--->2.1 You can simply create a constant of type TEXT , let's say:

NAME_OF_MINOR_RA_JIRA_CDT_REFRESH_DELAY

---> 2.2 This constant will contain the following TEXT as its value:

MINOR_RA_JIRA_CDT_REFRESH_DELAY

---> 2.3 Change your expression in your timer to be

=rule!getIntConstBasedOnEnv(cons!NAME_MINOR_RA_JIRA_CDT_REFRESH_DELAY)

---> 2.4 This way the Dependency Checker will tell you that you need to include the constant called NAME_MINOR_RA_JIRA_CDT_REFRESH_DELAY. This is still not the relevant constant right? But you can put in the description of this one a warning saying: "ALSO INCLUDE MINOR_RA_JIRA_CDT_REFRESH_DELAY". This way the dependency checker, when alerting about this auxiliary constant can "remind you" through this constant description that you need to include another constant.

You will see this message in the description of this constant once you add it to your application.

1. The suggestion to update the plug-in was so you can see an exception in the server.log if the plug-in is not printing it out or if you want it to print more information when the constant is not found.

2. You can still make your design compliant with the Dependency Checker without making any code changes. Let me explain how. The Dependency Checker (base product) is based on UUIDs which are unique identifiers for objects within Appian. What makes this plug-in non-compliant with this approach is that it references constants by name and the name is a simple string which could be anything there's no way the Dependency Checker knows that string is a constant name since the plug-in says it expects a simple string.

But that's not a problem:

--->2.1 You can simply create a constant of type TEXT , let's say:

NAME_OF_MINOR_RA_JIRA_CDT_REFRESH_DELAY

---> 2.2 This constant will contain the following TEXT as its value:

MINOR_RA_JIRA_CDT_REFRESH_DELAY

---> 2.3 Change your expression in your timer to be

=rule!getIntConstBasedOnEnv(cons!NAME_MINOR_RA_JIRA_CDT_REFRESH_DELAY)

---> 2.4 This way the Dependency Checker will tell you that you need to include the constant called NAME_MINOR_RA_JIRA_CDT_REFRESH_DELAY. This is still not the relevant constant right? But you can put in the description of this one a warning saying: "ALSO INCLUDE MINOR_RA_JIRA_CDT_REFRESH_DELAY". This way the dependency checker, when alerting about this auxiliary constant can "remind you" through this constant description that you need to include another constant.

You will see this message in the description of this constant once you add it to your application.