199 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
From Blogsphere to a Static Site (Part 5) - Comment front-end
Thu, Jul 20th 2017 64
Ownership flow of customer community created cases
Sun, Jul 16th 2017 51
Using FontAwesome in your VisualForce pages
Fri, Jul 14th 2017 40
Salesforce Community License Overview
Mon, Jul 10th 2017 34
Sharing is caring - Salesforce edition
Fri, Jul 7th 2017 24
Meeting a CxO
Thu, Jun 8th 2017 5
From Blogsphere to a Static Site (Part 4) - Comment backend
Thu, May 4th 2017 2
Top 10
From Blogsphere to a Static Site (Part 5) - Comment front-end
Thu, Jul 20th 2017 64
Ownership flow of customer community created cases
Sun, Jul 16th 2017 51
Using FontAwesome in your VisualForce pages
Fri, Jul 14th 2017 40
Salesforce Community License Overview
Mon, Jul 10th 2017 34
Sharing is caring - Salesforce edition
Fri, Jul 7th 2017 24
Meeting a CxO
Thu, Jun 8th 2017 5
The Decline and Fall of IBM
Mon, May 1st 2017 3
From Blogsphere to a Static Site (Part 1) - Objects
Sat, Apr 15th 2017 3
From Blogsphere to a Static Site (Part 0) - Requirements
Wed, Apr 12th 2017 3
Goodbye IBM, hello Salesforce!
Sat, Apr 1st 2017 3


Ownership flow of customer community created cases
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
   

In a previous entry I mapped out sharing abilities the Salesforce platform is capable of.

In this entry I will put these capabilities to practial use. The scenario starts with a customer logging into the customer community and raising a ticket. Client representative, the partner and support staff need/want access to the case. The case needs to flow along the same processing as cases created by other means (call, email, IoT). The following diagram explains the flow (click for a larger version):

Customer Portal Created Cases Ownership flow

The diagram has been rendered using Websequencediagrams based on a plain text file:



---------------------
2017/07/ownership-flow-of-customer-community-created-cases.html
Jul 16, 2017
52 hits



Recent Blog Posts
64
From Blogsphere to a Static Site (Part 5) - Comment front-end
Thu, Jul 20th 2017 3:58p   Stephan H. Wissel
In Part 4 I described the comment backend. This installment sheds a light on the comment front-end. Comments can be tricky. One lesson I learned early: When your comment form is standard HTML form, it attracts spam like a light bulb attracts moths. So the requirement were: The original blog entry should not contain any HTML form. It should be loaded on a button click using JavaScript. Nota bene: this isn't hide/show, but actual manipulation of the DOM The dynamic form shall not contain a POS
52
Ownership flow of customer community created cases
Sun, Jul 16th 2017 2:53p   Stephan H. Wissel
In a previous entry I mapped out sharing abilities the Salesforce platform is capable of. In this entry I will put these capabilities to practial use. The scenario starts with a customer logging into the customer community and raising a ticket. Client representative, the partner and support staff need/want access to the case. The case needs to flow along the same processing as cases created by other means (call, email, IoT). The following diagram explains the flow (click for a larger version):
40
Using FontAwesome in your VisualForce pages
Fri, Jul 14th 2017 8:43a   Stephan H. Wissel
I'm a big fan of Font Awesome (including backing Version 5). It allows to add icons without the overhead of loading tons of small graphic files. In a recent internal project I had to integrate FontAwesome into a Salesforce VisualForce page Installing FontAwesome In theory you could load the font from a CDN. However based on security settings this might or might not work. So I decided to add FontAwesome as resource to my project: Download FontAwesome 4. Or support the team and use Version 5 A
34
Salesforce Community License Overview
Mon, Jul 10th 2017 9:40a   Stephan H. Wissel
To facilitate collaboration across corporate boundaries, Salesforce offers Salesforce Communities. The licence for communities come in three flavours: customer community, customer community plus and partner community. There are similarities and differences between the entitlements. The biggest difference can be seen between customer community and customer community plus. There's a simple rationale behind it: a customer community account uses simplified sharing access, so the computational load
24
Sharing is caring - Salesforce edition
Fri, Jul 7th 2017 8:52a   Stephan H. Wissel
I like declarative security to give access exactly to the extend a user requires. When learning Salesforce, I discovered to my delight the portfolio of possibilities to tailor access. With great powers, as we know, come great responsibilities. Learning the Salesforce lingo can be quite daunting. So here is my little overview: Access to data in Salesforce is based on two principles: everything is owner based and a generally restricted access can be extended for given conditions, but not limite
5
Meeting a CxO
Thu, Jun 8th 2017 9:28a   Stephan H. Wissel
These are my notes on a role play we did in Salesforce to better cater to successful CxO meetings. Most of the topics do apply to any meeting, so no surprises here. We had actual CxO as participants. They shared that the most common item wanting is clear meeting agendas with outcomes, including them being time managed during the meeting. Second in line were unclear outcomes and not asking for a follow-up meeting.
2
From Blogsphere to a Static Site (Part 4) - Comment backend
Thu, May 4th 2017 7:32a   Stephan H. Wissel
The blog needed a comment function. While there are social options around (Facebook, Disqus etc), I decided I want to roll my own. Partly because I want tighter control and partly, well, because I could. My comment backend would: Provide a REST API to create comments in a JSON structure. The comment body will be Markdown. Reading would provide comments in ready to use HTML (I hear howling from the API crowd). No delete or update functionality Cleanup content considered harmful (code injection
3
The Decline and Fall of IBM
Mon, May 1st 2017 12:35p   Stephan H. Wissel
I wrote this quite a while ago, never finished the article until now. Enjoy. Yeah right! With this words Robert X Cringley a.k.a Mark Stephens celebrates himself when he asserts something clever. His book The Decline and Fall of IBM created quite some stir and was a hot topic of discussion especially among IBMers and alumni. So I got myself a copy and had a look. Clearly he has an axe to grind with IBM and everybody is invited. Many came. Half of the book consists of mostly grieving comments
1
From Blogsphere to a Static Site (Part 3) - Generating pages
Mon, May 1st 2017 11:23a   Stephan H. Wissel
The rendering engine I choose is mustache which describes itself as "logic-less templating engine". My main criteria was the availability on multiple platforms including Java and JavaScript (I might port the rendering part to NodeJS at some time in the future). The only logic mustache supports is conditional rendering based on the presence or absence of an element. When an element is present and is an array (or a collection in Java) the body of the template gets repeated for each element in t
1
From Blogsphere to a Static Site (Part 2) - Cleaning up the HTML
Mon, Apr 17th 2017 9:29a   Stephan H. Wissel
Blogsphere allows to create RichText and plain HTML entries. To export them I need to grab the HTML, either the manual entered or the RichText generated on, clean it up (especially for my manual entered HTML) and then replace image sources and internal links using the new URL syntax. To make this happen I created 2 functions that saved images and attachments and created a lookup list, so the HTML cleanup has a mapping table to work with private void saveImage(Document doc) { String sourceDirec




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition