Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-9476

UX improvements in file listener form


    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-4-4-0-M1
    • Component/s: Server
    • Security Level: Users (General product issues)
    • Labels:
    • Story Points:
    • QA Testing:
    • Sprint:
      BRQ Sprint 21, BRQ Sprint 22, BRQ Sprint 23, BRQ Sprint 24


      When I create a new file event listener, I want to make it working as fast as possible so offer default value everywhere it makes sense. It also helps to understand meaning of field. Also form itself should be robust and work well even for wrong values (currently it sometimes throws an exception).

      Also please revisit label texts (both language and if it is understandable for users).

      This story is basically "make file listeners work".

      Proposal of defaults (feel free to use different):
      Name: FileEventListener
      Protocol: FTP used most of the time
      Authentication type: None does not make sense to have radiobuttons group without selection
      Interval of check in seconds: There is a 0 as a default. What does it mean? Can we put there something? eg. 60 seconds
      Type of check: Ask consultants for most common type of check for non-remote listeners

      Acceptance criteria

      • There are reasonable defaults for fields listed above
      • Form does not produce exceptions for wrong values
      • Form elements work as PO expects


          Issue Links



              • Assignee:
                sedlacekj Jan Sedlacek
                sedlacekj Jan Sedlacek
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: