Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3432

[Stunner] Case Definition - Wrong location of the default WID file

    XMLWordPrintable

Details

    • CR1
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15)

    Description

      Issue

      The StartCaseInstance  [1] custom task is not being present when authoring a Case Definition, which is being located outside the <default> package

      Description

      When creating a new Case Project, in Business Central, the wizard creates a WID file at the root package (<defatult>). On the other hand, the Case Definition (Stunner) editor expects the WID files either at global folder or same package as the asset itself.

      Proposed solution

      Change the location of the default WID file, being added by the project creation wizard, FROM the root package TO the global folder.

      Additional Actions

      • Check the WID - compare attributes and parameters with the runtime one, if any, to check everything is up to date

       

       [1] https://github.com/kiegroup/jbpm-wb/blob/master/jbpm-wb-integration/jbpm-wb-integration-backend/src/main/resources/CaseWorkDefinitions.wid#L70

      Acceptance criteria

      The location of the default WID file is changed FROM the root package TO the global folder.

      • As a result, StartCaseInstance Custom task node is present in palette of processes or cases in Case projects.

      No other changes for Custom tasks are applied.
       

      Attachments

        Issue Links

          Activity

            People

              kgaevski@redhat.com Kirill Gaevskii
              romartin@redhat.com Roger Martinez
              Lubomír Terifaj Lubomír Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: