After introduction with salesforce community, I am unable to clear how community is different from portal functionality. I already read here but this don't have answers of question like:
What is new things being provided by community?
What are restriction we have if we use community?
Advantage of community over portal.
Is it capable of provide Email functionalities as same we have in other organization types?
Role of chatter in communities etc.
Is their difference between portal user and community user?
I already know that community is dedicated feature for portal functionality, but is it have some new functionality or only a portal part is separated?
Please provide some summary, links or answers you have.
While there are probably more detailed answers, it sounds like you are looking for a high-level overview. Communities basically combines Partner Portal, Customer Portal and chatter capabilities (so users can chatter on records they have access to, etc.)
Security, sharing, etc. are basically the same. There are standard responses on how it makes things more social and provides a path to greater communication but I think it comes down to combining the portals + chatter.
The main difference is that you will have more flexibility in terms of branding, integrating the communities with site.com CMS for publishing pages and also above all full Chatter integration for all things social.
The old Customer portal and Partner portals had an outdated look and feel and very basic support for publishing a full blown portal. The old Customer and Partner portals are retired and no longer offered, so your only option is not Communities.
With Salesforce 1 platform, now you can have a fully mobile optimized community portals as well.
You can also consider another solution called Magentrix which fully integrates with Salesforce CRM and allows you to build branded self-service mobile portals and more.
Related
I am currently looking into how to store and manage users in a production IdentityServer solution.
My question is how do you store and manage your users with IdentityServer? What have you tried that worked? and what to avoid?
Do you roll your own solution?
Use ASP.NET Identity?
I did read about the AdminUI commercial project, any alternatives? Any good publicly free available open-source solutions?
Do you roll your own solution?
Use ASP.NET Identity?
I personally prefer ASP.NET Identity
There is a lot of examples and a quick-start available (i.e. IDS4 docs, An old but good blog)
You have a very good, well documented and extensible base framework, classes and types already in-place and you can build on the top of it
Also as a side note, I would say keep IdentityServer4 and ASP.NET Identity solutions separated to have two separate development and deployment lifecycles, separate teams, etc.
I did read about the AdminUI commercial project, any alternatives? Any good publicly free available open-source solutions?
There is a nice open source admin UI available from skoruba. You can find more docs here
Can anybody explain me one thing? Is it possible to get free NetSuite sandbox account for the developer like in Salesforce (developer org)?
You can be a community developer and you get a free Netsuite account.
see http://www.netsuite.com/portal/developers/overview.shtml
It's a fully functioning standard Netsuite account so you don't get One World functionality but other than that you can do all the development and setup you need to do.
It's a bit restrictive in that once you have turned on some functionality like multi-location inventory you cannot turn it off again.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Is that possible? I know that services like Google Ads prohibit advertising in desktop applications. Is there a service that supports the WPF/.NET?
First,adsense being not allowed to be used in desktop apps , You can look for other advertising networks. There are other ad networks like amazon associates , .. etc . You can search for them according to the domains ex: banking, retails . You can look for/contact them for their terms and conditions on desktop usage.
And not all of them would provide you an API for .Net.
If amazon is allowed for desktop usage: Look into this
API
Secondly , w.r.t the technical aspects of WPF.
You can have a website built to inject ads from your network . Embed the URL in the web browser control in your WPF applications. This would work on condition that the desktop is connected to internet all the time.
In case if all doors are closed , and you still want to make money from your wpf app , you can think about using toolbars provided by various vendors in your application.
Hope this helps.
Here is some term you may encounter while your start your research in the marketing jungle. you can imagine the Marketplace of advertisement like WallStreet, it work with bidding.
open market : you may get X ads. Ads that lock the user navigation or else... it's a mess.
private market : elitist, you better have good arguments!
Publisher : probably YOU, your website, your application
Advertiser : generally brands
SSP : Supply-Side Platforms (for Publishers)
DSP : Demand-Side Platform (for Advertisers)
RTB : Real-Time Bidding (used by all open market)
PMP : Private Marketplace
Programmatic Direct : mostly used by PMP to ease advertisers<>publishers targeting & bidding
Inventory : ads Demands/Supplies
Impression : ads showed by publishers on a webpage/application
Ad Exchange: marketplace for SSP, DSP, Ad Network & other Ad exchange to buy/sell ad inventory
ex: Google Ad Manager (Google DoubleClick Ad Exchange) < this one is a PMP
Ad Network : (optionnal mediator / PMP)
ex: Google AdSense, Facebook Audience Network, Microsoft Advertising, Amazon Associates, openX, etc...
Ad Mediation (optionnal mediator working with multiple Ad Network)
--------------------------------------------------------------------------------------------------------
With all of that, you may still wonder why desktop application is not accepted by the PMP?
there's a lot of reason, but here are some:
You are unknow and brands don't want to take the risk to be associated with a hacking tool or other illegal stuff
mobile phone app is accepted coz they are all validated by a human review before been released in the "blabla store". So, advertiser don't need to worry too much about the quality of the publisher.
My advise is that if you want to be in business with a PMP, then you're going to have to prove yourself. Build a website (and put ads in it), publish your application, build a reputation, write mails, call phones, negotiate.
And i sincerly whish you to succeed!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Our organization is looking to put up a site utilizing DotNetNuke, and according to our consultant (who is less a .Net fan and more of a Joomla fan), there is 'anecotal evidence' that the Community version is crippled in a way that pretty much forces you to get Pro if you wish to have a reliable site.
I have serious doubts as to the validity of this claim, but just in case I would be very interested to hear if this is or is not the case, based on use of the product and it's community and professional versions.
Specifically, if there are bugs/issues/etc in the community version that are resolved only by upgrading to pro.
I apoligize in advance if I posted this on the wrong stack exchange, but figured this was the best bet ;)
I would definitely disagree with that assessment.
The only Pro feature that I can think of that might affect reliability is a different caching provider (which we've had more problems with than the standard caching provider). I believe it's the suggested provider for a web farm scenario, but in most typical scenarios it won't be a big issue.
The community edition is the same community edition that's been used in real sites for years, there's been no crippling to it since the introduction of the Pro version. The Pro version is just a number of custom extensions on top of the community edition, most of which are quite optional for everyday use a website.
The Edition Comparison on DotNetNuke.com shows the following inequalities:
Advanced Content Approval Workflows
Content approvals ensure any of your users impacted by a content change can approve updates before they go live. Workflow approvals can be configured in a top down hierarchy at the site, page, and module level. A business rules engine enables workflows with an unlimited number of states and reviewers
Granular Permissions
Page, module and folder level extended permissions provide granular security rights which allow you to precisely define which content contributors can edit which modules on each page.
Advanced Site Search
The search engine includes rich query syntax with support for Boolean searches, phrase searches, relevance searches, wild cards, fuzzy searches, and groupings. Includes a true web spider that is capable of indexing any site which removes the requirement to implement the ISearchable interface within modules.
Configuration Manager
A host user can manage the various configuration files that control run-time operation. Upload a Configuration Merge script which can be used to automate many of the more repetitive and complex configuration operations.
Content Staging
Content contributors and software engineers make all changes to your web site on a physically separate staging server. You push the staging site to production when all changes have been reviewed, tested and approved.
My Editable Pages
Links to all of the pages and modules in the site which a user has permission to Edit are displayed, allowing efficient page editing
Document Management
A complete document management solution which allows your organization to store, control and view documents online
Module Caching
A database caching provider for module content which stores module content in a centralized database for faster page loading without requiring web server processing.
Page Caching
Allows your site to save an entire page of rendered content to one of three different caching locations: memory, database or disk. Improves page delivery speed for site visitors.
Distributed Caching Provider
More efficient resource usage in large web farms
File Integrity Checking
Checks files in the installation and reports any inconsistencies which may impact website reliability
Health Monitoring
Pings your web site periodically to identify failures and will notify you of any problems. Also ensures the site stays in web server memory for faster visitor accessibility
Security Center
A host-level feature which dynamically loads a list of known security vulnerabilities affecting your version of DotNetNuke and provides you with navigational guidance to acquire the latest upgrade
Comprehensive Product Documentation
Includes more than 2,800 pages divided into User and Superuser Manuals
Online Knowledge Base
Provides guidance for DotNetNuke administrative tasks and answers to common technical questions
Impersonate User
A host-level feature that allows you to impersonate another user who is a member of your web site. Search for a user by name and then click an icon to assume their identity to view the site using the user’s permissions while keeping their password confidential.
Outside of the three caching items, I don't see anything in there that's more than icing on the cake. Also, having used many of those features, they aren't quite as impressive as they all sound, and the DNN community core isn't completely devoid of any similar features. Module caching, in particular, is available in the community edition, there's just another provider. Also, page caching is possible in the community edition, it just doesn't come with any page caching providers built-in.
Quite the opposite.
Disclosure: Scott Willhite, Director of Community Relations for DotNetNuke
There is absolutely NO limiting code in the DotNetNuke Community Edition, and I am quite proud of that fact. We have made a purposeful and, frankly, very challenging business decision to keep our Community Edition the base of all of our software. We engage in enhancement of the base Community Edition to produce Professional and Enterprise editions using the same extension points that are available to all developers. And we constantly add features and capability to the Community Edition which benefit all users of the platform. Any suggestion to the contrary is unfounded and misleading.
Some companies choose to limit their free editions (by number of users, number of content items, number of pages, etc). Some require branding that can't be removed in free editions. Others specifically use their free editions as "hooks", knowing that a customer of any size will be forced to upgrade if they want to continue using the product. None of these approaches is acceptable in a truly open source environment and none of them are in practice with DotNetNuke.
It is fair to say that we have resources working on proprietary extensions to distinguish our Professional and Enterprise edition offerings. But this is the same privilege we enable hundreds of thousands of others to enjoy who develop for or implement proprietary solutions using DotNetNuke. We are also customers of those extension points and so are constantly improving them for everyone's benefit because we don't just use them as marketing points, we base our companies products on them. Every release of DotNetNuke contains both substantial Community Edition as well as commercial edition enhancements.
To specifically answer your question... while there are no constraints within the Community Edition of DotNetNuke, and it is a highly functional application out of the box, it cannot address every need (no product can, all projects have unique requirements). This is why it is constructed with well defined extensions points and why there is such a vibrant open source and commercial ecosystem supporting it. So it is fair to say that the solution, out of the box, may not address all of your needs specifically? But between Professional & Enterprise options, 000's of commercial extensions on Snowcovered, 00's of open source options in the DotNetNuke Forge and myriad developers and integrators in the ecosystem (in addition to your own skills), I am confident that any need can be met in the way that makes the most sense for your or any application.
I too would disagree strongly. I've been working with DNN for years, well since version 3 and there is no great conspiracy to force CE users to upgrade to Pro. I've rolled out 100+ Community Edition sites (seriously, no exaggeration) and the ONLY PE sites I've worked on were usually government or educational institutions where they needed content staging or the benefits of the OpenDocument Library module. To me, it sounds much like you say - your consultant is letting his opinion of .Net vs. PHP flavor his recommendations.
We have an existing data source which already includes tables for users (employees) and roles.
Is there a way to use these tables instead of the users and roles tables created by lightswitch when you select forms authentication?
Check out this thread:
http://social.msdn.microsoft.com/Forums/en-US/lightswitchgeneral/thread/5f2965cf-a6d5-4b31-8ed5-a737fc13bdb9
BTW, the LightSwitch team is active on the Microsoft forums right now. You'll probably have a better bet using that forum for questions until the community builds up more. It's a new product so the team is trying to focus on discussions there right now.
Thanks for evaluating LightSwitch!