Skip navigation
All Places > Getting Started > Blog > Authors eharris04

Getting Started

8 Posts authored by: eharris04 Employee

Hello Connect members,

My name is Eric Harris and many of you may have seen my name somewhere here either on a post, Nintex Hangout videos or content with Nintex. I’m excited to be reaching out to you in 2019 on the community and wanted to bring you some great news as Nintex starts out the new year with a bang.

 

 

 

While many of you signup as members and visit here to post questions or find answers, there is a group who do more such as help moderate, and most importantly help set the atmosphere of the community by making other members feel comfortable here. As a representative of Nintex and a former community member, Nintex Champion and evangelist, I want to say thanks for all that you have done, and happy new year to each of you.

 

Over the past year, you may or may not have heard about a small project Nintex took on to revamp this community, make some enhancements and updates to make it easier to serve you and migrate to a different platform so we can keep growing together.

 

Well I’m pleased to announce that while a year is a long time, doing things right is always our aim and we are getting really close to launch time. Hope you’re excited as I am about it, if not, get excited because this is for and about you.  and we want your help to make sure the community continues to grow. Because this is your community, I want you to be part of this launch to make this the biggest technical community launch in the history of Nintex, and communities like it worldwide.

 

So what does this mean? This is the first of many updates I will be posting as we get ready for the launch, so definitely stay tuned. Also visit here often and do what you do best, post questions and answers right here. Also if you have any suggestions, ideas, complaints or whatever you want to call it, list them below in the comments section and I'll be sure we take note as we finish up the final launch steps. 

Ever wanted to find out more about Nintex partners or have some great ideas about a potential project, but don't quite know how to get going? 

In fact, many organizations need help locating Nintex partners, and the Nintex.com site has a nice little feature available for FREE.  It's called, "Find a Partner".

Why you should care about this feature?

1. If you're new to Nintex.  Well outside of any obvious reason, if you're new to Nintex, then this feature can help you connect with a partner near you that can get you the necessary information.  They are super qualified, know your local area really well, and t best of all they are waiting to hear from you. 

 

2. If you're already a partner, or considering joining Nintex's Partner Network, then this could be your little gold mine.  Partner networking is a great way to get connected, learn the ropes, and make great networking connections that can help grow your business or expand your current offerings.  Many partners have a unique service offering or handle reselling only, so the chance to partner with others companies to tackle a specific opportunity could be huge. 

 

How does it work?

The feature is built using the Microsoft PinPoint platform which works really well because it provides organizations visibility not only from Nintex, but also within the entire Microsoft eco-system. Who wouldn't want that? While I'm not going to sell you on the PinPoint profile, the advantage for Nintex is that other partners can use it to find you and connect regardless the need.  Nintex just makes it easier for you to use it and find others. 

 

How to use it?

Click on the link Find a Partner - Nintex then click on the "Beta Preview*" link.

Image

Next, fill in your search criteria on the left hand side and watch the partner names roll in.  Its great, its fast, and its useful to helping you find the partner that’s right for you.

Image

So now that you've seen it, go check it out.  Happy Nintexting ....

 

P.S.  If you're a partner, then ensure your profile is out there and that your information and tags are updated correctly.

Hello there.  If you're reading this post, I hope that you had the opportunity to read Part 1: Work Flow Purpose.  and Part 2: WWYSYDH.  In part two of this series, I introduced the concepts of using the right actions to get the right results.  At the end of it I promised to go even deeper and provide an example Training Calendar solution for you with a list and workflow incorporating what I've been covering in this series.  Well, I did it .  I built it all out, typed this long blog, included screenshots and even remembered to attach the files.

 

I will say this post is rather lengthy, but no solution is good without documentation and I wanted to explain each step so you would learn as you went along.  If you’re as excited as I am…let’s get going!

Part 3: Meet Mr. Wilson.

Scenario: I had a customer, whom I will call Wilson.  Wilson called me one day with an issue using his workflows.   He had been working on a calendar list for training and was wanting to make it automate notifications when training events are created, updated or canceled.  He also wanted to setup a reminder notification to be sent out one day prior to the events start date.

 

Seems easy enough right? So let’s see why I’m using Wilson as an example for my blog.

 

Outside of the obvious that he’s a celebrity and has been coveted since his debut in Castaway, Wilson has some things he wants to do better.  What I discovered when I look at his SharePoint site was quite interesting. Not bad, just….well that’s the reason he called me.

 

So let’s see what Wilson did…

 

Wilson created three workflows for each scenario listed above.  He had a workflow running when a new event was created, a workflow when the event was changed, and a workflow when the event was cancelled.  Are you seeing what I’m seeing? That’s slight overkill for the events and his process.  Not a bad thing, and he certainly can do that, but that makes things difficult if he’s wanting to be efficient.  Hmm… let’s keep going.

 

If you remember, Wilson wanted to send a reminder out for the day before the events date to remind attendees.  The problem that he was facing was trying to send the reminder without causing the other workflows to fire which would send additional notifications.  Okay, I can see how this can occur, so how am I going to fix that?  Just for your reading pleasure, there wasn't anything special about his list, it was a standard out-of-the-box Calendar list, and I attached a copy below for you.

 

So where did I start?

I needed to get him the reminders and as an added benefit, eliminate some redundancy?   I also knew he had a busy schedule with interviews and special appearances and didn't need to spend so much time managing three workflows.  This is too much fun writing about Wilson, but he is enjoying the press as well. So keep reading...

 

Here’s how I approached it.

 

Step 1: Assess the purpose and the logic

My first step was to look at his workflows.  After realizing they were all similar I knew I could eliminate one of them easily. The image below shows what actions were in his workflow (nothing spectacular):

 

So as you can guess, Wilson had three workflows that would run on new item creation and on changes to the item.  I knew that was part of the problem, so I wrote out the logic using the DUCERIM Process worksheet to be sure I didn't redo his looping affect:

  1. Notify a group of people when a new event was created
  2. Notify a group of people when the event was changed/updated
  3. Notify a group of people when the event was canceled

 

Step 2: Reconfigure the logic to ensure efficiency (2 workflows instead of three)

My next step involved two separate things.  The first part of step 2 was to reconfigure the New Event Workflow settings to ONLY run for new events.  This is important because by doing this I could then isolate the logic of what happens when the event is new.  See the workflow setting below:

 

How are you doing so far? I hope you’re following my logic; at least it made sense to me and Wilson at that time :-).

 

My rationale is that I know when a new event is created in SharePoint, it can only be a “New Item” once.  This means I do not need any additional conditions to be checked or validated against. I also added in a status column so that when things are changed, the workflow running on modified would know what to do with that information as well.  This possibly could be eliminated, but I left it in here for my own sanity. 

 

The results of the reconfiguration produced the following workflow that only runs once when the event is first created. 

 

New Event Workflow Explanation

The workflow runs on new > sends a notification to the appropriate group > updates the item’s status > calculates the pause date, pauses until the pause date > sends the reminder notification.

 

Wow!!! So why did I build it this way?

As I mentioned this workflow is solely meant to run once, and if nothing else happens to this event, such as an update or change, this is the only workflow that will run.  Therefore adding the pause until made sense because I can pause the workflow until the day before the event’s date and then have it run again to send out the reminder.

 

So I got this one done, now what?  Well, I had to test it to make sure I had it built correctly.  After running through two events, Wilson was quite thrilled to see the reminder working as well.

 

The second part of step 2 was to get the Changes and Cancellation Workflow built out correctly.  My challenge here was to fix the logic of one workflow, and if possible eliminate the other workflow.

 

Let’s see how I did that…

Ideally I wanted this workflow to ONLY be triggered when the event is modified.  This is important because this isolates my logic to a certain action that I know and can plan for and wont cause this one to run when the event is new.  To achieve this I modified the Workflow Settings and ensured that it only ran on event was modified.

 

The next thing was to keep the actual workflow process simple.  I decided to use the run parallel actions. This gave me the chance to run both conditional test simultaneously and only complete the correct action each time. I know some people would try to use the run if action and you could do that, but I like to try and keep process as simple as possible and keep my workflow as short as possible.

 

After I figured that part, I used the set a condition action because I wanted it to do a single task; check the status field for either “Change” or “Canceled”. Based on the status it would then perform the remaining actions accordingly. For a modified event to be considered a change, the user could update the event item, and change the status to reflect that it was changed.  The logic I was aiming for was to have the workflow process that change.  See the image below.

 

The next part was processing for Cancellations. Hmm... I already had the actions that I wanted to use for changes, and technically the cancellation is very similar to the change so I did this:

 

Hidden below is a BIG TIP and one reason I absolutely love Nintex.

I know that set a condition is similar to an action set in that it groups all the actions underneath it.  So I simply clicked on the little down arrow to the right of the set a condition action and selected copy.  I then went over to the branch on the right, click on the little node and selected paste.  I hope you caught that tip (you can copy and paste actions).  Literally within 2 seconds I had the same actions in both branches and all I needed to do was to configure the right side branch to process for Cancellations.

 

I want to see you do that with a SharePoint Designer Workflow. Oh wait…you can’t .

 

Wilson was also impressed by how quickly I had this logic built out.  So lets keep going, we’re almost finish with this workflow.

 

I removed the first send notification, the calculate date and the pause until actions as I didn't need those for a cancellation.  Since an item was canceled, I wanted to show the users that it was canceled.  This would help them identify the canceled events from the current ones.  I decided that to achieve this I would update the title of the event by appending “- canceled by Initiators Name” to the end of it.  That was it, and I was able to achieve that by using the update item action.  After that action, it would send the notification to all attendees and end.  Think that’s cool, see below:

I now how all the information and logic correct, both branches are filled out and it seemed to be legitimate; however, a workflow that is not tested is not a good workflow.

 

Testing the Change and Cancellation Workflow:

To test this one accurately, I took an event previously created for the New Event test and I modified the event dates, added a different description just for fun, and set the status to “change”.  I knew I could do this because the logic of this workflow would only run when an event was modified. I also knew that the New Event workflow would not run again so this event was a safe test.

 

The results of this was as expected.  I received the first notification that the event was changed, then it paused until the notification date.  Because I ran the pause for the same day, I received the reminder 5 minutes later which told me that it worked as it should.  If nothing else changed on this event, that would be the only time it would run and complete.

 

The next test was to take another event that I had created and process it for canceled.  For this I simply edited the event and changed the status to cancel. Seems simple right.  The results again were successful.  That means I had a good workflow and I can now reveal it to you.  Here is the complete workflow altogether.

 

Conclusion:

Well that’s it, I had two workflows running and notification being sent to the attendees at the right times, but my job wasn't quite done.  While I did leave Wilson quite speechless with how nice it turned out, and how fast I built it, I couldn't leave his site in that manner.

 

What I mean is that I had test data out there and it needed to be cleaned up.  So in following the DUCERIM process, I went through and purged the workflow history along with the items in the events calendar that I had created.  This allowed Wilson to start with a clean slate and get back to whatever he was doing before he called me.

 

I hope you enjoyed this fun but real life example of using Nintex to achieve an automation process with a Training Calendar.  There is a lot more that I could have done from adding a registration component, ensuring only active events are showing and so much more; but this was long enough. If you want to know more about the DUCERIM process or have questions, ask me and happy #nintexing.

 

Thanks,

Eric

 

P.S.  I may have a Part 4 but who knows...

In Making “Work Flow” Matter Part 1, I discussed purpose and the benefits of setting a clear vision for your workflow.  Without a purpose, your workflow can end up being nothing more than a resource constraint on the platform, and no one wants to build that.

 

To honor my commitment to dig deeper with each part of this series, I offer you the below meme for some light humor.  The next part of the series I will simply title “Mr. Action, WWYSYDH? (pronounced Whissidh)”.  Interested?  Keep reading…

Part 2: Mr. Action, what would you say you do here?

When it comes to workflows, do you know what your workflow actions are actually doing?  This goes beyond the purpose, the logic and the idea or the workflow.  What actions are you using, and are they impacting the object and platform in the correct manner?  I touched on this some in part 1 so let’s go deeper.

 

If you have ever built a complex workflow, you would have at some point experienced that workflow failed to run, or an error message while running.  You may have had it complete successfully, but nothing changed as you intended. Sucks right?  Well, you are not alone.  Since actions are the backbone of workflows, when something is not working right, it usually prevents anything else that follows from working. Troubleshooting can also be just as daunting, but here is a tip: use the “log to workflow history” or “custom message” for certain actions so that the workflow can output data to the history area. Don't forget to remove those once everything is working fine.  They can bloat the Nintex database unnecessarily, so keep that in mind.  Another tip is to view the workflow visually to see just what action failed.

Nintex allows you to visually see the workflow, how it ran and what actions completed or did not complete.  This visual indicator is a nice way to see where your logic may need some tweaking. To locate this view, click on the item menu > view workflow history (see above).  Then select your workflow instance.  The goal is to troubleshoot and tweak your workflow until it does exactly what you want it to do.  As promised here are the double E's mentioned in part 1.

 

Workflow Effectiveness: Ensuring that the workflow actions work together following the logic implied to complete a process which produces the intended results.

 

Workflow Efficiency: Ensuring that the workflow accomplishes the intended results with minimal expenditure of time and effort (resources).

 

Everyone wants results, but are you getting the right results?  The scene in the movie Office Space, from which the meme at the beginning is taken, is really funny; however, it provides some good insight into the question of how to make work flow matter.  Being both effective and efficient can help determine the difference between a process someone is willing to work with and a process someone is willing to find a work around.

 

Nintex again helps by providing some great web parts for management and reporting. Two web parts that I would recommend you incorporate into your workflow strategy are:

  • My Workflow Tasks: this is helpful to put on a personal page or maybe even the site home page.  It provides a quick view with link to the workflow tasks that the signed in user may need to perform an action on.  Essentially it helps your users complete their task faster, by being able to find them and complete them from one central view on your site.

  • Workflow Report Viewer: This web parts is useful from an Admin’s perspective.  You can see the workflow reports for Nintex from within a page on the site. This is helpful for tracking your workflows such as the ones that have errors, are overdue, or are in progress.  There are about 10 reports that you can use to help manage workflows within your site collection or site.

The two above web parts can help your users’ do more productively and it gives them visibility into information that they can use to do their jobs.  There is nothing like having good data to support your claim that work flow matters.  Now who wouldn’t want that?

 

In summary, when you build workflows, check on them to ensure they are doing what you intended? If you are archiving data, how much are you archiving and where are you storing it?  If using workflows to break permission inheritance, understand the effects of that on your farm and ensure that the right people have the correct permissions. Use the information from the reports to find ways to do workflows better, decrease running time, or just to show why your workflow is helping.

 

Stay tuned for part 3 where I will discuss a specific use case setting a Training Events Calendar using the steps outlined above.  Part 3 will include an example list and workflows for you to download and use as well.

 

Thanks,

Eric

For those out here that have followed a lot of my posts on this Community or just seen some of my blog posts on my companies blog at Summit 7 Systems, I want to take a moment to say thanks for reading them.

 

I’m encouraged by many of you to keep writing and as I aim to do better and achieve more with the tools I have, I want to share that insight with you as well.  Also a special shout out to David Deschere for being a great reviewer and always providing positive feedback on my posts. Much appreciated .

 

To that end, I know we all are pressed for time, so I’m making this blog short and sweet.  This post will be the first of a series of post aimed at providing some basic but necessary logic and thought processes that is often overlooked or forgotten when it comes to using Nintex forms and workflows in your organization.  I will endeavor to dive deeper with each post to help users from all levels use Nintex more efficiently as we go along.

 

Hope you enjoy this short read and that you learn or remember something from it.

 

 

Part 1: Does your workflow have a purpose?

Just as it is a natural desire to have an impact in your workplace, and to know that what you do matters to your organization; you should approach your workflows with the same consideration.  The image above makes a very profound statement: “Prioritize what matters”.  Yes, that sounds odd when referencing workflows, but why not put some thought into what you are about to architect or create?  How is your logic, the process you are about to automate, and the results going to affect your organization in the end?

 

Priorities help you see what’s important!

 

When creating a workflow, ensure that your workflow was built with a distinct purpose.  Too often I’ve seen people try to automate everything from the making coffee in the morning to turning off the lights at the end of the day.  Some stuff was not meant to be automated by a workflow and that’s okay.  Also, do not try to fix everything in one workflow or solve an entire business process in one big sweep.  Simplify what you are doing, prioritize your logic, and use as few actions as possible to meet your needs. This is not a formula but a mindset and here are some additional thoughts to consider:

  • What are you really wanting your workflow to do?
  • Can you accomplish your desired result in just one workflow or do you need more?
  • Are you using the right workflow scope (Item, Site, and Site Collection)?
  • Are you using the appropriate workflow actions?
  • Do you have unnecessary loops, run-if’s and conditions?
  • Are you overusing the “log to workflow history” for the sake of seeing outputs?

 

Following this process can help you create a workflow that you will be proud of.  You may also be able to show value by making it reusable within your organization,, who knows.  Now that’s “ninticity” for you, and like I promised, I kept this one short.  For more guidance with Nintex and basic workflow management, check out the DUCERIM Process.

 

Feel free to leave comments about this blog or questions you may have about Nintex and your organization.  Stay tuned for Part II: The double "EE’s" of workflows.  and if you can guess what the “E’s” represents, shoot me a comment or tweet @eharris04.

 

Thanks,

Eric

Have you ever had a problem that you knew was possible, you've seen it before, or you just know that the fundamentals of the problem should be solvable.  We I will admit that I had one that stumped me for over two weeks.

 

I was talking to a friend of mine about using Parent/Child List items and how to automatically tie them together and create them within one form.  Without hesitation, I was like, "Sure that should be simple, just input information into one form, then use a workflow to sift through (loop) and create child items from the one list."  Note to self: Do not commit to a solution before writing it out!

 

Honestly that sounded really simple in theory and should have been, but when I started down the reality path of developing the solution, it became a real brainteaser.  I thought about using InfoPath, SharePoint, and Nintex Forms, but each time I got stumped at how to exactly get the child items into the list in the first place.   After spending several hours looking through this one night I ended up in tears.  Well let me paint the picture differently, it was so frustrating that I let out a cry for help.   Then as if by a stroke of genius, I figured it out and well, the rest is history.

 

So I am now writing this to save you from the long hours of pain of staring at your computer screen.  Please dont do that.  Its not worth it, just read through this, see if it makes sense, and then download the attachments and be happy.  Don't stare at endless errors wondering why the form or workflow is not working correctly.

 

Concept:

The premise of this is not for everything, but useful when you want to track Parent/Child Items.  What this will allow you to do is create one form for entering the Parent information and the child items, then track those items in two separate list for reporting and other options.

 

I will not go into the depths of SharePoint or Nintex on this, but communicate the concept and steps taken.  If you dont understand a certain step, shoot me an email and remember what I said above, please do not stare at this stumped its not that serious.  Really, thats why Im writing this, to show it can be done.

 

Kudos, Props, Much Thanks, Cheers. Hopefully you get the point

First off, thanks to Vadim Tabakman for the start of my solution in his blog.  I'm sure everyone that has looked at doing repeating tables in Nintex has read his blog in some form or another.  If not, umm...what are you waiting on, click here.  It was his workflow piece that I used to get the child items piece for my solution.  After going through each piece of his workflow, I was able to figure out what steps to add in to make the child list work.

 

