Elczar Adame's Shared Points on SharePoint


Why? Because it simplifies web conferencing and instant messaging anywhere we are.

It simplifies my awareness of the presence of my contacts.

It simplifies management of my contacts.

It simplifies tracking of my communication history.

It simplifies management of my online meetings even with people outside my organization or people who does not have Office 365 account.


It simplifies instant messaging.

It simplifies online meeting presentation.

It simplifies online meeting dial-in.


It simplifies online meeting invitation.


It simplifies online meeting invitation in Outlook.


It simplifies joining in an online meeting from Outlook calendar.


And a lot more why I love Lync Online in Office 365.

Advertisements

As we all know, our private site in SharePoint Online is only accessible to people inside our organization. But how about if we need to share a content, like meeting notes, to someone outside our organization? Yes, nothing to worry and it is absolutely possible.

Below are the steps that we could follow to make it working.

1. Initially, let us go to our SharePoint administration page in Office 365.

2. Let us select a site collection and set its Sharing option to “Allow both external users who accept sharing invitations and anonymous guest links”.

3. Let us select a content we want to share to people outside our organization by sending him an invitation. In this demonstration, we will be sharing our notes on Introduction to Office 365.

4. Automatically, the recipient of our invitation will receive the link in his inbox.

5. Upon clicking the link on the invitation, he could now access the content we have shared. If we are sharing a Word, Excel, PowerPoint, or OneNote document, the recipient of our invitation needs not to have Microsoft Office installed in his local machine.

I hope this would help.


To complete my previous posts on Client-Side Rendering in View Form, Client-Side Rendering in New Form, and Client-Side Rendering in Display Form, I am sharing the basic JS lines we need for the Edit Form.

Hope this would help.


Continuing my previous posts on Client-Side Rendering in View Form and Client-Side Rendering in New Form, the implementation in Display Form is as well straight forward.

We only need to write some lines in our JS file.

Hope this would help.


The same with my previous post on Client-Side Rendering in View Form, this post will not discuss as well the WHATs and WHYs of Client-Side Rendering but it will provide a demonstration of its HOWs in SharePoint Online and On-Premise.

What to be expected after the steps below? Based on user permission, the column New Form Column will be accessible. NOTE: This post will not demonstrate a column-level permission solution but it will guide us on how to manipulate a column in a New Form.

  1. I started by creating a SharePoint solution in Visual Studio. Since it is designed for SharePoint Online and On-Premise, I have chosen sandboxed solution as its trust level.
  2. In my solution, I have added a List module to create a document library that will hold the .js file that we will be creating in a while. I have named the document library as View Form Assets.
  3. Then, I have added a module with NewForm.js file. This file will be discussed in the succeeding steps. At this point enough to have a blank .js file. Notice that the URL of the .js file is pointed to the document library we have just created.

  1. I have added as well a Site Column or Field Element in my solution. I have named the field as New Form Column. This is the text column that we will manipulate later. Please note of the JSLink property. It is pointed to the NewForm.js file that will be stored in the New Form Assets document library.

  1. Now is the NewForm.js file. It simple as having few functions.

NOTE: As I have mentioned above, this post will not demonstrate a column-level permission solution but it would fundamentally guide us on how to manipulate a column in a New Form. This is the reason that I have not included a screen capture of the PortalIntegrators.HasPermission function.

  1. After building my solution, I have just deployed the .WSP file in the solution gallery and activated the feature.
  2. And finally, I have added the New Form Column in my list. With that I could now enjoy using a customized column in my New Form.

    Hope this would help.


Client-Side Rendering is a new concept available in SharePoint 2013. This number of posts will not discuss the WHATs and WHYs of Client-Side Rendering but it will provide several demonstrations of its HOWs in SharePoint Online and On-Premise.

There are several ways to customize a column in a View Form, but in this piece I will demonstrate the steps that I have followed:

  1. Initially, I have created a Custom List with a choice/dropdown column named View Form Column. The column has a selectable values of Pending, Approved, and Rejected.

    What to be expected after the steps below? The values in the View Form Column will be replaced by graphical representations. This is not to mention that it could be replaced by any HTML object.

  2. Then, I started creating a SharePoint solution in Visual Studio. Since it is designed for SharePoint Online and On-Premise, I have chosen sandboxed solution as its trust level.
  3. In my solution, I have added a List module to create a document library that will hold the .js file that we will be creating in a while. I have named the document library as ViewFormAssets.
  4. Then, I have added a module with ViewForm.js file. This file will be discussed in the succeeding steps. At this point enough to have a blank .js file. Notice that the URL of the .js file is pointed to the document library we have just created.

  5. I have added as well a Site Column or Field Element in my solution. I have named the field as View Form Column. This is the choice/dropdown column that we will customize later. Please note of the JSLink property. It is pointed to the ViewForm.js file that will be stored in the ViewFormAssets library.

  6. Now is the ViewForm.js file. It simple as having three functions.

  7. After building my solution, I have just deployed the .WSP file in the solution gallery and activated the feature.

  8. And finally, I have added the View Form Column in my list. With that I could now enjoy using a customized column in my View Form.

    In my next demonstrations, let us attempt to customize the column in an Add Form, Edit Form, and Display Form.

    Hope this would help.


I had a chance to talk with a technical writer of Microsoft on SharePoint 2013 workflow, and foremost a good friend of mine, that inspired me to share this piece: the workflow actions in SharePoint workflow platform that I love most.

I have started by creating a SharePoint 2013 Workflow in SharePoint Designer 2013. To configure SharePoint 2013 workflow, please visit my previous post on Workflow Configuration in SharePoint 2013.

And these are the new features that I love most:

For reference, please visit http://technet.microsoft.com/en-us/library/jj164026.aspx .

Tag Cloud