Skip navigation
All Places > Getting Started > Blog > 2015 > November
2015

Good News!

 

With the latest update for Nintex Forms (2.8.1.0) List Lookup Control has been enhanced.

In the release notes you find: "Fixed an issue where the List Lookup filter may not work when Source View specified."

 

So with that fixed, you now have the possibility, to filter data with multiple parameters, based on your Source View.

 

For example:

I have a SharePoint-List named "Contracts" and I only want to display items of a particular company, where Currency Status equals "Active".

2015-11-26_08-43-47.jpg

Configuration of my List Lookup Control looks like this:

2015-11-26_08-45-47.jpg

 

And the result is very #2015

2015-11-26_08-28-28.jpg

 

(Note: Currently, "CompanyName"-Control has to be a Single Line Text Control. Calculated Value Controls are not supported (yet?))

I have passed the exam!

What are you waiting to take your certification?

Visit the Nintex Learning Center >>> https://learning.nintex.com/

 

 

We have a Form

in which we would like to have form validation enabled for

  • First Name,
  • Last Name and
  • Department/School
  • Manager 

as seen in the picture below. I have setup Validation Rule NotEmptyWhen isNullOrEmpty({Self}) for all the controls I'm interested in validatin.

So far so good,

What happens in the next screen is that there is a button, which on click takes the users to another screen to select a bunch of systems. A simple script onclicent click does the trick. But, for some reason, VALIDATION is NOT applied.

 

goStep(3) sweetly takes the form to the next form for system's to select. When the user click FINISH immaterial of the value of text fields, the item gets submitted. Bad, form, bad person, bad swetha.

I am sure its an easy fix, but am stumped. So i was hoping you gurus can help me resolve this issue.

I was pretty sure I posted this qsuegtion somewhere, but can't seem to find it for the life of me(been that kinda day),so posting it again.

Attached is the Nintex form exported xml file. Perhaps Nintex Ninjas here can help this sister force her users to Submit their FirstName, LastName, Managers and Departments?

Tagging rockstars who were very helpful and assisted me brilliantly in the past.

Thanks in advance

Pavel Svetleachni Frank Field Eric Harris Nintex For Office 365 Support

fhunth

Have you seen the Nintex Store?

Posted by fhunth Champion Nov 18, 2015

 

 

Introducing the Nintex Store

 

Nintex Workflow for Office 365 provides a huge range of actions you can use to build workflows to automate your business processes, taking your productivity in Office 365 to a whole new level.

 

With Nintex Workflow, it's introduced the Nintex Store, a one stop shop for all your action needs. The Nintex Store contains a range of actions you can leverage in your workflows; including actions to integrate all the applications and systems that are relevant to your business. You can now easily add actions to the workflow designer that connect to a specific system or to a particular service provider. The store also contains a powerful search capability allowing you to find actions quickly and easily. Nintex is constantly adding new actions to the Nintex Store, allowing you to extend Office 365 in ways you had only imagined before.

 

 

 

 

 

Using the Nintex Store

 

Step 1

The Nintex Store can be accessed straight from the Nintex Designer Ribbon. Click on the Store button in the Ribbon. This will open the store where you can browse, try, or buy workflow actions.

 

 

Step 2

Search for an action pack/action, or browse the categories.

 

 

 

Step 3

Let’s add the Yammer Starter Pack. Each action pack contains information on what’s inside and allows you to Add the action to your toolbox.

 

 

 

Step 4

Once you try an action pack, the actions will be available in your Action toolbox

 

 

 

 

 

 

This content is part of the Nintex Workflow Office365 Product Guide

 

 

 

fhunth

Nintex Support Options

Posted by fhunth Champion Nov 13, 2015

Nintex Support Options Enhance Your Nintex Investment with One of Our Cost-Effective Support Packages

 

Nintex Software Assurance

Entitles your organization to product updates and/or new releases of your licensed Nintex product(s). Support is provided in the areas of installation, configuration and technical troubleshooting via our community site, chat or email help desk.

 

Nintex Premium Support

Provides your organization with higher priority service, through outbound phone support, guaranteed response times, plus unlimited developer licenses (based on annual renewal), migration guidance and global coverage.

Nintex Premium Support is a step above Nintex Software Assurance, which is required in order to purchase Premium Support.

 

Nintex Platinum Support

