Skip to Content
Author's profile photo Kenichi Unnai

Typical BPM Workflow HOWTO on NW CE 7.1 Ehp1: Scenario 4 – Pushing back the submission

Hi all,

Let’s continue with another implementation use case. (Again  – I suggest to take a closer look at the 1 hour recorded session if you are interested in the demo.)

Remark: The contents require beginner level knowledge of NW BPM on 7.1 Ehp1.

Scenario 3:  Pushing back the submission

From the workflow implementation point of view, this is another classic use case. If the customer has any legacy workflow tool, you would get question like this – “How SAP NW BPM would implement it?”

Solution

This is a typical use case of Process Context. It is sometimes called as “Data Object” in the process composer.

The general idea is

  1. Create a Data Object for the temporary data persistence during the process execution
  2. UI uses this data for the screen rendering
  3. Process Modeler will map this context data between Requester and Approver UIs. 

That’s it. Again please drop your insight for

 – “Very common workflow use cases” but you don’t know how to implement them with NW BPM.

 

See you in the next blog! 

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.