As promised; its public now and you can download my first SharePoint 2013 Administration Workshop from here: http://1drv.ms/1LvsOau
I used to write PowerPoints only, since this is my first writing workshop; your comments are highly appreciated [not public J]
I know some of you really need to see the installation from scratch, I will be pushing this out very soon, just keep following me.
Now I need to get some sleep J
Good night SharePointers
Dear SharePointers, you are all invited to the Cairo SharePoint Saturday, so far speakers have very good content they want to share with you, it’s a chance to meet with SharePoint experts and ask them questions.
This event is a chance for everyone want to learn SharePoint, is to get inside the community, where you will learn faster J
Happy SharePointing. .. oh and Speakers are finalized and will be announced soon.
A SharePoint friend, is going to be missed really. It’s so sad as I am writing this.. I will miss you Dave, you were such a great friend, and shared great posts.
You gave me the opportunity to write with you in your blog and always shared my posts.
I finally made it and meet him, the below picture were in the European SharePoint Conference in Copenhagen – Denmark.
Rest in Peace Dave! L
Originally posted on Gaurav Mahajan:
Microsoft has published a very comprehensive set of guidelines for installing, configuring and managing Apps for SharePoint 2013. These guidelines are available on the TechNet site here: http://technet.microsoft.com/en-us/library/fp161232.aspx. Without duplicating those details however, I wanted to capture the few necessary steps for those who wanted to quickly get apps for SharePoint 2013 going on a dev. farm. Please note that the examples assume you are using the VM downloaded from my earlier blog post:
- Configure DNS entries: First a little background on why we need to do this – Each installation of an app has a unique URL in your environment. You determine the template for that URL (by determining a domain name and an app prefix), and then app URLs are automatically generated based on that template. Paths for the apps are based on the URL for the site where they are installed. When you install an app to a site, a…
View original 707 more words
In SPSCairo, one of the attendees had a problem with the marquee in SharePoint that it is not moving, I know its basic but I promised to write this post for him, because he was the only one that had this concern.
I did not do anything more than what is required to write the marquee tag and put text in between and all that was in the “Page Content” field in a page, not even “Content Editor” WP, no need cause I used the “Edit Source” to insert HTML tag.
I believe that you did not enable the animation in the Internet Options, if you open “Internet Explorer” and go to “Tools”, then click “Internet Options”; under “Multimedia” category, as below select the “Play animations in webpages”, I tried on and off and if it is not enabled, obviously the marquee stopped working.
I tried on both SharePoint 2010 & 2013 – it is the same html marquee tag that I wrote and on both enabling the animation from Internet Explorer is a must.
the marquee tag I wrote; <marquee>this is in SharePoint 2010 .. just saying</marquee>
I wrote as below screen shot; nothing else and saved it. For SharePoint 2013;
For SharePoint 2010;
Last Saturday on 6 September, we had the first SharePoint Saturday in Cairo – Egypt since the revolution. It was great to be done in ITWORX.
The day was great, more knowledge & informative to everyone J we started with a keynote by Mr. Wael Amin [CEO of ITWORX]
Then after the sessions started.. in case you missed it or you don’t know what we had, check this link http://www.spsevents.org/city/Cairo/Cairo2014/sessions
I’d like to thank the organizers J yup & Mahmoud Hamd, find how to contact us; http://www.spsevents.org/city/Cairo/Cairo2014/about
Especial thanks to Gokan Ozcifci MS MVP delivered 2 sessions, who came all the way from Belgium J Thank you Gokan.
And after our sessions & at the end of the day, we had a helpful & useful discussion with the attendees and answered all their questions & concerns.
In case, you missed that day, we will do it again soon and we’d love to hear your feedback or suggestions or any recommendations. All welcome and if doable then why not J
So we have created twitter account, Facebook page and group, Yammer group & LinkedIn group to be able to stay connected and up to date to event updates. You will see our announcements, receive emails and alerts, speaker agenda, sponsors & event photos.
So choose below the best way to stay connected J
Datapolis Process System is a visual workflow designer for SharePoint 2013 that offers a robust set of tools to simplify workflow development and deployment. At the moment it is available for on-premises deployments only, however the company plans to release its Office 365 equivalent in the future. SharePoint 2010 and 2007 are supported by older and simpler versions of that solution, branded as Datapolis Workbox.
Datapolis toolkit is integrated with the SharePoint environment, with workflow actions accessible from context menu, list, ribbon, or form, and permission and management options available in the Central Administration. Like its competitors, it models workflows using a browser-based drag and drop designer., with the workflow engine based on Windows Workflow Foundation.
The main differentiatior from solutions like Nintex or K2 is the emphasis on the state machine workflows in place of sequential ones. While you can design state machine workflows using other solutions, as well as SharePoint Designer itself, Datapolis offers that option as a default and most exposed one. As it claims, state machine workflows are more flexible, allowing rapid process improvement, and offer easier learning curve, depicting a process in a manner similar to Visio, BPM notation, and other familiar tools. Datapolis therefore positions its solution to be used for teamwork, enabling both IT engineers and less tech-experienced business people to build processes for their organization.
Similar to other workflow tools, Datapolis allows actions between each state. Within these actions, in a separate sequential designer, you can specify different functional activities which will push a process forward. It also allows storing variables and using them for comparative activities and triggers within the workflow life cycle. The model can include decision points which redirect one action to another depending on defined conditions.
Between each action, the designer can also use a standard form or a customized InfoPath form. Those forms can perform look-ups to other SharePoint lists for additional information that is sometimes needed in the process.
As for workflow security, the build-in permissions protector allows users to manage permissions on SharePoint list column level. Using filters and look-ups, you can set who has access at what time during the workflow life cycle. This can also be managed using permission groups within the workflow designer.
The new feature in Datapolis Process System are Datapolis applications. Those are said to be stand-alone objects which may contain a sub-process or group of tasks, shared by different workflows or executed in parallel. Applications can build on the basis of previously designed workflows or designed with other tools like Visual Studio. They can replace generic parts of workflows as they are stored in a single repository and modifying one application takes effect in all workflows where it was used, keeping processes coherent and up-to-date. Different applications can be grouped into solutions to unify a complex process or pull data from disparate sources. While this is a new innovation, there are as yet no practical examples of implementing it, so it will likely take some time to evaluate its effectivity.
Datapolis Process System fits in the line of tools going beyond SharePoint Designer capabilities with which you can create advanced workflows without a need to code. The choice between it and other solutions should depend on whether you prefer working with sequential or state machine workflows and if your SharePoint environment is deployed in cloud or on-premises.