Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-521

Workbench: add optaplanner annotations domain editor functionality in kie distributions, but masked out by role plannermgmt

XMLWordPrintable

    • NEW
    • NEW

      In the domain editor, the optaplanner annotations tab functionality needs to be included in all our distributions, but masked out by a special role called "plannermgmt".

      Context:

      • Business Resource Planner (= OptaPlanner) is part of both BRMS and BPM Suite. Customers who buy either, get Planner too.
      • All optaplanner-wb functionality is being added in BRMS 6.3, but customers will need to add a special role to their users to be able to use it. So it's "masked out" (= code included, but not usable to users normally).

      Reqs:

      • That domain editor functionality needs to be added to both:
      • The optaplanner annotations tab needs to masked out if the user does not have the role "plannermgmt"
        • Preferably the tab should not be visible at all (see UF-279)
        • Even the admin user won't have the role "plannermgmt" in the first release.
        • Customer will use the optaplanner functionality by creating a new user specifically that does have this "plannermgmt" role.
      • (When creating a new domain, a user should not have to choose between creating an drools-jbpm or an optaplanner domain. A domain is automatically drools-optaplanner-jbpm compatible. What I mean by this: A user should be able to take an existing drools domain and later change it to add optaplanner functionality (and later even add jpa functionality etc). This seems to already possible, so this req is probably already fulfilled.)
      • This needs to be in kie 6.4.x (and BRMS 6.3) too.

            wmedvede@redhat.com Walter Medvedeo
            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: