Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  • Getting Started
    • Explain what this tutorial about
    • By the end of this tutorial...(not sure) - You would be able to write moderate Groovy scripts in JMWE.
  • Basics of Groovy
    • Skip this if you already know Groovy
    • Detail few basic concepts of Groovy
      • if, for, closure, lambda expressions, safe-navigation operator etc
    • References to Groovy tutorials (external)
  • Where do you write your Groovy script
    • Add a post-function/scripted condition/scripted validator of JMWE
    • Select "Groovy expression" option
    • The Groovy editor is displayed - Rough introduction on Groovy editor and reference to its actual page.
  • Tutorial - My first Groovy script
    • Fetch the key of the issue
    • issue.getKey()
    • Provide reference to the issue variable and the getKey() method
    • What do you get as the output - Refer the expected value of each field type document.
    • What can I do with this Groovy script result? - that is a String
      • Either add this as a comment/Set a field that expects a String as input.
  • Tutorial - How to write a condition - The result of a scripted condition is a boolean. It can be used either to Control the execution of a post-function or Control the availability of a condition or Validate the input during a transition.
    • Simple condition - Check whether a text field is empty or not
      • issue variable - Reference to variables documentation
      • Standard field, Access standard field doc reference
      • Custom field,  Access custom field doc reference
      • Compare the value to the required value
        • Use if() or
        • Optimize the code by returning the result of the comparison
    • Check the current user is a specific user
      • currentUser is the variable. - Reference to variables documentation
      • Explain its return value, and how to get the name of the user. -  Reference to User interface
      • Return the result of the comparison to the specific username
    • Check the priority of the issue
      • issue variable - Reference to variables documentation
      • Standard field - Expected input type of this field - Refer expected field type document
      • Issue interface - getPriorityObject() or get("priority")
      • Priority interface - getName()
      • Standard field, Expected field type - Check the priority - Priority object
      • Since it is an object, it has properties to look up to
      • Priority interface- refer
  • Tutorial - Safe access a field - To explain on how to avoid null pointer exceptions

  • No labels