Skip navigation
All Places > Getting Started > Blog > 2017 > July
2017

Question:

I absolutely love the option of creating ‘pages’ in a form, which is an option in InfoPath. I start with the first page to ask the user a question. Depending on the selection they make, it will flip to a new page to ask additional questions or asks the user to fill in information. Once complete, they click submit and it flips to the final page saying thank you and provides any additional information.


I also like the ability to create new pages based on what the user is doing, i.e. new item or edit item. If it is a new item, I start with Page 1. If I am editing an item, it starts with Page 8, which has all the information in read only format. Simple and easy to work with.


However, the concept of ‘pages’ in Forms does not exist. It looks like I have to add ‘sections’, and then determine which one should be active based on a ‘value’. That does not make any sense to me. Why is such a simple concept so difficult to implement in Forms?

 

Answer

 

There are a few ways that this can be implemented. First option is to use tab functionality like was mentioned.  The second option would be to use JavaScript to switch the views.  I can follow up with the product team to see if there has been any movement on implementing this functionality natively, but the blog posts below can provide some options:

 

https://community.nintex.com/docs/DOC-1361

https://community.nintex.com/docs/DOC-1198

http://www.slfiene.com/blog/2015/10/19/a-new-fantastic-point-of-view-slide-ux-for-nintex-forms

 

Question:

I have some ability to adjust the width of the ‘table’ in InfoPath. So if I want to show that form in a web part that is only 33% of the page, I can make the table 150px wide, which will fit into that web part. The problem is that it isn’t responsive, so the smaller I make the screen, the more it will bleed into the web part next to it.
In Forms, I so far have no seen a way to create a form that is responsive, so putting it in a web part that is 33% and then making that form responsive based on how big or small the screen is just does not work. It seems no matter what I do, the ‘window’ of the web part is a certain size, so it always seems to expand beyond the 33% that I have designated as the web part size. Am I missing something here?

 

Answer: 

We should be rolling out responsive forms later this year.  This release should address the needs described above.  The one caveat here, is that the responsive forms will not support custom JavaScript.  We will still have the Pixel Perfect forms (current product) available if there is a more complex design requirement, and the user designing the form will have the option on which form type to deploy.

 

Question

In InfoPath, when I want to setup a conditional rule, it is simple – If x is No, do this. If x is Yes, do that. It is a simple selection of which item I want to be x, select the conditional item (equals, greater than, less than, etc.), and select the result. Again, I like seeing the options and knowing in plain language what it will do.

 

Forms however does not take that approach. It seems even the simplest of needs requires knowing the JavaScript language to accomplish the need. To do a conditional rule in Forms, you have to write it up in a JS format. I do not know what that format is, so I now have to research how to do it, which takes it more time. This is not making the best use of my time, especially if I am just trying to put together a simple form.

 

Answer:

The help files have some pretty good information on how to configure rules and the operators: http://help.nintex.com/en-US/nintex2013/help/#Forms/RootCategory/Designer/Nintex.Forms.Rules.htmhttp://help.nintex.com/en-US/nintex2013/help/#Forms/RootCategory/Designer/Nintex.Forms.Rules.htm

 

If the JavaScript operators are not ideal, there is also the capability to configure runtime functions, which may make more sense coming from the InfoPath world.

http://help.nintex.com/en-US/nintex2013/help/#Forms/RootCategory/Designer/Nintex.Forms.RuntimeFunctions.htm

I'm very excited to see the new Scheduling features for O365 Workflows. As first read from Tee Up Your Work - Scheduled Workflows Are Available for Office 365! we learned the basics of scheduling site workflows. So I ran a few site workflows myself and could not find the history that they executed. My first test workflow would send me an email, since I received the email I knew it was working. But there was no evidence. Typically, I would go to Site Contents from the suite menu gear, then click on Site Workflows.

I then see my normal screen of available site workflows to run, and which are still running or completed. Notice in this view I don't see anything in the completed section, yet I had the Email Site Workflow scheduled to run and it executed.

What I found was, by clicking on Show All Workflows, I then see the completed scheduled workflows.

 

Clicking on the workflow name will then display the workflow history associated.

 

 

The reason this was required is that the workflow executed under elevated App permissions. Notice the userID is app@sharepoint. So by selecting to show all site workflows I then could see workflows completed by the system.

 

 

A couple of key notes to follow:

  1. Keep in mind you can disable these schedules and schedule data will be retained for 90 days after the final execution so you can quickly reference your prior work. This means specifically the schedule rules for the workflow from the workflow gallery. This is not related to History data.
  2. History for each workflow instance is saved to the history list specified in the workflow settings, typically the default site workflow history list. In SharePoint Online, the Workflow Auto Cleanup job permanently deletes workflow instances and related task entries that still exist 60 days after a workflow is completed or canceled. You can regularly export the workflow history list if you need to save the workflow history for longer than 60 days, or contact your Farm Administrator to reconfigure job settings.
  3. To view the default site workflow history list

    Append the following to your site URL:

    /Lists/Workflow%20History
    For example, if your site URL is https://example.sharepoint.com/sites/hr, then the appended URL appears as follows.
    https://example.sharepoint.com/sites/hr/Lists/Workflow%20History

  4. To enable scheduled workflows, the following SharePoint site feature must be activated by your site administrator:

    Workflows can use app permissions

    This feature remains inactive until it is activated.

Many of you, like me, will have seen and used this feature many times.  What does it do?  Well it allows you to add a shortcut to your start workflow page directly on the item context menu.

These are the settings you need on workflow settings:

 

This then, when the workflow is published, displays as such on the item context menu:

 

Now I have been using this awesome feature for many years and then Paul Crawford asked me why he seemed to be limited to only adding four workflows to the menu?!  I have never needed to add this many before so wasn't aware of any limitation... 

I won't pretend I solved it, because I didn't, but he came up with a quick fix that I wanted to blog about so that neither of us forgot this simple trick:

 

Rather than using Menu item position: 0, 1, 2, 3, etc

Have Menu item position: 100, 101, 102, 103, etc

Hi all and welcome to a new Community Mission!

 

In this mission you don't have to build a form, you don't have to build a workflow so..what you are requested to do?

Just a simple fix on an existing workflow that currently has some issues..attached to this post you can find all you need for your environment (there is a zip file for who is on O365 and one for on-premises).

 

You just need to have Nintex Workflow and Nintex Forms installed and then you can start setting up your personal playground.

 

How to setup the scenario:

  1. Import the three list templates that are in the zip (they template are for an English website)
  2. Create a list for each template (you should use template name as list name)
  3. In list "CommunityMissionDestination" you have to create a lookup column based on the settings shown in LookupConfiguration.png (the image is in the zip)
  4. In list "CommunityMissionSource" you have to import the Nintex Forms available in the zip and publish it
  5. In list "CommunityMissionSource" you have to import the workflow (for O365 users, remember to fill last action with valid credential) and publish it.

 

Now, what the workflow should do? Every time a new item is added in the CommunityMissionSource list, it should check the repeating section that is present in the form and create one item for each row in the CommunityMissionDestination list. That's all? Not exactly.. last requirement is that for item in CommunityMissionDestination, "Type 1" value in the lookup field should always be selected, even if it wasn't selected by the user in source item.

 

Once you've fixed the workflow, post your exported workflow as a document in the Nintex Gallery briefly explaining what you did! (Visit the space, click "actions" and then select "document" from the dropdown. You'll see a place to attach your file in the editor.)  Reply below with a link to it.

 

fixit badge

For your repair skills, you'll earn this badge and 100 points..good luck!

Each month we name ten people to an "honor roll" in the community to highlight their contributions and encourage you to connect with them.

 

Congrats to the Nintex Connect members below - and THANK YOU for your contributions!

 

I encourage everyone to "follow" each of them. Here's how: Just hover over their names below and then click "follow" in the card that pops up, or visit their profile pages and click "follow" next to their name in the banner.

 

Why do this?  Because following puts their activity in the news stream of your choosing and exposes you to how leading community members are engaging in Nintex Connect.  You'll see what content they're creating, and responding to.  It's a great way to enrich your community experience.

 

This month's Honor Roll members to follow:

 

 

honor roll big

 

Honor Roll members will get this badge in their reputation center, along with 100 points.

 

This is not an undemocratic process!  If you'd like to nominate someone for the honor roll next month, post their name below and tell us why you think they should have a bigger following!

We're scarcely half way through 2017, and we've already seen one community member attain Rock Star status!

Congrats to Marian Hatala, who is a Nintex customer and member of our community Blue Ribbon Group!

 

Marian spends a lot of time in Nintex Connect answering questions.  His advice is always to the point and he really knows his stuff!

 

Thank you, Marian!

 

The Blue Ribbon members do a lot to help others in the community. See the entire list here: Blue Ribbon Group for 2017 Announced!

Find out what it means to be a Rock Star here: Be a Community Rock Star! 

 

See where you rank by visiting the homepage and finding our leaderboard in the lower-right corner.  Or, visit your profile (click: Avatar>view profile>reputation).

 

profile marian

 

Find out about how to collect badges and points and work your way up that community status ladder here: Badges and Earning Points on the Site

 

You may want to "follow" someone who provides a lot of valuable information. Just hover over their name in the community and click "follow" on the card that pops up. Or click their name and visit their profile page and click "follow" next to their name in the banner.  You'll then get notifications of their activity. A good group of people to follow are those in the Blue Ribbon Group, or the people who make the monthly Honor Roll.

You can see those here:

New: A Monthly Honor Roll

Honor Roll: June 2017

Honor Roll: July 2017

 

Maybe you, too, can reach rock star status this year! Still lots of time to find out!

Filter Blog

By date: By tag: