I am creating a workflow using Microsoft workflow automation. One requirement is to send an email for approval where the approver needs to add one field in the email and then should hit the approve button. We then need to capture that field. I don't know how to achieve this.
I have a class registration set up in SharePoint 2013. Users are emailed when they register for a class. I want to create email notifications when the Start Date, Start Time or Location [fields] of the Session changes. I only want to email the users that have registered for said Session (between 1 and 400 people).
I should be able to handle this with an Alert or an Event, but can't figure it out. My SharePoint team is telling me that this is too difficult because "the columns are in Sessions [list] and not in Registrations [list view].
I've found a lot of information on general SharePoint alerts, but I can't find anything on sending notifications to a select group of users, based on another field.
You could create event receiver for the list and send email by SPUtility.SendEmail with dynamic users.
You could check sample code from here.
Create event receiver in SharePoint 2013.
I am using SharePoint 2010 workflow template to create approval workflow for my organization. One thing I am stuck at is how to update a field when the users cancel the workflow. It does not seems like there is any workflow parameter that capture the workflow status when it is cancelled by user.
Have a look at the Workflow History List:
http://[servername]/[sitename]/lists/Workflow%20History
The issue I'm having in Dynamics CRM 2013 is the ability to assign activities or appointments to a team and have those cascade downward into individual users. The end goal here would be after assigning a lead or activity to a team, the users within that team would receive notifications, emails, etc. and those records would integrate with their 'my' sections of CRM.
The issue I see with this is that only 1 'Owner' can be set for a new record in all areas of CRM, and the 'my' sections are based off of the Owner. Therefore the users within the team won't be notified.
We are currently using a service to pull from an existing database and populate CRM, assigning new leads to a Team which contains multiple users.
Does anyone have a recommended method to do this?
Thanks for your time.
Either give the users a view of "Leads owned by Teams of which I am a member" or possibly use Queues, which are pretty much designed for the scenario you describe.
New items assigned to a Team will be added to the Team's Queue. Users can see all Queue Items not yet being worked on (from all Queues they have access to, including all Teams they are members of). A user can "work on" an item to show they are dealing with it so it no longer appears in this list of items to be worked on, and instead appears in their own list of items they are working on. A user can either complete the item or 'release' it back into the queue.
Queues can contain items of different types, eg Leads, Tasks, Cases etc.
I have a situation where an office just created a couple of dozen shared meeting room calendars for all of their office meeting rooms. There are about 100 or so employees. The plan right now is to send a document around to all of them explaining how to add all of these shared calendars to their outlooks. We are running a mixed environment with some outlook 2010 and some 2007 clients and the exchange server is 2010. IS there anyway to "push" all those calendars out automatically from exchange or is there a VB script that we could run on each computer to automate the process of all 100 people adding dozens of calendars?
My recommendation is don't!
When you open your copy of Outlook, there is a pause while Outlook synchronises everything. One of the things it has to synchronise is any calendars. This can be a slooooow process particularly with busy calendars which I assume your meeting room calendars will be.
I have experienced slowdowns when utilizing more than 12 calendars in shared mode if the access is higher than reviewer. However, I have created my own workaround. Don't use direct booking. Use an auto-attendant based access.
If you want many people to be able to alter the events, then you can do so by checking out the following:
Situation: When allowing multiple people to access and send the same event, you give them access to one another's account in most cases. This is unacceptable by security standards.
The fix:
Create an equipment calendar that can be used as a Department Calendar. This is essentially the Exchange version of the corkboard calendar. Everybody can add notes and send the updates through from this calendar. How? Follow this paradigm: Everybody is a part of some grouping for security. This security grouping in AD is Universal. In Exchange you tie a Distribution list to the Security Group that's in AD. Now you can email the group. The group is the department.
The calendar you create as an equipment calendar will have some extra functions built in, right out of the box. Using a shared calendar or folder in public listing, you'd have to script it all yourself. Grant the group (not a single user) full access, and send as.
For the delegate, only the managers of the group or calendar (which could be a separate group that you set up to include a receptionist and the manager for scheduling purposes). Allow the boss to auto-book, along with the receptionist. The others do not.
Set the recurring policy and other policy settings. Let nobody book out of policy. This is not a room, it is a cork board. When people don't follow the rules, they can lose access. Grant access to the Distro group to the boss and receptionist. Then, allow them to add anybody on premises that's in the department. Now you have the calendar set up.
When they need to lock an appointment for editing, they go to the receptionist and have them book it, Sending it As their own personal ID, or go to the boss and have that person do it. If it's a team shared meeting that will be noted and continually edited by all, you have anybody book it and send as the cork-board.
Since they all have full access to the cork-board, they can edit the calendar, and since they have send as, they can send the updates to everybody. Now you just add the group as a recipient and they all get an invite. Set them up with sync, and they'll always be able to respond.
Have the responses marked read then autoredirect to the receptionist who can remove those who are busy from the attendees. Now you know who's at the meeting. Anybody can add themselves by clicking Copy to My Calendar, and they'll show up as an attendee, forwarding their response to the receptionist, who can make any other arrangements necessary. And so on.
If you make sure that the Calendar attaches the name of the booking ID to those events that are booked from outside it (receptionist and boss), they'll know which events they shouldn't delete. Want to forgo that ability? Script a change in their access to the calendar, set the Calendar itself to be able to EDIT OWN, DELETE OWN. Set all but manager and reception to Edit OWN, Delete OWN. Set Manager and reception to Owner access.
Now they can all still edit and send using the calendar, but only the manager and Receptionist can actually lock events.