Are you ready?  Lets dive in.

 

Step 1: Lets create our Parent and Child list.

Parent List: Test Repeat is the name I used for my list.  Click here to download the .stp file.

ParentList.png

 

Child List: Child List is the name I used for my list. I know really intuitive huh?  Click here to download the .stp file.

ChildList.png

Note: Remember this is a simple concept; you can do much more with this if you desire.

 

Step 2: Now lets modify the form on our Parent List.  To do this, got to your list, and select Nintex Forms (See screenshot).  If you want to get going quickly, click here to download the list templates which should include the form preloaded.  You can then skip to Step 5.

SelectNintexForms.png

  1. Delete the forms controls for MyRepeatingSection and DetailTable.
  2. Add a repeating section to your form
    1. repeatingsection.png
  3. Name your repeating section "MyRepeatingSection" and Connect it to the MyRepeatingSection column. (This is a testing step and is not needed if you know how to write XML. I recommend doing this only at the beginning.  This will allow you to grab the XML that you will need later in your query. )
  4. Drag the label and text field for FirstName and LastName into the repeating section
  5. Format it with colors or whatever as needed, then save and publish the form.

 

If you're a brave soul that wants to figure out some of this manually go to Step 3 first.

Form(ConnectedRP).png

Step 3: Create a test item to grab your XML and copy it to notepad to hold it.  Now go back to your form and disconnect your repeating section. Save and Publish it again so that its setup correctly for the workflow.  This is IMPORTANT, so that your workflow will work correctly.

grabxml.png

Form(NotConnectedRP).png

Step 4: Create the form, import the template, save and publish it.

Form(Complete).png

Step 5: Create a Nintex Workflow connected to the Parent List.  Use the blank template and when it opens up click on Import.  Click here to download the workflow to use as a template.  I am choosing not to go into details so that this isn't a really, really long blog.  But, don't fear, I have attached the screenshots for each action in a zipped folder for you.

CreateWorkflow.png

 

Step 6: Once the workflow loads, ensure that each action does not have an error on it.  If it does, double click on it and configure the settings.

Updated

Based on some feedback and the workflow not importing the UDA correctly, I have added that as an attachment below. The Get Forms Repeating Data UDA needs to be imported before the workflow will work. It will still need configuration, but this should help out.

Step 7: Test your form and workflow.  This should work and you should see an output of the data in the list view as shown below.  If you are not seeing that, go back and make sure you have your fields named correctly and that your workflow ran with no errors.

ParentListWItem.png

------- Parent List Output Above -------

ChildListWItems.png------- Child List Output above -------

 

That's it.  You have just created two list, a form and a workflow that will generate child list for your users.  This application can be used for many things, and hopefully gets you started in the right direction for a solution.  Now that's what I call ninticity which is short for simplicity with Nintex .

 

Oh yea, one more thing, share your comments and thoughts on it, what would you have done differently, and do you have any cool tricks with the table that you can do?

 

Happy Nintexing,

Eric

Hello fellow Nintexers.  This is my Happy New Year post and why not bring it in with some humor?

 

If you're like me, and enjoy working with others, then Nintex is one of the best tools to use for organization using SharePoint.  After a fantastic year with several clients, I decided to go back through my projects and help tickets to see what were the top 5 things I saw being done wrong with Nintex.  Its definitely not comprehensive, but it can help shed light on things you should probably avoid if at all possible.

 

So without any further waiting, click on the attachment below.  Each mistake includes a tip to help to prevent it or avoid it if at all possible.

 

Oh and because this is not comprehensive, share things you've seen and maybe we can build an even bigger list for people to avoid in 2015 (yes this is repeated in the presentation for emphasis).

I recently had request from a client to show current items in a list for users to preview as they created a new request.   The actual requirement is listed below.


Requirement:

Allow users to view list items from the current list.  Users should be able to enter the “ID” of the item they want to see in a field on the form, and the form should process and return the fields of the item they specified.


Diagnosis:

I know some people may be thinking about using views, filtering fields and using a query, or perhaps even using a lookup field to achieve the results.  While there are a few different ways to achieve this that I explored, some with extra code, I decided to use a built in function that was native to Nintex that seems to fit the bill quite easily.


Solution:

ehnin1.png

The solution has a few pieces working together and could be greatly complicated depending on your list and form view, but here is what I did to show this functionality:

  1. Current List Form
  2. List View
  3. Labels
  4. Single line of text field (used to capture the ID to filter on)


That’s it.  Seriously, that’s all I added, but it’s connecting them to make the solution work.  I didn’t complicate it because I wanted to focus on the functionality, but there are plenty of additional things that can be done for this to make it nice!  Please note this was configured for Nintex Forms on SharePoint Server 2013 using their trial version. So let’s see how I made this happen.

 

ehnin2.png

The first thing was to make a simple list.  The list in this case was called “TestForm” and contained four fields:

  • Title – default SP title field (Single line of text)
  • Test1 – single line of text field •Test2 – single line of text field
  • Test3 – choice field with drop down options (I used the default ones here for simplicity)

 

After creating the list, I created three test records to have available when I needed to test the form.   So lets get started.  Navigate to the ribbon and access the Nintex Forms button.  Either click on the logo or Customize the Item Form as in the picture below.

ehnin3.png

Once the new form opens in Nintex designer, I started with the basic form and highlighted all the items, then dragged them down to create space for the new fields.

ehnin4.png


From the General section on the left, select the following: Single line of text and set the name to “SetID”.  That’s all you need to do for now.  SetID does not need to be connected to anything since it will temporarily store data we will use for filtering the list view.

ehnin5.png

From the SharePoint section on the left, select the following: List View.  Access the settings and fill in the following information as below, or to match your site information.

ehnin6.png

You will see a warning bar in yellow, alerting you that some additional configuration is needed.  So let’s see if we can get rid of that warning.  See below:

ehnin7.png

  • Source site: / I used the backslash to signify the root site.  You can also click on the green arrow and it will bring up the sites that can be selected.
  • List – this is the list name “TestForm” •View name – type in “All Items” for now.  This takes straight text here so don’t use the “.aspx” name here
  • Filter list items – “by a controls value” (this is where SetID comes to work)
  • Where – “ID”
  • Filtered by Control – “SetID”
  • Resizing – “No”


So if you are following along you can now see that we want to display the list TestForm, where the items ID is equal to the value entered in the SetID field on the form.  I also chose no resizing so the results would not overflow my form but stay within the boundaries I set.


Before going to far, let’s test this to see if it works.  Navigate to Nintex Forms tab in the browser and hit preview.  The reason for using the preview is that it gives you the ability to view your form without saving or publishing it.  Saves you some time in case you don’t like the changes you made.

ehnin8.png

You should see something similar to the screenshot below.  If not, go back and walk through the steps again.

ehnin9.png

While this does not look pretty, let’s enter a value to see if our setup worked.  Hoorah! I hope yours worked.  If not, shoot me a comment.

ehnin10.png

Fine Tuning:

Now that I know it works, I went back and added a few more things to make it look better and give the user a few instructions on how it works.   Here’s what I did:

ehnin11.png

  1. Added a rule to the List View to only show when SetID was not empty or null. “isEmptyorNull(SetID)”
  2. Added a label with bold text set to 11 with the words “Enter ID below
  3. Added another label with the instruction text
  4. Made the list view smaller so that only the title of the columns and the one line would show up.

 

That’s it “Simply #Ninticity”.   You should be able to create a new item, enter the ID if you want to view the other items and proceed.  Know of other things to make this look pretty?  Leave a comment with any questions. Also tweet me your comments @Eharris04.  This post can also be found on Summit 7 Systems website as well if you want to find other post similar to these.

Filter Blog

By date: By tag: