Configuring a Notification!

  • 17 March 2016
  • 6 replies
  • 0 views
H
Badge +2

I am wanting to configure a notification that is pulling in the names of documents from a collection (All Document Names).

Here is the body of the text:

-------------------------------------------------------------------

Following item(s) will be coming for review
within two weeks:

All Document Names

Please
ensure solution inventory is correct for these item.

--------------------------------------------------------------------------

When the e-mail is received, the document names appear as follows:

--------------------------------------------------------------------

Consumer Electronics Online Experience Survey -
Google Forms(2014-12-03_13-45-12_63404).pdf;MRD
Imperatives.docx;PowerShell_Commands.txt;

-----------------------------------------------------------------

My goal for the notification is to have the documents list in the e-mail as follows:

------------------------------------------------------------------

Consumer Electronics Online Experience Survey - Google Forms(2014-12-03_13-45-12_63404).pdf

MRD Imperatives.docx

PowerShell_Commands.txt

-------------------------------------------------------------

A much cleaner format?   Any Suggestions?

6 replies

P
Badge +11

Hi William,

use a "for each" action to loop through all items of your collection. Inside the loop you use a "Build string" action to combine the single items of your collection in one single string and to provide any format you like.

Remember that you can write html code in the "Build string" action to format your text. You can then put the variable you stored your string in directly in the mail and the html will be interpreted correctly.

Regards

Philipp

H
Badge +2

Thanks Philipp!

I have a loop set-up and but I was using the wrong action.

As far as the HTML code, does this look correct?

<html>

<body>

<p>{WorkflowVariable:All Document Names}</p>

</body>

</html>

Thanks, Bear

P
Badge +11

I think we need a little correction.

First of all you don't really need the <html> and <body> at all here. Using a paragraph (<p>) is fine.

You have to understand that you do this action inside of a loop and therefore the action will run many times. Your configuration should therefore rather look like:

{WorkflowVariable:var_AllDocumentNames}

<p>{WorkflowVariable:var_CurrentDocumentName}</p>

And store result in: {WorkflowVariable:var_AllDocumentNames}

This will add the current document name (var_CurrentDocumentName is the variable you store the current instance inside the "for each" action configuration) to a new variable called var_AllDocumentNames. You need to provide this variable in the beginning so you will not just overwrite it with the current document name, but save all previous names as well.

Is this comprehensible?

Regards

Philipp

H
Badge +2

Phillip,

I have attempted to use the information you provided but I end up with all the document names like this:

--------------------------------------------------------------------

Consumer Electronics Online Experience Survey -
Google Forms(2014-12-03_13-45-12_63404).pdf;MRD
Imperatives.docx;PowerShell_Commands.txt;

-----------------------------------------------------------------

plus one more which is separated:

PowerShell_Commands.txt

this is the first document in the order of the workflow.

I have tried different approaches but have no luck in setting this up correctly.  I am new to working with Nintex and workflows but I am trying to understand.  I am not a developer.   Any assistance is appreciated.

Bear

P
Badge +11

Could provide a screenshot of the configuration of your "build string" action?

H
Badge +2

Philipp,  thank you so much for your assistance, but I got it to work using the following method.

Workflow

Nintex notification list.png

Regular expression configuration

Nintex Regular expression..png

Notification results:

Nintex notification.png

Again, thank you for your assistance!

Bear

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings