Uploaded image for project: 'AppFormer'
  1. AppFormer
  2. AF-2517

System error appears when form with unsaved changes is renamed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Hide
      1. Create a data object
      2. Create a form based on the data object
      3. Navigate to Overview -> Metadata
      4. Add a tag
      5. Click "Rename"
      6. Enter the new asset name and click "Rename"
        Expected result: The form is renamed without any issues
        Actual result: There is a system dialog (see attached screenshot)
      Show
      Create a data object Create a form based on the data object Navigate to Overview -> Metadata Add a tag Click "Rename" Enter the new asset name and click "Rename" Expected result: The form is renamed without any issues Actual result: There is a system dialog (see attached screenshot)
    • NEW
    • NEW

      When you try to rename a form with unsaved changes, a system error appears in the business central. Following are the error details:
      "ToSubject":"org.kie.workbench.common.forms.editor.service.shared.FormEditorService:RPC.loadContent:org.uberfire.backend.vfs.Path::153:RespondTo:RPC"} | Uncaught exception: Client-side exception occurred although RPC call succeeded. Caused by: (TypeError) : a is undefined

      The same thing happens with the Guided decision table graph, with the following error details:
      "ToSubject":"org.uberfire.ext.editor.commons.service.ValidationService:RPC.isFileNameValid:java.lang.String::131:RespondTo:RPC"} | Uncaught exception: Client-side exception occurred although RPC call succeeded. Caused by: (TypeError) : this.c._ is null

        1. Screenshot from 2020-05-15 11-37-40.png
          Screenshot from 2020-05-15 11-37-40.png
          30 kB

              eignatow Eder Ignatowicz
              bsiskova Barbora Kapustova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: