We are pleased to present below all posts tagged with 'Workflow'. If you still can't find what you are looking for, try using the search box.
I recently had an interesting issue with a client’s SharePoint environment that I wanted to hopefully help someone else out as it wasn’t the most intuitive cause. What do you do when you try to save list items or InfoPath-customized list items and it fails? It turned out to be really simple if you know what to look for.
I’ve had this come up multiple times lately, and I thought I’d put up a post to help get the information all in one place. Now that we’re moving away from SharePoint 2010 and dealing with SharePoint 2013/2016/Online more often, folks still want SharePoint Designer but are confused which version they need. You want to be sure to get the latest and most patched version, which requires more than one download.
On a recent client project, we’re working to implement a task-based tracking solution in SharePoint 2010. There is a parent Project, and that Project has a template set of tasks the workflow creates with due dates. Then the requirement came up where if the Project due date changed, all of the task due dates needed to be updated to. Read on to see how I show you an easy and simple no-code way using workflow to tell if a field changed.
You've been there, we all have. At one point or another, we loved InfoPath and were disappointed at the news it would be discontinued. We waited with anticipation to see what was going to replace it. It's been quite the gray unknown for a long time, and in part the Ignite conference this year didn't make any overwhelm anyone with any big announcements in this regard. But that doesn’t mean there wasn't one.
Keep reading to get my thoughts and what was announced and where the planned future of InfoPath is going.
Thanks for staying with me as I walked you through the basics of workflow in our favorite intranet platform – Microsoft SharePoint (and I’ll see you at the Ignite Conference at the end of the month!).
To wrap up our series, I wanted to talk a little about some best practices with workflow then offer some ways that you can extend your workflows.
I trust that you’ve been following me in this 101 series on workflow, so welcome to part 3! Today we’re going to focus on getting SharePoint Designer going, reviewing the interface for workflow and creating some workflows. Get ready, this will be a long one! There’s a lot of info to get through, and I give you different steps between 2010 and 2013.
Welcome to part 2 of our introductory blog series on SharePoint workflows. Now we can venture deeper into the depths of your workflow adventures. We’ll cover how to use the default workflows, more details on workflow structure and we’ll wrap up with working with workflows. In the next post, we’ll crack open Designer to see how we can create some workflow.
With most clients I’ve worked with over the years, I inevitably get asked the same thing sooner or later – “what’s workflow?" Or it’s “teach me about workflow,” or “how do you customize an default workflow?"
With this blog series I want to try to take explain some core concepts of workflow, then give some direction on creating them, the interface, customizing the default ones, some best practices and some ideas on extending them. Sounds like a lot, and it is! There are 2 and 3-day training courses just on workflow, but my goal is to give you some basics and direction to get you going with your adventure with SharePoint workflows. I won’t go into many step by steps on building a sample workflow, but I want to help you started.
Why are we talking about Nintex? If you’ve taken a look at their site lately, they have a lot going on!
In today's post, I'll review some of the latest changes and new functionality coming from Nintex and look forward to great things from them in 2016.
Have you ever opened SharePoint Designer, clicked on Workflows, and saw nothing? I sure did and was able to fix it. In today's blog post, we'll do a quick primer of SharePoint reusable workflows, then I'll discuss the problem and all the troubleshooting I did to try and fix the issue. Finally I'll review the magical steps necessary steps I took to actually resolve it.
I’m in the midst of two different major workflows for clients right now, one of them being an HR New Hire Onboarding request and approval process. One small but critical requirement of the process was that each level of approval needed a two business day wait period. In this post I'll demonstrate 2 easy ways to be able to calculate working or business days inside a SharePoint workflow.
See if this sounds familiar:
Someone asks you “Can I get an email reminder for these events on the team calendar?”. You think well, we can set alerts, so you go look into the alert settings, so you go look into the alert settings, and quickly realize that alerts don’t work like that. The alert mechanism in SharePoint will send the alert subscriber an email based on an action happening on the item (it is being created, edited, etc). We need the trigger to be based on a date. So what to do?
While working on a client request recently, I came across a way to easily work with date and time values in a SharePoint Designer 2010 workflow. I was able to solve this using only SharePoint Designer. I reviewed other solutions, and I will give links to a couple others in case they are needed. This worked for me, and I didn’t see anyone else with this exact solution so I thought I would share for the greater good.
In deployments with a decent amount of workflows that fire constantly (i.e., system jobs are spawned), the amount of records placed in the AsyncOperationBase table is quite impressive. However, when these system jobs complete (canceled or succeeded) they remain in this table until you decide to purge them. When these tables begin to grow into the millions of rows it imposes undue performance issues on the Async service and overall system performance may suffer as well.
Using Global Option sets in CRM 2011 can simplify the process of mapping option sets. But what if you have a local option set in one entity and a global option set in another? This blog explains how to map data from a local option set in one entity to the equivalent in another via workflow.
Have you finally gotten users to start creating contacts in CRM only to find out that they are often forgetting to associate them with an account? For B2B organizations, this can become a significant data quality issue. Most B2B organizations are business centered rather than contact centered. What this means is that users tend to use the account entity in CRM to search for information. So if a contact is not associated with an account, then users are not nearly as likely to find it. This problem is exacerbated by Outlook integration features, such as the ability create a new contact directly from an email address. In this blog, I’ll offer a couple of practical solutions to aid you with creating higher quality data by ensuring that the Parent Customer field is always populated on contact forms.
Every so often while working in SharePoint, you encounter a feature that has almost no documentation or you can’t find anyone with a similar issue. This happened to me when I was trying to configure a workflow to move a document set to a Records Center. After I got this to work, I wanted to try and save others the grief and frustration that I experienced. If “Unknownerror” means anything to you, this post is for you.
This action might be useful in document management scenarios, where documents have a formal “approval” process, and management policies are defined to “expire” them to meet retention policies. Once expired, they would be removed from the current location and moved to another location, specifically a Records Center in this case where they sit waiting to be purged from the system.
On a recent Salesforce implementation, we identified a need to map a single lead field to two different fields - one on the contact and one on the opportunity.My initial thought was to create a trigger to fire on lead conversion that would populate the second field. However, I always try to look first for a non-coding solution. Which brought me to the fairly simple idea of creating a second field that would use a workflow field update to copy the value of the original field. The new field would be hidden from the users, but would be used for the sole purpose of mapping to the second destination field. I thought I'd found the perfect "clicks not code" solution ...until I realized my field was a lookup field, a field type that can't be updated by workflow. Drat.
Which clients should we focus more time on? Are there any clients that we should consider firing? How can we find new clients that look like our best current clients? Do we have clients that should be more profitable?
These are the questions that many B2B firms are asking themselves as they think through how they should prioritize their client list. So read on for some of the how’s and why’s of establishing a client scoring system.
It's the week after Microsoft unveiled Dynamics CRM 2011 at the Worldwide partner conference and my head is still spinning from all of the great new features and strategic improvements that will be coming soon. Read on to learn about a small number of the most powerful additions you can expect to see in Microsoft Dynamics CRM 2011.
The failure to understand and execute an effective activity management process is a leading cause of poor CRM adoption. There are a variety of issues that can make activity management confusing and frustrating for users in ANY CRM system. In this posting, I've detailed 11 suggestions for improving your activity management process.
This is only a starting point. Proper use of Queues and Workflows - in particular - are areas that can also improve your activity management efficiency and results.
This article describes how to use the workflow in Microsoft Dynamics CRM 4.0 to trigger an action based on a date field in a CRM record.
Duplicate Detection is a great feature in Microsoft Dynamics CRM 4.0. But it can also be a pain. Do your users complain that whenever they convert a lead, they get a duplicate record alert when trying to save the contact - and the alert continues to pop up on all future saves? Good news - there is a pretty simple fix for this problem.
Read on for more information on this issue and how to fix it.
Oftentimes, you will want to copy an existing Microsoft CRM workflow. You might want to create a similar workflow with a few minor changes. Or, you might have a workflow that is "in production" and you need to make some changes to it - but you don't want the current workflow to be unavailable while you're making changes. But CRM doesn't provide a way to copy a workflow - this entry explains a quick and simple way to copy a workflow in Microsoft Dynamics CRM 4.0.
[Read the full entry for the "how to"]
We implemented a workflow that was frequently failing with a message stating "the text entered exceeds the maximum length." Fortunately, the fix was fairly easy.
[Read the full entry for more information]
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.