Provides your organization with the highest level service offered. Not only do you get the benefits of Nintex Premium Support, but you also get direct phone access to our support team 24x7x365, a faster response time, and more time to review and plan for your next migration. In order to purchase Nintex Platinum Support, you must already have Nintex Software Assurance and Nintex Premium Support.

 

 

You will find detailed descriptions of our support offerings in this guide so you can make an informed decision on which Nintex support option will meet your organization’s requirements. For more information on these options, please contact the Nintex sales team at sales@nintex.com.

 

Support Offerings in Detail

 

NINTEX SOFTWARE ASSURANCE (SA)

 

Software Assurance is Nintex’s Maintenance Agreement. This level of service provides you with the following:

 

• New Software Releases - Nintex will periodically make available to you releases that typically include patches, bug fixes, modifications and/or updates to the software, (collectively, “software updates”). All software updates are considered part of the software as long as your license(s) is/are current and you have a valid maintenance contract. All support and maintenance are provided only for the most recently released version of the software and the immediately preceding version of the software.

 

• Self-Help and Web-based Cases Submission - Software Assurance provides you access to an online collection of self-help tools and how-to information to help you develop your own solutions and troubleshoot issues. If you cannot resolve your issue via the self-help portal, Nintex allows you to log service requests via the Nintex Connect community site.

 

• Support Hours – The hours of Support mirror the regional support center where you purchased the Nintex product and support package. These hours are: AMER Region – 8am-5pm Pacific Time, Monday-Friday APAC Region – 8am-5pm AEST Time, Monday-Friday EMEA Region – 8am-5pm GMT, Monday-Friday

 

• Response Times: Response times for Software Assurance customers are not guaranteed. However, Nintex will provide our best effort to respond to all inquiries within 24 hours.

 

• Non-Production Licenses – Nintex will grant, at your request, non-production licenses that can be used in your development or test environments. You will receive up to one non-production license per production license you purchase.

 

NINTEX PREMIUM SUPPORT (PS)

 

Premium Support is the Nintex Support and Maintenance Agreement. In addition to the benefits you receive with Software Assurance, you will also receive the following benefits under a Premium Support contract:

 

• Phone Support – As a Premium Support customer, you receive OUTBOUND phone support. After you request assistance, we will attempt to contact you via phone 24 hours a day, five days per week. Please note that weekend coverage is NOT included.

 

• Support Hours – Support hours for Premium Support customers are from 12am GMT on Monday through 11:59pm GMT on Friday.

 

• Initial Response Time (SLA) – As a Premium Support customer, you benefit from an 8-hour initial response time after you open a support case, excluding weekends.

 

• Migration Guidance – If you are planning a migration, your Premium Support contract provides you up to four hours of migration guidance. Our experts can share best practices, assist in identifying potential issues, and provide advice specific to your environment. Please note that migration guidance is a “best effort” activity and does not include any customizations, script creation, solution deployment or anything that may be considered professional services.

 

• Non-Production Licenses – As a part of the Premium Support contract, we offer unlimited non-production licenses for you to use.

 

• Global Coverage – You will receive support from our global network of support centers. As a result, your initial response may come from another office depending on the time and day you open your support ticket.

 

• Customer Portal – You will receive a login to our customer portal, where you can create a case, modify an existing one, get real-time status updates and track your case history

 

 

NINTEX PLATINUM SUPPORT

 

Additionally, you can supplement your Premium Support with Platinum Support, which is critical for any enterprise. In addition to the benefits you receive with Premium Support, you will also receive the following benefits under a Platinum Support contract:

 

• Phone Support – As a Platinum Support customer, you benefit from our priority inbound phone support.

 

• Support Hours – Platinum Support customers receive 24x7 support coverage for email support. • Initial Response Time (SLA) – As a Platinum Support customer, you benefit from initial response within four hours for all support cases you open.

 

• Migration Guidance – If you are planning a migration, your Premium Support contract provides you up to eight hours of migration guidance. Our experts can share best practices, assist in identifying potential issues, and provide advice specific to your environment. Please note that migration guidance is a “best effort” activity and does not include any customizations, script creation, solution deployment or anything that may be considered professional services.

 

Support Requests

 

CONTACTING SUPPORT

 

To receive support, please contact us using one of the following means:

 

Online Case Submission – community.nintex.com/support

Email – support@nintex.com

Phone – if you are entitled to inbound phone support, you will receive the support phone number when you purchase Platinum Support.

 

To help expedite resolution, please make sure that you provide the following:

 

• Full description of the problem, including any actions that initiate the problem state;

• The business impact of the problem;

• The version, edition and build numbers of all software components affected or involved in the affected system (for example, Nintex products, Microsoft SharePoint products, Windows Server, including physical or virtual configuration, SQL Server, Internet Explorer);

• Any applicable log files that help with diagnosis;

• Any applicable screen capture images that help illustrate the problem; and

• General information such as your name, job title, organization name, location, Nintex license ID information and partner name.

 

RESPONSE TIMES

 

Nintex will make every reasonable effort to respond to all support and maintenance requests based on your current service contract. The “response time” is the time elapsed between the initial report by you and when Nintex aims to make an initial response to your report. A “business day” means a regular business workday other than a Saturday, a Sunday, or a public holiday in the support region from which support and maintenance services are provided to you, and “business hours” means the business hours in the support region from which support and maintenance services are provided to you during a business day.

For additional information on support hours, please see the services offering details listed above.

 

SCOPE OF SUPPORT SERVICES

 

Nintex support services are available to customers with a current support agreement. The support services provided under Nintex support agreements cover the following:

 

• Incidents attributable to faults in Nintex software

• Information and advice pertaining to the use, installation, configuration and troubleshooting of Nintex software

• Information and advice regarding configuration of operating systems and host systems for the optimal operation of Nintex software

 

OUT-OF-SCOPE SUPPORT SERVICES

 

If you contact Nintex for assistance with an item listed below, or if the failure is due to one of the below reasons, we’ll provide the information to your partner for assistance. You will be responsible for any expenses or invoices incurred as a result of the partner engagement. The following support services are considered out of scope:

 

• Information and advice pertaining to the use, design, and configuration of the software

• Troubleshooting of Microsoft, third party, or open standards-based technologies, such as XML, HTML/CSS, SharePoint, BizTalk, Active Directory, middleware, SQL queries, and database connectivity.

• Custom solutions created by any party other than Nintex. “Custom solutions” include customizations enabled by Nintex documentation, such as an SDK, and any other enhancement or modification that is not provided “out of the box” by Nintex.

• Custom scripting or code.

 

Services that are considered out of scope include, but are not limited to: information and advice pertaining to the use, design, configuration or troubleshooting of Microsoft, third party, or open standards-based technologies such as XML, HTML/CSS, SharePoint, BizTalk, Active Directory, middleware, SQL queries, and database connectivity

 

 

More info at Support - Nintex

Nintex was present on an event in Chile. Sharepoint Chile 2015

Luis Bardin presented  "The Cost Of Not Investing In BPA"

 

The Eighth Latin American Symposium on SharePoint and Other Microsoft Technologies is the largest multidisciplinary event in the region , where the most prominent experts and business executives met to talk about SharePoint , Project Server, Office 365, Microsoft Azure and Yammer , among other technologies. It was an opportunity to learn more , share and search for the best technological solutions in a pleasant atmosphere and thought of every detail for assistants.

 

16.jpg

Imagen hoy 5-23-44 pm (1).JPG

principal.jpg

After an update to our community platform in October, it seems some members aren't seeing what's actually "newest" in their newsfeed. Here's a quick tip on finding the latest information, blog posts, comments, threads, people you're following and trending content.

 

It's two clicks:  "News" and then "Most Recent."

Here's a picture to show you where to click:

NewsTip.PNG


This is where you'll see you can post your status update. It's a lot like Facebook. Tell us what you're up to!

And look to the right... You can filter your results to focus on, or eliminate, things from this feed.

Tip3.PNG

 

Like what you see? Then only one more click makes this your default view!  Just push that little thumbtack, and then any time you click "news," you'll see the "most recent" results as you chose to filter them.

Default View.PNG

 

I hope this little tip helps you enjoy your newsfeed!

The feature to edit the task forms from the workflow designer in Office 365 came with the July updates for Nintex Forms.

For me one of the best features that came with this is the ability to include fields from the related item in the task form.

 

However you may  receive an error when you try to publish the workflow.

Error similar like the one below:


Error publishing workflow. Workflow XAML failed validation due to the following errors: Activity 'DynamicActivity' has 54 arguments, which exceeds the maximum number of arguments per activity (50). HTTP headers received from the server - ActivityId: 2d403179-534a-44ab-8ecc-cd1bd18271ed. NodeId: . Scope: . Client ActivityId : 18ef3f9d-a0e8-2000-213e-a3414321b7c2. The remote server returned an error: (400) Bad Request.


 

This error is explained in flowing post Workflow XAML failed validation due to the following errors: Activity 'DynamicActivity' has ## arguments .

 

The issue is that for each task form that you edit two additional variables will be added, even if the tasks are using the same content type!

This conclusion is mine and I came to it via testing.

 

So keep this in mind when you design your workflows!

 

Cheers,

Ivan

Hello,

 

**********

I strongly suggest you review Repeating section as html table

Its easier and more efficient than this.

**********

 

I've been searching alot for something simple to convert or decode the xml that is generated from the repeated section into a plain text.

 

most of the blogs uses UDA and some complex workflows to do that.

 

but i managed to make a simple workflow and some extra controls on Nintex forms to get the text i needed.

 

it may not be the optimal solution for most cases, but for me, its just what i need

 

as a start, create two list columns type of Multiple lines of text "plain text"

 

Repeated Action.png

 

 

- Create a form using Nintex Forms.

 

- Create the repeated section you need.

 

connected to.png

 

note that all controls inside the repeated section must be "Not connected".

 

only connect the repeated Section to one of the multiple lines column that you created.

 

name the controls inside that repeated section.

 

when publishing the form and creating a new item, you will see the below results in the Repeated Action Column.

 

Repeated Results.png

 

now we want to get the required data in plain text without the tags

 

as a start go to you Nintex form

 

- Add 4 single line textboxes, sort and configure them as demonstrated in the below images.

 

adding 4 textboxes and sorting them as the below image

 

txtboxes names.png

 

note that all the textboxes are not connected to any control

 

i sorted them this way because after testing, the list column is filled from top to bottom

 

first textbox is used to "add new line" and add the field name to it, see the image below.

 

1stboxconfig.png

 

we added the name of the label so the data is displayed properly when converting it to plain text ( you will see the results at the end )

 

do the same step for text box 2 and 3

 

-txtbox2: default value: new line Email / not visible.

-txtbox3: default value: new line Address / not visible.

 

for textbox 4, make its default value a new line only.

 

now Nintex form part is complete.

 

now you have to create a workflow to remove all the tags, its a really simple workflow that i discovered by mistake

 

- create a variable type of multiple lines of text, lets name it varContent.

 

- add "set variable" action to your workflow and configure it as shown in image.

 

setvar1.png

 

- fill this variable with the field where you saved the repeated section and retrieve it as plain text.

 

- add "set field value" action to your workflow, set the second list column that we created "plain text" with varContent as shown below.

 

setfield.png

 

save and publish your workflow, now you should see the expected results.

 

final.png

 

**Note

 

if you wish to add spaces in the default value of the textboxes, like this (Name: John) instead of (Name:John). add the below workflow action. (before set field value action)

 

plaintextafter.png

 

fn-Replace(variable," ","")

 

  means the "space" in html but the & was rendered as &

 

hope this helps

 

thanks

Repeating section as html table in mail describes how to transform a repeating section to html. It was done by template rules. Problem was it outputs all the Text Data that is present in the XML file even if no template rule is defined for a repeating section control since then applies the default rule for text.

 

To avoid that here for-each is used in stylesheet. Only these fields that have to appear in the output must be specified.

 

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

   <xsl:output method="html" />

   <!-- transform repeating section from xml to html -->

   <xsl:template match="/">

      <table border="1" width="100%" style="border-collapse:collapse;background-color:#eee;border:1px solid;color:black;font-size:100%;font-family:arial,helvetica,sans-serif;">

         <thead>

            <tr>

               <td>first name</td>

               <td>name</td>

               <td>company</td>

            </tr>

         </thead>

         <tbody>

            <xsl:for-each select="//Items/Item">

               <tr>

                  <td>

                     <xsl:value-of select="first_name" disable-output-escaping="yes" />

                  </td>

                  <td>

                     <xsl:value-of select="last_name" disable-output-escaping="yes" />

                  </td>

                  <td>

                     <xsl:value-of select="company" disable-output-escaping="yes" />

                  </td>

               </tr>

            </xsl:for-each>

         </tbody>

      </table>

   </xsl:template>

</xsl:stylesheet>

 

Except for the stylesheet, everything remains as in Repeating section as html table in mail .

Filter Blog

By date: By tag: