AndreasBucher Absent Member.
Absent Member.

Creating Own nrfCorrelationId from request Workflow

Hi all,

I have a customer that has several ways to order Roles (about 10 Request Workflows). All Roles have the same Approval Workflow. Until now we could handle all wishes from the customer.

Now he wants to have an exception for just one Request Workflow (1 out of 10).

As far as i know there is no Attribut on the nrfRequest Object that Points to the Workflow that role gots ordered from. Now im thinking about creating my own CorrelationIds during the Request, but i am not sure if this is recommended.

So here are my Questions:
1. is it recommended to create this yourself?
2. what happens if several nrfRequest have the same ID (because currently they can order many roles in one Request Workflow)
3. is there another way to find out which nrfRequest Object was created by what workflow?

Thanks for your help.

Kind Regards
Labels (1)
1 Reply
AutomaticReply Absent Member.
Absent Member.

Re: Creating Own nrfCorrelationId from request Workflow


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request:
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (
- You might consider hiring a local partner to assist you.

Be sure to read the forum FAQ about what to expect in the way of responses:

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.