Skip to Content
Author's profile photo Rene Klumberg

Develop a Common Process for Single and Mass Processing in MDGF

At several customers I was faced with the fact that the
standard MDGF workflow behaves different when the requester compares a single
with a multi object change request.

In a single object change request the requester gets the
single processing user interface and can enter the master data that he wants to
have created or changed. This is usually what is expected.

For a multi-object change request it is a different story. The
requester can only add IDs to the change request. For example if a field in the
account shall be changed and a new company code shall be created, the requester
can only add the IDs to a new change request and maybe use the note field to
tell the processor of the execute changes step which field he wants to be

So I thought that the requester should get the single
processing user interface as well for a multi object change request. Therefor I
added an additional activity to the workflow that provides this functionality
to the requester in case the change request is a multi-object one. The rest of
the workflow is untouched, so after the requester has finished his task it will
behave identically.

Please read the document
for further details.

Thanks to Steffen Ulmer and Adrian
Branka for supporting me in writing the document.

Assigned Tags

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