• Type: Feature Part
    • Resolution: Done
    • Priority: L3 - Default
    • 2.7.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      Context:
      Once the event based process mapping is in place (OPT-2722) the process generation can be triggered and monitored using the publishing api.

      AT:

      • a publishing endpoint is added to the Event Based Process API, e.g. POST /api/eventBasedProcess/:id/_publish
      • a cancel publishing endpoint is added to the Event Based Process API, e.g. POST /api/eventBasedProcess/:id/_cancelpublish
      • the endpoints Event Based Process By Id & Get all event based processes return:
        • the current state of the event based process 
          • unmapped - mapping is empty and no published state available
          • mapped - mapping contains entries, no published state available
          • publish_pending - once an event based process publish is triggered the process will be in this state till the publish has processed all events till the publish date
          • published - there is a published state and the event based process hasn't been modified since (will not be available in the scope of this task as we need OPT-2982 for this )
          • unpublished_changes - there is a published state and the event based process has been modified since publication
        • the progress of the publishing if in state publish_pending (will not be available in the scope of this task)

      Out of scope:
      The actual process instance generation/import

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: