Email view that does not show buttons and views of other activities - dynamics-crm-2011

I want to add Emails to navigation so It can be used like any other entity. Editing sitemap is not a problem but it does not work in the expected way.
First, of all it shows all entities, not emails only. And consequently there are filters for other activities which are unwanted.
How do I make email-view that does not show other activities?

Create a new view in CRM showing the records you wish to see
Create a HTML web resource, with an iFrame pointing to the URL of the view you just created. It will look something like this /advancedfind/advfind.aspx?AutoRun=true&QueryId=%7b495B7974-58AC-E234-92D4-EE155D107003%7d&ViewType=4230&etn=email
Point your sitemap to the new web resource

Related

How to force custom sublist view (Saved Search) on specific roles

I have modified the view under communication > Messages for a supplier, so that nobody apart from Finance should be able to see certain transactions. I also managed to make the new one default. However, the users still see the other views in the view dropdown list and the ‘View History’ button shows communication history of everything.
Please advice on how to stop the users from using the other views and remove ‘View History’ button? I tried workflow but it did not work.enter image description here

Working with Forms in Shopware

I am unable to understand how forms work in shopware. I need to update the contact page with my own style but when I add content into the contact page cannot see that content on page when I browse it.
Could you please let me know how to create a page and what need to be done to add a form to that page?
You are aware that the contact form is handled via configuration that can be done in the shopware backend's content > form section? there you will find a list of existing forms that can be modified by clicking the pen icon. A window will open where you can configure the forms name, the recipient email address, subject, email template as well as the form html content that will be shown in the frontend and the message that appears after submitting the form.
If you intend to change the layout (html and/or css) of the forms you need to override the forms template files:
frontend/forms/elements.tpl
frontend/forms/header.tpl
frontend/forms/index.tpl
Kind regards!

Emailing out an item in sharepoint 2010 to users that don't have access to the site

I am trying to figure out how to email out one item from a list by when you have an item clicking on a button as a web part. Sort of like when you create a print button and it prints out just the one item.
I don't want all of my users to have to download anything. Is there a way just to code the webpart to create a button where your outlook email pops up with a new email and the list item and details are in the body of the email?
While it is possible to build a button that would use JavaScript to scrape the contents of a specific element on a page (since you are building client side script) and put them into the body of an email, there's a lot of formatting issues that can arise there since non-text elements might be lost, styling might drop off and there's the potential for XSS, etc. You would also have to edit the item template for that button to show up.
You can also build a custom action that sends the content of the item through email with a workflow. This requires a bit of dev work in SharePoint that you may or may not be familiar with.
Additionally, if they don't have access to that site, why would you automate sending them content from it? If it's content they should have access to, why not put it in a list/library that is more tailored to their permission level?

Orchard CMS Editable Content on MVC Views

I'm working on an Orchard module for selling an e-book of sorts. Prior to purchase, a user can view a page showing a sample of the product. After purchase, there is no more need for the sample page, and the user has access to the full product.
I would like to set things up such that if a paying customer tries to access the sample page that they would be redirected to their full product and if a non-customer were to try to go to full product page they would be redirected to the sample. I'd also like my page content to be editable via the Dashboard.
My current implementation:
Controller handling the conditional routing / redirecting based on whether a purchase has been made.
A layer rule for each of my page url's each containing an html widget to provide the page content
This seems to work, but I am wondering what other options I have to accomplish this.
You may be making things way more complicated than they need to be.
Using widgets is unnecessary. It would be much better to build a regular content type and display that. You could serve it through a special controller that checks for a purchase, but even that is unnecessary. Instead, you could create a part that would have the purchase verification logic in its driver's display method. This way, you could even apply the exact same logic to any content type.

Create a web page in Orchard

I need to create a "custom" web page in Orchard. As I understand it, below are the steps I need to take to do so. Before I go down this somewhat lengthy process, are there any steps I'm missing or that I can skip?
Create a model
Create a content part and content part record which use the above model
Create a driver which implements the Display method which returns the "shape" of the content part
Create a shape template to render the shape returned from the above driver
Create a content type which holds the content part
Create a page which holds the content type
Add the page to my site
This page is "custom", in the sense that it needs to pull data from a web service and display it in an interactive way. When the user makes changes, those changes will need to be sent back to the web service.
Those are really steps for creating a content item. You would want to create a content item if your page should be treated as content - e.g. administrators can create, edit, publish, unpublish, and finally delete your page.
If you just want to create a simple page, then there is nothing to stop you from creating your own ASP MVC controller. You can define routes for it using Orchard's routing, and if you decorate it with a [Themed] attribute, it will even inherit the site's theme.

Resources