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

System error appears when form with unsaved changes is renamed

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • 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

    Description

      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

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. AF-2515 Error dialog appears when business process with unsaved changes is renamed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. AF-2516 NoSuchFileException appears when data object with unsaved changes is renamed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2946 Error when renaming an asset with pending changes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: